[SamStock ROM][ODEX][DEBLOAT][7.0][920/5 | W8 - F - I ][NOVEMBER PATCH]

[SamStock ROM][ODEX][DEBLOAT][7.0][920/5 | W8 - F - I ][NOVEMBER PATCH] - Galaxy S6 / S6 Edge Unified Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Other roms not giving you the performance or battery life you want? Try SAMSTOCK rom. It's so stock that its stock. Some rom makers like to customize their rom by branding it with their name, and I have nothing against that.
This rom however has none of that.
KNOX WARRANTY VOID: 1 (0X1)
Features:
-Untouched. Completely stock out of the latest zip from sammobile.
-December Security Patch
-Multi CSC just like stock firmware
-Safetynet Passed
-Private Mode working
-System Status = Official (In DL mode and in about phone)
-Can check for latest updates from samsung
-Play Store > Settings > Device Certification > Certified (MOST ROMS FAIL THIS)
-No branding by me at all
-No changes to any apk
-SE for Android Status: ENFORCING
-Samsung Health working fully
-Latest ROOT by topjohnwu
Whats customized
-this line from build.prop : "ro.config.tima=0"
But why DEV? You said stock.
To make Samsung Health work again.
NO OTHER FILE IN THIS ROM HAS BEEN TOUCHED ABSOLUTE STOCK!!
-Removed Samsung Pass (Does not work on any rom unless official not rooted)
-Removed Samsung Pay (Does not work on any rom custom or stock after knox trip)
Debloated apps include:
All available to reinstall from aroma.
-Facebook
-Instagram
-Onenote
-Peel Smart remote
-Skype
-WhatsApp
-Microsoft Excel
-Microsoft PowerPoint
-Microsoft Word
-Microsoft OneDrive
-Hancom Office
-Samsung Health
-S Voice (Honestly don't torture yourself)
-Yahoo Edge Panels (EDGE ONLY)
Requirements:
-Device SM-G920F/W8/I, SM-G925F/W8/I
-Flash latest firmware from Samsung
-Must be latest Bootloader and modem
-If you come to me with bricked devices I'll honestly just laugh. It says what you need right above this.
Installation:
-Backup your garbage
-Power off
-Charge to 80% or higher
-Boot into TWRP
-Advanced wipe ALL partitions except for /usbstorage
-Install Zip
-Select the garbage you want
-Let it install
-Reboot
FAQS
Q: I see a new update can you update the rom?
A: No those are generally region specific updates. Not major patches. Just carrier fixes. If I did it I would sit here for days.
Q: I checked for and downloaded a new update. I reboots into recovery and then nothing. What happened?
A: You cannot install OTA updates because they require the stock recovery to be installed. TLDR: Ignore the update.
Q: When are you updating this rom?
A: When samsung releases the next MAJOR/MONTHLY security patch update.
Q: When are you adding [Insert feature name here]?
A: Never. Its stock what ever stock comes with is what you get. There are other roms available for that.
Q: My phone is taking too long to boot. What should I do?
A: Did you follow all instructions? First boot takes 10-15 minutes.
Q: Fingerprint reader doesn't work. What do I do?
A: Device needs to be restarted.
Q: Can you remove/debloat [INSERT APP NAME HERE] and put it in aroma?
A: Sure when there's a new patch from Samsung I will.
Q: Does this work with my device?
A: If its a G920F/W8/I OR 925F/W8/I. Yes. Yes it does. If not. Get out.
Q: OK dev my garbage works like you said. Now what?
A: Let me know how you like it. Drop a like and enjoy. :laugh: :good:
Q: Why isn't there just one zip for all devices?
A: Because these aren't custom roms. They are stock. If i did one zip for all devices zip size would be 4GB+
Q: Will this work with my carrier?
A: Please click below to see a full list of supported CSC's.
SM-G920/5W8
-BMC (Bell Mobility)
-BWA (SaskTel)
-ESK (East Link)
-FMC (Fido Mobile)
-GLW (Freedom Mobile)
-KDO (Koodo)
-MTA (Manitoba Telecom)
-RWC (Rogers Wireless)
-TLS (Telus)
-VMC (Virgin Canada)
-VTR (VideoTron)
-XAC (Unlocaked Canada)
SM-G920F
-BTU (United Kingdom)
-CPW (United Kingdom)
-DBT (Germany)
-ITV (Italy)
-KOR (Korea)
-NEE (Finland)
-XEF (France)
-XEO (Poland)
SM-G925F
-BTU (United Kingdom)
-CPW (United Kingdom)
-DBT (Germany)
-ITV (Italy)
-KOR (Korea)
-NEE (Finland)
-XEF (France)
-XEO (Poland)
-XSG (UAE)
SM-920I
-BNG (Bangladesh)
-INS (India)
-INU (India)
-NPL (Nepal)
-SLK (Sri Lanka)
SM-G925I
-BNG (Bangladesh)
-INS (India)
-INU (India)
-NPL (Nepal)
-SLK (Sri Lanka)
Thanks to:
-amarullz for Aroma
-topjohnwu for Magisk 14 Root
-Samsung for the stock rom
-Carriers for doing nothing
DROP THESE GUYS A LIKE TOO THEY DESERVE IT.
For Developers:
-If you want to use this as a base for your rom please PM me and i'll reply asap
-If you want to help add features to aroma them PM me so we can talk business
Samsung Official Security Bulliten:
This is the security patch status. Here you'll be able to see the vulnerabilities that were fixed by Samsung and google.
JULY:
Code:
SMR-JUL-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process.
This SMR package includes patches from Google and Samsung.
Google patches include patches up to Android Security Bulletin - July 2017 package.
The Bulletin (July 2017) contains the following CVE items:
Critical: CVE-2017-0564, CVE-2016-9794, CVE-2015-7555, CVE-2017-0540, CVE-2017-0673, CVE-2017-0674, CVE-2017-0675, CVE-2017-0676, CVE-2017-0677, CVE-2017-0678, CVE-2017-0679, CVE-2017-0680, CVE-2017-0681, CVE-2017-0469
High: CVE-2017-6423, CVE-2015-9004, CVE-2014-9940, CVE-2017-0648, CVE-2017-6074, CVE-2017-8253, CVE-2017-8273, CVE-2014-9979, CVE-2015-8595, CVE-2017-0664, CVE-2017-0665, CVE-2017-0666, CVE-2017-0667, CVE-2017-0669, CVE-2017-0670, CVE-2017-0671, CVE-2016-2109, CVE-2017-0672, CVE-2017-0684, CVE-2017-0685, CVE-2017-0686, CVE-2017-0688, CVE-2017-0689, CVE-2017-0690, CVE-2017-0691, CVE-2017-0692, CVE-2017-0693, CVE-2017-0694, CVE-2017-0695, CVE-2017-0696, CVE-2017-0697, CVE-2017-0700, CVE-2017-0701, CVE-2017-0702, CVE-2017-0703, CVE-2017-0642
Moderate: CVE-2017-7368, CVE-2017-7364, CVE-2017-8237, CVE-2015-5707, CVE-2016-5863, CVE-2017-8246, CVE-2017-8256, CVE-2017-8257, CVE-2016-3924, CVE-2017-0493, CVE-2015-7995, CVE-2017-3544, CVE-2017-0698, CVE-2017-0699
Low: CVE-2017-8241
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 16 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices.
Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8290: Crash via sending broadcast (AdaptiveDisplayColorService)
Severity: Low
Affected versions: KK(4.4), L(5.0/5.1), M(6.0), N(7.x)
Reported on: February 14, 2017
Disclosure status: Privately disclosed.
Lack of appropriate exception handling for Intents including Serializable instance allows attackers crash several system processes resulting in a possible DoS attack.
The patch prevents system crashes by handling unexpected exceptions.
SVE-2017-8888: Buffer overflow in tlc_server
Severity: Medium
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
There is a potential buffer overflow vulnerability due to not confirming if the size of source data is smaller than the destination buffer.
The patch removes the problematic code.
SVE-2017-8973: Buffer overflow in process_cipher_tdea
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
There is a potential buffer overflow vulnerability due to not verifying input and output parameters’ sizes.
The fix avoids a buffer overflow by checking if the size of output data is the same as input data.
SVE-2017-9109: Unintended memory is disclosed in rkp log
Severity: Medium
Affected versions: M(6.0), N(7.x)
Reported on: May 4, 2017
Disclosure status: Privately disclosed.
The vulnerability allows reading data outside of rkp log buffer boundary due to not checking the boundary.
The applied patch avoids an illegal access to memory by checking the boundary.
SVE-2017-9122, SVE-2017-9123, SVE-2017-9124, and SVE-2017-9126: Crash system server via sending broadcast
Severity: Low
Affected versions: N(7.x)
Reported on: May 10, 2017
Disclosure status: Privately disclosed.
Lack of appropriate exception handling for some Intents which cause NullPointerException allows attackers crash a system process resulting in a possible DoS attack.
The patch protects the receiver by changing to protected intent.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truely appreciate the following researchers for helping Samsung to improve the security of our products.
- Ryan Johnson and Angelos Stavrou of Kryptowire : SVE-2017-8290, SVE-2017-9122, SVE-2017-9123, SVE-2017-9124, SVE-2017-9126
- Daniel Komaromy : SVE-2017-8888, SVE-2017-8973
- David Berard : SVE-2017-9109
AUGUST:
Code:
SMR-AUG-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process.
This SMR package includes patches from Google and Samsung.
Google patches include patches up to Android Security Bulletin - August 2017 package.
The Bulletin (August 2017) contains the following CVE items:
Critical: CVE-2017-0714, CVE-2017-0715, CVE-2017-0716, CVE-2017-0718, CVE-2017-0719, CVE-2017-0720, CVE-2017-0721, CVE-2017-0722, CVE-2017-0723, CVE-2017-0745, CVE-2017-0407, CVE-2017-9417
High: CVE-2017-0576, CVE-2016-10286, CVE-2016-10244, CVE-2017-0713, CVE-2017-0724, CVE-2017-0725, CVE-2017-0726, CVE-2017-0727, CVE-2017-0728, CVE-2017-0729, CVE-2017-0730, CVE-2017-0731, CVE-2017-0732, CVE-2017-0733, CVE-2017-0734, CVE-2017-0735, CVE-2017-0736, CVE-2017-0687, CVE-2017-0737
Moderate: CVE-2017-0583, CVE-2016-5346, CVE-2017-6425, CVE-2016-10236, CVE-2017-6426, CVE-2017-7370, CVE-2017-7372, CVE-2017-7373, CVE-2017-0451, CVE-2017-7308, CVE-2017-8264, CVE-2017-8266, CVE-2017-8268, CVE-2017-8258, CVE-2017-0560, CVE-2017-0712, CVE-2017-0738, CVE-2017-0739
Low: CVE-2017-0452
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 12 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices.
Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8889, SVE-2017-8891, and SVE-2017-8892: Stack overflow in trustlet
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
Lack of boundary checking of a buffer in trustlet can lead to memory corruption.
The applied patch adds boundary checking.
SVE-2017-8890: Over-read in trustlet
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
Lack of boundary checking of a buffer in trustlet can lead to unauthorized access to data outside of boundary.
The applied patch adds boundary checking.
SVE-2017-8893: Arbitrary write in trustlet
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
Assuming privilege escalation is achieved, lack of boundary checking in a trustlet can lead to arbitrary write.
The applied patch adds boundary checking.
SVE-2017-9008 and SVE-2017-9009: Integer overflow in trustlet
Severity: Low
Affected versions: N(7.x)
Reported on: April 24, 2017
Disclosure status: Privately disclosed.
Lack of boundary checking of a buffer in trustlet can lead to memory corruption.
The patch removed the part of code related to Integer overflow.
SVE-2017-9383: Abnormal screen touch via malformed input with multiwindow_facade API
Severity: Low
Affected versions: M(6.0)
Reported on: May 31, 2017
Disclosure status: Privately disclosed.
Lack of appropriate validation check for display ID can halt system due to NullPointException problem caused by mismatch to a non-existing display.
The supplied patch prevents unexpected exception by confirming the validation of display ID.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truely appreciate the following researchers for helping Samsung to improve the security of our products.
- Daniel Komaromy : SVE-2017-8889, SVE-2017-8890, SVE-2017-8891, SVE-2017-8892, SVE-2017-8893, SVE-2017-9008, SVE-2017-9009
- Qing Zhang of Xiaomi and Guangdong Bai of Singapore Institute of Technology (SIT) : SVE-2017-9383
NOVEMBER:
Code:
SMR-NOV-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process. This Security Update package includes patches from Google and Samsung.
The following CVE items from November 2017 Android Security Bulletin are included in this Security Update package:
Critical
CVE-2017-11053, CVE-2017-9714, CVE-2017-0832, CVE-2017-0833, CVE-2017-0834, CVE-2017-0835, CVE-2017-0836, CVE-2017-0841
High
CVE-2017-9075, CVE-2017-11063, CVE-2017-0830, CVE-2017-0831, CVE-2017-0839, CVE-2017-0840, CVE-2017-0842, CVE-2017-0852, CVE-2017-0853(M 6.x), CVE-2017-0854(M 6.x), CVE-2017-0857(M 6.x), CVE-2017-0858(M 6.x), CVE-2017-0859(M 6.x), CVE-2017-13077, CVE-2017-13078, CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13086, CVE-2017-13087, CVE-2017-13088
Moderate
CVE-2017-0824, CVE-2017-0825, CVE-2017-7187, CVE-2017-9686, CVE-2017-11050, CVE-2017-11067, CVE-2017-11056, CVE-2017-11046, CVE-2017-9706, CVE-2017-11048, CVE-2017-9697, CVE-2017-11051, CVE-2017-9715, CVE-2017-9717, CVE-2017-11054, CVE-2017-11055, CVE-2017-0845, CVE-2017-0847, CVE-2017-0848, CVE-2017-0849, CVE-2017-0850, CVE-2017-0851, CVE-2017-0853(N 7.x, O 8.0), CVE-2017-0854(N 7.x, O 8.0), CVE-2016-2105, CVE-2016-2106, CVE-2017-3731, CVE-2017-0860
Low
None
NSI
CVE-2017-0857(N 7.x, O 8.0), CVE-2017-0858(N 7.x, O 8.0), CVE-2017-0859(N 7.x)
Already included in previous updates
None
Not applicable to Samsung devices
CVE-2017-7374, CVE-2017-0827, CVE-2017-9683, CVE-2017-0826, CVE-2017-0828, CVE-2017-0829, CVE-2017-11062, CVE-2017-9687
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 6 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices. Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8973, SVE-2017-8974, SVE-2017-8975: TA Scrypto v1.0 Vulnerability
Severity: Low
Affected versions: M(6,x), N(7.0)
Reported on: April 17, 2017
Disclosure status: Privately disclosed.
A race condition may occur in Secure Driver resulting in potential buffer overflow vulnerability.
The patch prevents race condition and buffer overflow by checking boundary of a buffer.
SVE-2017-10086: Arbitrary file read/write in locked device via mtp
Severity: High
Affected versions: KK(4.4.x), L(5.x), M(6.x), N(7.x)
Reported on: August 17, 2017
Disclosure status: Privately disclosed.
Device responds from malicious MTP command on the locked state.
The patch prevents the device from responding from a malicious MTP command when it receives MTP command on the locked state.
SVE-2017-10465: Bug in MSM8998 chipset’s bootloader that checks integrity of system image (SamFAIL)
Severity: High
Affected versions: N(7.x)
Reported on: October 08, 2017
Disclosure status: Privately disclosed.
A vulnerability in verification logic within the bootloader in Qualcomm MSM8998 chipset allows an attacker to successfully boot the Samsung Galaxy Note8 device with root privilege.
The patch prevents an Attacker from booting Note8 successfully by checking an integrity of system image.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truly appreciate the following researchers for helping Samsung to improve the security of our products.
- Salvatore Mesoraca : SVE-2017-10086
- Daniel Komaromy : SVE-2017-8973, SVE-2017-8974, SVE-2017-8975
DECEMBER:
Code:
SMR-DEC-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process. This Security Update package includes patches from Google and Samsung.
The following CVE items from December 2017 Android Security Bulletin are included in this Security Update package:
Critical
CVE-2017-11013, CVE-2017-11015, CVE-2017-11014, CVE-2017-0427, CVE-2017-0872, CVE-2017-0878, CVE-2017-13151, CVE-2017-13160, CVE-2015-3868, CVE-2017-0675, CVE-2017-6211
High
CVE-2017-0871, CVE-2017-9077, CVE-2017-7541, CVE-2017-0843, CVE-2017-11092, CVE-2017-11028, CVE-2017-0838, CVE-2017-0807, CVE-2017-0870, CVE-2017-13153, CVE-2017-0837, CVE-2017-0873, CVE-2017-0874, CVE-2017-0880, CVE-2017-13148, CVE-2017-13156, CVE-2017-13157, CVE-2017-13158, CVE-2017-13159, CVE-2017-13077, CVE-2017-0879(L5.1, M6.x), CVE-2017-13149(L5.1, M6.x), CVE-2017-13150(M6.x)
Moderate
CVE-2017-11057, CVE-2017-11059, CVE-2017-11061, CVE-2017-11060, CVE-2017-11052, CVE-2017-11064, CVE-2017-0861, CVE-2017-1160, CVE-2017-11073, CVE-2017-11035, CVE-2017-11012, CVE-2017-11085, CVE-2017-11091, CVE-2017-11032, CVE-2017-11024, CVE-2017-11025, CVE-2017-11023, CVE-2017-11029, CVE-2017-11018, CVE-2017-9702, CVE-2017-11089, CVE-2017-8239, CVE-2017-11090, CVE-2017-11093, CVE-2017-8279, CVE-2017-9696, CVE-2017-11058, CVE-2017-11022, CVE-2017-0879(N7.x, O8.0), CVE-2017-13149(N7.x, O8.0), CVE-2017-13150(N7.x, O8.0), CVE-2017-13152
Low
None
NSI
None
Already included in previous updates
None
Not applicable to Samsung devices
CVE-2017-6264, CVE-2017-9690, CVE-2017-11017, CVE-2017-6001, CVE-2017-0862, CVE-2017-0863, CVE-2017-0864, CVE-2017-0865, CVE-2017-0866, CVE-2017-6274, CVE-2017-6275, CVE-2017-11026, CVE-2017-11038, CVE-2017-9719, CVE-2017-9721, CVE-2017-9701, CVE-2017-11027, CVE-2017-0876, CVE-2017-0877
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 10 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices. Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8907: Information disclosure on Samsung gpu
Severity: Moderate
Affected versions: M(6.x), N(7.x)
Reported on: April 14, 2017
Disclosure status: Privately disclosed.
kbase_context address in gpu memory node is exposed and it may result in unauthorized information disclosure.
The patch prevents kernel memory address exposure which includes kbase_context address in gpu node.
SVE-2017-10011: muic_set_reg_sel heap_overflow
Severity: Moderate
Affected versions: L(5.1), M(6.x), N(7.x)
Reported on: August 17, 2017
Disclosure status: Privately disclosed.
System can be crashed by non-existence of null pointer check; and buffer overflow vulnerability exists because the size to be copied from user space is not checked.
The patch prevents Null Pointer dereference and buffer overflow when muic register values are read.
SVE-2017-9414: panel_lpm sysfs stackOverflow issue
Severity: Moderate
Affected versions: M(6.x), N(7.x) with Qualcomm chipsets
Reported on: June 5, 2017
Disclosure status: Privately disclosed.
The size of user data is not checked and it makes buffer overflow when user data is copied into an array.
The patch prevents buffer overflow when user data is copied in lpm ctrl debug function.
SVE-2017-10598: Arbitrary Code Execution in the Samsung Bootloader
Severity: Moderate
Affected versions: L(5.x), M(6.x), N(7.x) with Exynos chipsets
Reported on: October 8, 2017
Disclosure status: This issue is publicly known.
S Boot copies ramfs data to its memory without checking validation of the size making it possible to overwrite the code segment of S Boot which can result in arbitrary code execution in bootloader.
The patch prevents arbitrary code execution in bootloader by checking the limit of ramdisk size.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truly appreciate the following researchers for helping Samsung to improve the security of our products.
- Yaoguang Chen of Ant-financial Light-Year Security Lab : SVE-2017-8907
- Yu Pan and Yang Dai of Vulpecker Team Qihoo 360 Technology Co. Ltd : SVE-2017-10011, SVE-2017-9414
- Hung Chi Su of Team T5 : SVE-2017-10598
Development Status:
This is the development status section here you will be able to see what I am currently doing for this rom. If I have an older firmware version listed as latest please inform me as I only have worked with W8 devices in the past. Refer to the legend below to see what each status means.
LEGEND
STOPPED: Latest link available. No updates till next patch.
IN DEVELOPMENT: New build uploaded by sammobile. Development begins.
TESTING: Development ended. Ensuring rom is functional.
UPLOADING: Testing has ended now uploading.
BEFORE APPLYING NEW BUILDS. DOWNLOAD NEW STOCK FIRMWARES AND FLASH THEM THROUGH ODIN. THEN FLASH TWRP VIA ODIN THEN MY ROM.BEFORE APPLYING NEW BUILDS. DOWNLOAD NEW STOCK FIRMWARES AND FLASH THEM THROUGH ODIN. THEN FLASH TWRP VIA ODIN THEN MY ROM.BEFORE APPLYING NEW BUILDS. DOWNLOAD NEW STOCK FIRMWARES AND FLASH THEM THROUGH ODIN. THEN FLASH TWRP VIA ODIN THEN MY ROM.
PLEASE BE VERY CAREFUL AS THESE ARE STOCK ROMS THEY ARE NOT CUSTOMIZED SO FLASHING EDGE ROMS ON FLAT MODELS COULD RESULT IN SOFT BRICK, IMEI LOSS OR DEAD EMMC. YOU HAVE BEEN WARNED. IF YOU CLICK THE DOWNLOAD BUTTON YOU AGREE THAT YOU TAKE FULL RESPONSIBILITY FOR ANY DAMAGES YOU MAY CAUSE. IF YOU BLAME ME OR ANY OTHER DEVELOPERS FOR YOUR FAILURE TO UNDERSTAND THESE MESSAGES THEN WE WILL NOT HELP YOU SOLVE YOUR PROBLEM.
GALAXY S6
920W8 STATUS: STOPPED
BUILD NUMBER: G920W8VLS5DQK1
Security LEVEL: 2017-11-01
REASON: Waiting for December patch from Samsung. Nov. Patch Available.
NEXT UPDATE ETA: December (Date Unknown)
LINK: DOWNLOAD
920F STATUS: STOPPED
BUILD NUMBER: G920FXXS5EQL1
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
920I STATUS: STOPPED
BUILD NUMBER: G920IDVS3FQL5
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
GALAXY S6 EDGE
925W8 STATUS: STOPPED
BUILD NUMBER: G925W8VLS5DQH1
Security LEVEL: 2017-08-01
REASON: Waiting for December patch from Samsung. Aug. Patch Available.
NEXT UPDATE ETA: September (Date Unknown)
LINK: DOWNLOAD
925F STATUS: STOPPED
BUILD NUMBER: G925FXXS5EQL1
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
925I STATUS: STOPPED
BUILD NUMBER: G925IDVS3FQL5
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
Bugs:
-Samsung Internet Secret Mode works initially then never again.
TEMP FIX: Use internet beta from play store. (Basically same app but allows p0rn mode to work.)
XDA:DevDB Information
SamStock ROM, ROM for the Samsung Galaxy S6
Contributors
Moiz Ahmed
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Modem and Bootloader
Based On: Samsung Stock
Version Information
Status: Stable
Stable Release Date: 2017-07-31
Created 2017-08-01
Last Updated 2017-12-25

Reserved
DECEMBER BRANCH STARTED
Devices updated:
S6 FLAT
-920I
-920F
S6 EDGE
-925F
-925I
Devices not yet updated:
S6 FLAT
-920W8 (NOV)
S6 EDGE
-925W8 (AUG)
FIXES:
-Removed SVCAgent from rom to aroma. (PART OF S-Voice)
-root updated to magisk 14
-Added DTM CSC for 920F
-other fixes include bug fixes in samsung source code found in the SMR and during installation.

Reserved

Moiz Ahmed said:
Other roms not giving you the performance or battery life you want? Try SAMSTOCK rom. It's so stock that its stock. Some rom makers like to customize their rom by branding it with their name, and I have nothing against that.
This rom however has none of that.
Features:
-Untouched. Completely stock out of the latest zip from sammobile.
-July Security Patch
-Multi CSC just like stock firmware
-Safetynet Passed
-Private Mode working
-System Status = Official (In DL mode and in about phone)
-Can check for and DL latest updates from samsung
-No branding by me at all
-No changes to any apk
-SE for Android Status: ENFORCING
-Samsung Health working fully
-Latest ROOT by topjohnwu
Whats customized
-this line from build.prop : "ro.config.tima=0"
But why DEV? You said stock.
To make Samsung Health work again.
NO OTHER FILE IN THIS ROM HAS BEEN TOUCHED ABSOLUTE STOCK!!
Debloated apps include:
All available to reinstall from aroma.
-Facebook
-Instagram
-Onenote
-Peel Smart remote
-Skype
-WhatsApp
-Microsoft Excel
-Microsoft PowerPoint
-Microsoft Word
-Microsoft OneDrive
-Hancom Office
-Samsung Health
-S Voice (Honestly don't torture yourself)
-Yahoo Edge Panels (EDGE ONLY)
Requirements:
-Device SM-G920W8, SM-G925W8
-Flash latest firmware from Samsung
-Must be latest Bootloader and modem
-If you come to me with bricked devices I'll honestly just laugh. It says what you need right above this.
Installation:
-Backup your garbage
-Power off
-Charge to 80% or higher
-Boot into TWRP
-Advanced wipe all partitions except for /usbstorage
-Install Zip
-Select the garbage you want
-Let it install
-Reboot
FAQS
Q: When are you updating this rom?
A: When samsung releases the next update
Q: When are you adding [Insert feature name here]?
A: Never. Its stock what ever stock comes with is what you get. There are other roms available for that.
Q: My phone is taking too long to boot. What should I do?
A: Did you follow all instructions? First boot take 10-15 minutes.
Q: Fingerprint reader doesn't work. What do I do?
A: Device needs to be restarted.
Q: Can you remove/debloat [INSERT APP NAME HERE] and put it in aroma?
A: Sure when there's a new patch from Samsung I will.
Q: Does this work with my device?
A: If its a G920W8/925W8. Yes. Yes it does. If not. Get out.
Q: OK dev my garbage works like you said. Now what?
A: Let me know how you like it. Drop a like and enjoy. :laugh: :good:
Thanks to:
-amarullz for Aroma
-topjohnwu for Magisk 13.3 Root
-Samsung for the stock rom
-Carriers for doing nothing
DROP THESE GUYS A LIKE TOO THEY DESERVE IT.
For Developers:
-If you want to use this as a base for your rom please PM me and i'll reply asap
-If you want to help add features to aroma them PM me so we can talk business
Development Status:
This is the development status section here you will be able to see what I am currently doing for this rom.
920W8 STATUS: STOPPED
BUILD NUMBER: G920W8VLS5DQG1
REASON: Rev 1.2 Uploaded. No new updates from samsung.
ETA: August (Day Unknown)
920F STATUS: IN DEVELOPMENT
REASON: Working on initial release. 920F Testers needed.
ETA: Unknown
925W8 STATUS: STOPPED
BUILD NUMBER: G925W8VLS5DQG1
REASON: Uploaded. No new updates from samsung.
ETA: August (Day Unknown)
925F STATUS: IN DEVELOPMENT
REASON: Working on initial release. 925F Testers needed.
ETA: Unknown
Bugs:
-Samsung Internet Secret Mode works initially then never again.
TEMP FIX: Use internet beta from play store. (Basically same app but allows secret mode to work.)
Download:
PLEASE BE PATIENT AS I TRANSFER FILES TO A NEW DRIVE ACCOUNT. LINKS WILL BE UP SOON.
SM-G920W8NOT AVAILABLE
SM-G925W8NOT AVAILABLE
SM-G920F NOT AVAILABLE
SM-G925F NOT AVAILABLE
XDA:DevDB Information
SamStock ROM, ROM for the Samsung Galaxy S6
Contributors
Moiz Ahmed
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Modem and Bootloader
Based On: Samsung Stock
Version Information
Status: Stable
Stable Release Date: 2017-07-31
Created 2017-08-01
Last Updated 2017-07-31
Click to expand...
Click to collapse
What about SM-G925I?

nokia_16 said:
What about SM-G925I?
Click to expand...
Click to collapse
If a lot more people want it i'll do a 925I and 920I. I have a Ryzen 5 CPU and extraction and compression of these firmwares simultaneously doesn't take too much time but i need people to actually use it otherwise my work is worth nothing.

Hi,
Thanks for uploading the Rom. I'd like to have a look. Though two questions :
A) the description about support for g920f is a bit inconsistent. It says it is stopped and you say only the g920w variants work, but then there is a download link.
B) which csc is this based on? Does VoLTE work? Especially on German t-mobile? It usually requires a DTM csc
Br
Johannes

orgler said:
Hi,
Thanks for uploading the Rom. I'd like to have a look. Though two questions :
A) the description about support for g920f is a bit inconsistent. It says it is stopped and you say only the g920w variants work, but then there is a download link.
B) which csc is this based on? Does VoLTE work? Especially on German t-mobile? It usually requires a DTM csc
Br
Johannes
Click to expand...
Click to collapse
Hi sorry for the confusion. Stopped means i'm not doing any work on it anymore till next samsung update. As for csc when I unpacked the stock zip there was only one csc which led me to believe its an unlocked csc. All other models had multi csc support. Try it and let me know please i only have the W8 model. I'll take a look tomorrow morning.

Moiz Ahmed said:
If a lot more people want it i'll do a 925I and 920I. I have a Ryzen 5 CPU and extraction and compression of these firmwares simultaneously doesn't take too much time but i need people to actually use it otherwise my work is worth nothing.
Click to expand...
Click to collapse
May be once you do for 925I a lot user may opt to your rom coz there is no stock debloated nought rom for G925I. Hence its my request to make your rom for G925I. This is only an request. Also if you decided to do so go for INS csc or multi csc whch has INS or INU, coz both csc volte will work.

nokia_16 said:
May be once you do for 925I a lot user may opt to your rom coz there is no stock debloated nought rom for G925I. Hence its my request to make your rom for G925I. This is only an request. Also if you decided to do so go for INS csc or multi csc whch has INS or INU, coz both csc volte will work.
Click to expand...
Click to collapse
Ok I think I'll start tomorrow morning. Please link me to the latest multi csc for 920I and 925I from sammobile.com

Moiz Ahmed said:
Ok I think I'll start tomorrow morning. Please link me to the latest multi csc for 920I and 925I from sammobile.com
Click to expand...
Click to collapse
Sammobile has not yet updated latest version for g925i ..I am sending you direct link for g925i. Updated one similar to sammobile.
Here is the link...

nokia_16 said:
Sammobile has not yet updated latest version for g925i ..I am sending you direct link for g925i. Updated one similar to sammobile.
Here is the link...
Click to expand...
Click to collapse
Great downloading now. Could you also send me the 920I link usually same last 4 characters as 925I.

nokia_16 said:
Sammobile has not yet updated latest version for g925i ..I am sending you direct link for g925i. Updated one similar to sammobile.
Here is the link...
Click to expand...
Click to collapse
Great downloading now. Could you send me the 920I link. It's usually same last 4 build number characters.

Can anyone point me in the direction where I can find the latest modem and bootloader for my SM-G920F? And does the region of the modem matter? tnx

amgat said:
Can anyone point me in the direction where I can find the latest modem and bootloader for my SM-G920F? And does the region of the modem matter? tnx
Click to expand...
Click to collapse
Hi yes region does matter. the simple way would be to go HERE download the latest firmware for your model and region then flash using odin. then return here and flash this. TO find out your region go to dialer type *#1234# and the values that appear will guide you in finding your region.

Thank you Moiz Ahmed!. Does the firmware contain the latest modem as well? Or is not that important to update the modem?

amgat said:
Thank you Moiz Ahmed!. Does the firmware contain the latest modem as well? Or is not that important to update the modem?
Click to expand...
Click to collapse
Very important to update both modem and bootloader. Best to do a complete wipe flash latest stock then this.

The firmware file is 1.8GB in size. So the firmware file from updato is actually the stock ROM right? Sorry for asking dumb questions

Does Secure Folder work with this rom?

amgat said:
The firmware file is 1.8GB in size. So the firmware file from updato is actually the stock ROM right? Sorry for asking dumb questions
Click to expand...
Click to collapse
Yes it is.

huyhung411991 said:
Does Secure Folder work with this rom?
Click to expand...
Click to collapse
Nope

Related

[ROM][7.1.2_r33] AOSPlusone 7.1 [SultanXDA's Camera HAL][OMS] | 25/08/17

Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Hi everyone, freshgiammi here. Some of you may know me from my previous work on maguro (Galaxy Nexus), while some others may not. Here I am, presenting you an AOSP build of Nougat for our Oneplus One.
What does it differ from other ROMs?
Simple. It's philosophy is staying close to stock. Even closer that OmniROM. Closer to AOSP than AOSP itself.
Jokes apart, AOSP is the true philosophy, with a few tweaks to make it feel snappier but not too much intrusive changes.
HOW STABLE IT IS
Rock steady.
This ROM is designed with two things in mind: Security and Stability.
Everything is tested for multiple days (both from me, and from private testers) to be sure nothing lets the final user with instabilities. This makes the ROM stable and reliable, not making it go into full retard when you need it most.
And since this is AOSP based, with an AOSP philosophy in mind, remember that any feature that is not included in the official source code won't be added.
Beware. Since we have no N official builds, issues are to be expected. Devs are working hard to fix them as they get spotted, but some bugs only appear to certain users or under certain conditions. Because of that, if you encounter an issue please let me know.
Tag me in a reply, attaching a logcat/dmesg (last_kmsg if your phone reboots) with the steps to replicate and a short description of the problem. That way I can fix it faster.
WHAT DOES THIS ROM OFFERS, MORE THAN AOSP?
Well, there's some neat stuff aside from AOSP that's included here.
-SultanXDA's Camera HAL with Stagefright Hardening
-Night Light and Storage Manager (from Google Pixel)
-SELinux Enforcing
-F2FS Support (beware, you need to format to F2FS with TWRP 2.8.6.0 as 3.0.2.0 has issues with F2FS formatting.)
-Substratum is available! Go theme your device as you like it!
More? You tell me!
DOWNLOADS
Lastest Build: AOSPlusone_bacon_250817 FINAL RELEASE
Gapps: OpenGapps
Sources up at my Github!
Feel free to clone and create your own rom. Just make sure to prevent authorship and pull requests if you fix something!
Changelog is on #2, while FAQs and extra ZIPs are on #3!
XDA:DevDB Information
AOSPlusone, ROM for the OnePlus One
Contributors
freshgiammi
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2016-10-11
Last Updated 2017-08-25

Reserved. (CHANGELOG)
14 Jun. 2017 -> 25 Aug. 2017
Code:
[B]ROM: Updated to 7.1.2_r33[/B]
HAL: Upstreamed code to match Sultanxda's sources
+ Something that I don't remember but hey everything works well
21 Mar. 2017 -> 14 Jun. 2017
Code:
[B]ROM: Updated to 7.1.2_r11[/B]
ROM: Updated Substratum and Interfacer to lastest versions
[B]Kernel: Updated to 3.4.113[/B]
Kernel: Updated to match lastest kernel/common source from Android (3.4 is now deprecated)
Kernel: Upstream patches from LOS-14.1
[B]Kernel: Camera-drivers fixups from CAF[/B]
[B]HAL: Upstreamed code to improve stability
HAL: Fixed overexposure when taking picture with in good lightning conditions.
HAL: Fixed zooming in/out during video recording on Instagram/Snapchat[/B]
HAL: Merged patches from SultanXDA
[B]Vendor: Updated WDM libraries to match bullhead 7.1.1 ones[/B]
Vendor: Shimmed GraphicBuffer for camera libraries
[B]Snap: Merged upstream patches from LOS-14.1[/B]
Snap: Removed touch-to-screenshot during video recording
Snap: Fixed ZSL not re-enabling after disabling HDR
Snap: Added back 1440p resolution for videos
Previous Changelogs:
05 Feb. 2017 -> 21 Mar. 2017
Code:
[B]ROM: Updated to 7.1.1_r28[/B]
[B]ROM: Fixed Torch QS not working between reboots[/B]
[B]ROM: Substratum is now rootless[/B]
ROM: Substratum App is now bundled within the ROM
[B]HAL: Merged lastest patches from SultanXDA[/B]
[B]HAL: Moved nativehandle logic from CameraServer to HAL[/B]
Snap: Rebased Snap on CM14.1 sources
22 Jan. 2017 -> 05 Feb. 2017
Code:
[B][B]ROM[/B]: enabled F2FS support[/B]
ROM: Removed leftovers from Camera2
ROM: Re-enabled textiles check (Textiles are not globally allowed anymore)
[B]ROM: Enabled backuptool (thanks to @mandaman2k)
ROM: Fixed ringtone and notifications not being set (thanks to @medic)[/B]
ROM: Fixed qti.tetherservice crashing at startup
[B]ROM: Merged some security patches on hardware/qcom/media-caf[/B]
[B]Kernel: Fixed fast-charging not working for some users[/B]
Kernel: Fixed MPDecision not turning off cores 2 and 3
[B]Kernel: Restored CONFIG_MACH_OPPO;.[/B] (This will probably make kernel more stable,
but can cause instabilities. Please report any reboots.)
[B]Kernel: Fixed NULLPointer (kernel panic) when watching WEBM videos or using Google Fit.[/B]
Kernel: Merged the latest patches from LOS
[B]Snap: Fixed crash when resuming a video paused during recording[/B]
Snap/CameraHAL: Merged lastest patches from Sultanxda.
16 Jan. 2017 -> 22 Jan. 2017
Code:
[B]Adapted Camera HAL to work with the new stagefright hardening![/B]
[B]SELinux is now enforcing![/B]
[B]*maybe*[/B] Fixed HW Encryption (Need confirms)
[B]Fixed most of HFR/HSR;[/B] Everything works besides [email protected] and [email protected]
[B]Fixed Ambient Display
Fixed audio misbehaving with AUX cords (>3 pins jack)[/B]
11 Jan. 2017 -> 16 Jan. 2017
Code:
[B]Replaced Camera2 with Snap: Enjoy all the functionalities of Sultan’s HAL![/B]
[B]Fixed HSR; Slow-Mo isn’t working yet.[/B]
Updated Camera Capabilities for a better HAL compatibility and features
[B]Updated Display-CAF with newer commits to fix the Split Screen issue[/B]
Fine tuned RT Scheduler priorities
[B]Enabled prefhint: (Layers are rendered faster now, resulting in a smoother experience)[/B]
Enabled “Moves” in Settings
[B]Fixed Face Unlock (Trusted Face)[/B]
09 Jan. 2017 -> 11 Jan. 2017
Code:
Changed kernel name for conformity (from -cyanogenmod to -bacon)
[B]Fixed USB tethering not working[/B]
Replaced Launcher2 with Launcher3 (Materialized version)
25 Nov. 2016 -> 09 Jan. 2017
Code:
Updated to 7.1.1_r13 (5 Jan. Security Patchset)
[B]ADDED SULTANXDA’S CAMERA HAL! Enjoy that sweet camera optimization
Enabled HSR (High speed recording). Slow-mo doesn’t work yet.[/B]
Added back Substratum, with improved functionalities and customization.
Updated bionic libraries to load shims correctly
[B]Enabled Night Mode
Enabled Storage Manager[/B]
Under-the-hood device optimization
05 Nov. 2016 -> 25. Nov 2016
Code:
[B]Updated to 7.0.0_r21 (5 Nov. Security Patchset)[/B]
Removed Music app
Removed Browser2 (WebView Shell) app
[B]Added Chromium [/B]
Updated audio: AOSPlusone now uses Google Nexus’s audio files.
[B]ENABLED MULTIROM COMPATIBILITY[/B]
[B]Updated Adreno libs to LA.BF.1.1.3_rb1.12 (from Onyx)[/B]
Updated Kernel to match CM-14.1 sources
[B]Updated Substratum to OMS7 [/B]
Added reboot back to Power Menu
[B]Cleaned frameworks/av patchsets: restored some code from Nougat to improve security.[/B]
Enabled init.d/addon.d support
A bunch of other misc fixes
09 Oct. 2016 -> 05 Nov. 2016
Code:
[B]05 Nov. 2016[/B]
Added On-Screen NavBar and HW Keys customization (Settings -> Buttons)
Fixed vulnerability for Dirty COW exploit
Android 7.0.0_r14
Sync’d Kernel with CM14.1 sources
Fixed Bluetooth MAC
Enabled SystemUI tuner hidden options
Fixed Snapchat with on-screen buttons
Added Swipe Libs for AOSP Keyboard
Added Nexus/Pixel Bootanimation
Updated Adreno Blobs to lastest source (HTC M8 MRA58K Update)
Fixed Gapps F/C after first flashing
Added SuperSU to settings (You still need to flash it)
Updated Substratum

Reserved (FAQ)
Q: Plz add feature "X"
No. Just no. If it isn't in AOSP, it won't be added. Please stop asking. If you want themes there's substratum, for anything else XDA is full of mods and stuff. Just use the search button.
You can find more stuff in the "Themes and Apps" section.
Q: This thing is broken, please fix.
Please do not report bugs and issues this way. Attach to your message a log (dmesg or logcat, last_kmsg if it reboots) and if you can, the steps to replicate the issue. This way you help the dev track down bugs quicker.
Please don't report if you're on a different kernel or have mods installed.
Q: I've fixed stuff, how can I help?
Cool! Just submit a pull request on my repo or contact me via Hangouts.

Another Nougat rom, downloading right now, thanks!
Just a question: Is it compatible with multirom?

mustang_ssc said:
Another Nougat rom, downloading right now, thanks!
Just a question: Is it compatible with multirom?
Click to expand...
Click to collapse
Haven't tested yet, as I don't have MultiROM. But it should work just fine, if you apply the same modifications as the ones on Updateing's post.

Wow great concept! Everything I ever wanted from a ROM AOSP + Substratum. Nothing else
Hope you can enable SE-Linux soon

works theme ? some screenshots

Awesome! This is everything I wanted from a rom. Clean, with very minimal system level modifications.

beatbrot said:
Wow great concept! Everything I ever wanted from a ROM AOSP + Substratum. Nothing else
Hope you can enable SE-Linux soon
Click to expand...
Click to collapse
That'll take time, but we all hope to have that soon. I'm just not very good at writing SELinux policies haha
SirSoviet said:
Awesome! This is everything I wanted from a rom. Clean, with very minimal system level modifications.
Click to expand...
Click to collapse
I hope I can hit where OxygenOS didn't...
EDIT: Gah I forgot to add Substratum's App! But masquerade is installed, so you can get the app from the play store in the meanwhile, i'll make sure to add it in the next build.

Does this use AOSP's original camera blobs or Sultan's modified ones?

Spider-Vice said:
Does this use AOSP's original camera blobs or Sultan's modified ones?
Click to expand...
Click to collapse
CM. I've tried Sultan's, but I still need to work on his kernel.. A few incompatibilities.

Great!! Is it necessary a full wipe if I come from updateing's build?

capitanouncino said:
Great!! Is it necessary a full wipe if I come from updateing's build?
Click to expand...
Click to collapse
Shouldn't be needed, but I'd recommend a clean install. Make a backup first if you're going for a dirty flash.

And new Nougat for opo. I think this device is not gonna die for 2 years you guys are awesome. Thanks..

Any bugs encountered yet? Other than the issues stated in the OP
Sent from my OnePlus One using XDA Labs

C4SCA said:
Any bugs encountered yet? Other than the issues stated in the OP
Sent from my OnePlus One using XDA Labs
Click to expand...
Click to collapse
Currently setting it up..Pico TTS crashed once (and only once, so veeeerrry minor). I'll edit the post if i find more bugs
Edit 1: Whenever I tried to setup whatsapp without profile picture, it got into a endless loop. However, adding a picture and then removing it via settings worked just fine. (This is probably just a whatsapp-thing as I am also whatsapp-beta-tester)

beatbrot said:
Currently setting it up..Pico TTS crashed once (and only once, so veeeerrry minor). I'll edit the post if i find more bugs
Edit 1: Whenever I tried to setup whatsapp without profile picture, it got into a endless loop. However, adding a picture and then removing it via settings worked just fine. (This is probably just a whatsapp-thing as I am also whatsapp-beta-tester)
Click to expand...
Click to collapse
Pico TTS crashes on my side too. Gapps issue I guess.
WhatsApp works fine here. (Stable, not beta)

Shouldn't this be in android development?

rudolf895 said:
Shouldn't this be in android development?
Click to expand...
Click to collapse
+1

The GPS issue is solved then? Have been using the OPO as my primary driver, and it was near impossible to use ride hailing services and google maps with the last few builds.

[ROM] LineageOS 12.1 for Z Ultra with current Sec.Patches

Hi,
this thread is dedicated to keep the LineageOS (former Cyanogen Mod) version 12.1 (Android 5.1.1) with current security patches alive .
Code:
# Your warranty is now void.
#
# I am not responsible for bricked devices, dead SD cards,
# thermonuclear war, or you getting fired because the alarm app failed. Please
# do some research if you have any concerns about features included in this ROM
# before flashing it! YOU are choosing to make these modifications, and if
# you point the finger at me for messing up your device, I will laugh at you.
This is not my work!
I'll just build it for our Z Ultra. You can find the original thread here:
LineageOS 12.1 for Xperia Z1 compact.
All thanks goes to the contributors
MSe1969, Micha_Btz, hahnjo, derf elot
Features
Based on LineageOS sources (former CyanogenMod), branch 'cm-12.1'
Rebranded to LineageOS
Current Android security fixes included
Kernel 3.4.113 including Android Security Bulletin patches
Privacy Browser as replacement of outdated AOSP Browser
Removed Cyngn-Tracking and Google-dependencies (same as LineageOS)
Support for microG available under development options
Current Android System Webview
Enhanced Privacy Guard: Own switches for Wi-Fi scan, clipboard, notifications and vibrate
Renewed CA certificates from AOSP master branch
Use Cloudflare DNS 1.1.1.1 as default fallback (instead of Google)
Download:
LineageOS 12.1 for Z Ultra Builds Folder
Source Code:
https://github.com/cm12-amami
https://github.com/colarus/local_manifests

Changelogs:
Code:
[B]FINAL build[/B]
lineage-12.1-20201116-UNOFFICIAL-togari.zip
- ASB November 2020 patches (sec. string 2020-11-05)
- Addl. fix of CVE-2019-2306
- Addl. fix of CVE-2020-15999
- System Webview on 86.0.4240.185
lineage-12.1-20200928-UNOFFICIAL-togari.zip
Changelog:
- Security string 2020-09-05
- Kernel upstream patches
- Webview updated to 85.0.4183.101
- Privacy Browser updated to version 3.5.1
lineage-12.1-20200615-UNOFFICIAL-togari.zip
Changelog:
- Sec. string 2020-06-05
- Ported missing CVE-2020-0096 ("Strandhogg") from May ASB
- Webview updated to 81.0.4044.138
lineage-12.1-20200518-UNOFFICIAL-togari.zip
Changelog:
- ASB May 2020 patches (sec. string 2020-05-05)
- System Webview on 81.0.4044.117
lineage-12.1-20200317-UNOFFICIAL-togari.zip
Changelog:
- Security string 2020-03-05 (includes kernel fixes from Feb. and March)
- System Webview on 80.0.3987.132
lineage-12.1-20200224-UNOFFICIAL-togari.zip
Changelog:
- Security string 2020-02-01 (this time no kernel updates)
- Webview on 79.0.3945.136
lineage-12.1-20200127-UNOFFICIAL-togari.zip
Changelog:
- Security string 2020-01-05
- Privacy Browser updated to 3.3
- System Webview on 79.0.3945.116
lineage-12.1-20191220-UNOFFICIAL-togari.zip
Changelog:
- Security string 2019-12-05
- System Webview 78.0.3904.108
- Kernel: Amongst several patches, backported CVE-2019-2215 from October 2019 ASB
- Skipped CVE-2019-2212 from ASB 2019.11 included
- Skipped CVE-2019-2196/CVE-2019-2198 from ASB 2019.11 included
- Skipped CVE-2019-2117 from ASB 2019.07 included
- DownloadProvider part of CVE-2018-9493 from ASB 2018.10 now also included
lineage-12.1-20190911-UNOFFICIAL-togari.zip
Changelog:
- ASB September 2019 patches (sec. string 2019-09-05)
- Implemented CVE-2018-20346 (aka "Magellan"), which was outstanding from March 2019 ASB
- Implemented CVE-2019-2031 outstanding from April 2019 ASB
- Webview updated to 76.0.3809.111
lineage-12.1-20190819-UNOFFICIAL-togari.zip
Changelog:
- August 2019 ASB patches (sec. string 2019-08-05)
- Additional (backported) security patches from AOSP branch 'nougat-mr2-security-release'
- Privacy Browser updated to version 3.2
- SetupWizard rebranded to LineageOS
lineage-12.1-20190710-UNOFFICIAL-togari.zip
Changelog:
- ASB July 2019 patches
- System Webview updated to 75
lineage-12.1-20190619-UNOFFICIAL-togari.zip
Changelog:
- ASB June 2019 patches (sec. string 2019-06-05)
- Privacy Browser updated to version 3.1
- System Webview updated to 74.0.3729.157
- Included CVE-2017-0554 and CVE-2017-0840
lineage-12.1-20190513-UNOFFICIAL-togari.zip
Changelog:
- ASB Security patches May 2019 (sec. string 2019-05-05)
- Privacy Browser updated to version 3.0.1
- Android System Webview updated to M74
- Missing CVE-2017-0554 and CVE-2017-0840 have been backported and included
lineage-12.1-20190429-UNOFFICIAL-togari.zip
Changelog:
- ASB April 2019 patches (sec. string 2019-04-05)
- Privacy Browser updated to version 2.17.1
lineage-12.1-20190320-UNOFFICIAL-togari.zip
Changelog:
- ASB March 2019 patches (sec. string 2019-03-01)
- Privacy Browser updated to version 2.17
- Android System Webview updated to 72.0.3626.121 (includes CVE-2019-5786)
[B]Build broken, don't use it![/B]
[STRIKE]lineage-12.1-20190214-UNOFFICIAL-togari.zip
Changelog:
- ASB February 2019 patches (sec. string 2019-02-05)
- Privacy Browser updated to version 2.16
- Fix of carrier display of Telefonica Germany, part 2 (thanks to @awl14)
- Kernel: Additional 'spectre' mitigations[/STRIKE]
lineage-12.1-20190114-UNOFFICIAL-togari.zip
Changelog:
- January android security patches (sec. string 2019-01-05)
- Android System Webview updated to M71 (71.0.3578.99)
- Privacy Browser updated to 2.15.1
- Fix of Telefonica Germany carrier display
- Package usage stats switched off by default
lineage-12.1-20181216-UNOFFICIAL-togari.zip
Changelog:
-Security String 2018-12-05 (December 2018 Android security bulletin, back-ported applicable patches)
-Fix of the 'adb root' bug, as announced on the LineageOS site
-Found and implemented a backport of CVE-2017-15835 fix (Pixel/Nexus bulletin 11.2018, Qualcomm comp.)
-Implemented fixes for CVE-2018-9531, CVE-2018-9536, CVE-2018-9537, which were listed in the November 2018 ASB as applicable for Android 9 only (but they also apply to lower releases)
lineage-12.1-20181110-UNOFFICIAL-togari.zip
Changelog:
- Security string 2018-11-05
- Android System Webview updated to 69.0.3497.109
- The patch level info in the Settings emphasizes now the unofficial character (since there are no official patches any more for Android 5 since a couple of months)
lineage-12.1-20180910-UNOFFICIAL-togari.zip
Changelog:
- Security string 2018-09-05
lineage-12.1-20180815-UNOFFICIAL-togari.zip
Changelog:
- Security string 2018-08-05
- Privacy Browser 2.12
lineage-12.1-20180718-UNOFFICIAL-togari.zip
Changelog:
- Security string 2018-07-05
- Android System Webview M67
- Privacy Browser 2.11
- Additional kernel fixes f. CVE-2018-1092 / CVE-2018-1093
lineage-12.1-20180626-UNOFFICIAL-togari.zip
Changelog:
- Security string 2018-06-05
- Privacy Browser updated to V2.10
- Privacy-focused default setting (only at clean install): Hide sensitive information on lock screen
lineage-12.1-20180603-UNOFFICIAL-togari.zip
Changelog:
- Security string 2018-05-05
- Android System Webview M66 (stable)
- Privacy Browser updated to V2.9
- Use Cloudflare DNS 1.1.1.1 as default fallback (instead of Google's 8.8.8.8)
- Further fix for the "Ask" topic in Privacy Guard to mimic the defined behavior
lineage-12.1-20180502-UNOFFICIAL-togari.zip
Changelog:
- ASB 04/2018
- M65 for system webview
- telephony patch, still need another fix related to [URL="https://review.lineageos.org/210741"]https://review.lineageos.org/210741[/URL]
lineage-12.1-20180314-UNOFFICIAL-togari.zip
Changelog:
- March 2018 android security bulletin (security string 2018-03-05)
- Android System Webview updated to M64
- Renewed CA-certificates from AOSP master branch
- Privacy Browser updated to version 2.8.1
lineage-12.1-20180214-UNOFFICIAL-togari.zip
Changelog:
- February 2018 android security bulletin (security string 2018-02-05)
- Applied CVE-2017-13218, listed in the January ASB as mitigation against "Spectre/Meltdown"
- Applied many past bulleting patches marked as "not publicly available"
- Enhanced Privacy Guard: dedicated switches for WiFi scan, clipboard access, notification access and vibration
lineage-12.1-20180121-UNOFFICIAL-togari.zip
Changelog:
- Security string 2018-01-05
- Webview switched to stable M63 (from M64 beta)
- SQLite "secure delete" feature enabled
cm-12.1-20171215-UNOFFICIAL-togari.zip
Changelog:
- Security string 2017-12-05
- Privacy Browser updated to 2.7.2
- Backported patches from LineageOS 13 for su (root application)
cm-12.1-20171124-UNOFFICIAL-togari.zip
Changelog:
- 6th Nov. sec. Level
cm-12.1-20171024-UNOFFICIAL-togari.zip
Changelog:
- still 5th Oct. sec. Level
- fix for WiFi KRACK attack
- android system webview has been updated to M64
cm-12.1-20171008-UNOFFICIAL-togari.zip
Changelog:
- patches for October
cm-12.1-20170927-UNOFFICIAL-togari.zip
Changelog:
- patches for September
cm-12.1-20170828-UNOFFICIAL-togari.zip
Changelog:
- patches for August ASB
cm-12.1-20170719-UNOFFICIAL-togari.zip
Changelog:
- Current Android security fixes included (5th July)
- Kernel 3.4.113 including Android Security Bulletin patches
- Privacy Browser as replacement of outdated AOSP Browser
- Removed Cyngn-Tracking and Google-dependencies (same as LineageOS)
cm-12.1-20170614-UNOFFICIAL-togari.zip
Changelog:
- ASB June patches (sec. string 2017-06-05)
- Android System Webview updated to most current M59
- Replaced old (and insecure) Browser app with Privacy Browser
cm-12.1-20170525-UNOFFICIAL-togari.zip
Changelog:
- Patchlevel 5. May 2017
- LOS Bootanimation
cm-12.1-20170520-UNOFFICIAL-togari.zip
Changelog:
-Patchlevel 5. April / most(?) Patches May
cm-12.1-20170406-UNOFFICIAL-togari.zip
Changelog:
-Security Patch Level 5. March 2017:

New Build (cm-12.1-20171215-UNOFFICIAL-togari.zip) is up!
Changelog:
- Security string 2017-12-05
- Privacy Browser updated to 2.7.2
- Backported patches from LineageOS 13 for su (root application)

Thank you very much for this love and support.
I'll flash it right away. Is it possible to port lineage os 13 for our ultra?

AmeyDude said:
Thank you very much for this love and support.
I'll flash it right away. Is it possible to port lineage os 13 for our ultra?
Click to expand...
Click to collapse
It is imposible for me, cause I am not a developer. Can't change anything.
I'm only a noob who builds form others sources.

Proximity sensor not working
When dialing the screen goes black - even when the phone is not at my head. I can't operate it any more, e.g. it is impossible to hang up the call. This is a common problem also for Nougat ROMs. Con this be fixed here?

doc martin said:
When dialing the screen goes black - even when the phone is not at my head. I can't operate it any more, e.g. it is impossible to hang up the call. This is a common problem also for Nougat ROMs. Con this be fixed here?
Click to expand...
Click to collapse
This is not a nougat rom so its not affected by bugs from it
Your sensor can have become unplugged as many of us here discovered including me
https://forum.xda-developers.com/xp...olution-proximity-sensor-fix-z-ultra-t3595525
https://forum.xda-developers.com/xp...een-started-off-calls-regardless-rom-t3536343

SUPERUSER said:
This is not a nougat rom so its not affected by bugs from it
Your sensor can have become unplugged as many of us here discovered including me
https://forum.xda-developers.com/xp...olution-proximity-sensor-fix-z-ultra-t3595525
https://forum.xda-developers.com/xp...een-started-off-calls-regardless-rom-t3536343
Click to expand...
Click to collapse
Hey! You saved my day! :good:
A tiny piece of plastic pushed underneath the connector fixed it.

@colarus
Great rom , thanks for building it , its working really good , never felt my ZU so fast
Please continue with the updates ! Really appreciate it

is anything can be done about camera quality? it's noticeably worse than on stock. rom is fast and great, btw.

pvillasuso said:
@colarus
Great rom , thanks for building it , its working really good , never felt my ZU so fast
Please continue with the updates ! Really appreciate it
Click to expand...
Click to collapse
Thank you very much.
As long as the great developers of the Z1 Compact ROM provide updates, I will try to build updates for the Z Ultra. :good:

Gread and fast ROM
Thank you for this ROM, my ZUltra run smooth and fast. Thank's for this job!

Hey how to flash Sony z ultra

Apekt said:
Hey how to flash Sony z ultra
Click to expand...
Click to collapse
Please use the search function of the forum:
- Unlock Bootloader
- Install TWRP Recovery
- FULL WIPE in Recovery
- Install Rom ZIP
- Install GAPPS
- Reboot

New Build is up!
lineage-12.1-20180121-UNOFFICIAL-togari.zip
MSe1969 said:
...
New in this version:
Security string 2018-01-05
Webview switched to stable M63 (from M64 beta)
SQLite "secure delete" feature enabled
Two remarks:
"Meltdown/Spectre": The CVE-2017-13218 patch announced by Google, "which helps limits side channel attacks", is not yet implemented, we have to properly test that one for side effects first. Besides, the information given here is not entirely clear whether the Krait CPU of our device is affected or not, however - for the benefit of doubt, we assume so.
We are working on getting many kernel patches applied, which are/were flagged as "not publicly available" (so is also CVE-2017-13218) in the last security bulletins - so the next release will bring a couple of additional kernel patches
For those of you building from source, the test branch will soon be merged into the stable branch 'cm-12.1'
Regards, M.
Click to expand...
Click to collapse

How stable is this rom? Any bugs?

salevdns said:
How stable is this rom? Any bugs?
Click to expand...
Click to collapse
My opinion is its the most stable lollipop rom I've used long-term.
If you execute fstrim once per day it stays very fast.
I have had only two random reboots both in a critical time but I got it up and running within a minute.
As mentioned before its cm/lineage based so camera is a thing to be aware of.
Let the phone execute camera workaround app on boot. Don't touch the screen for a second or two or the camera might not work.
If the camera freezes when in use you can usually exit the app and relaunch it and its good to go.

New Build is up!
lineage-12.1-20180214-UNOFFICIAL-togari.zip
MSe1969 said:
...
This build includes the following features:
February 2018 android security bulletin (security string 2018-02-05)
Applied CVE-2017-13218, listed in the January ASB as mitigation against "Spectre/Meltdown"
Applied many past bulleting patches marked as "not publicly available"
Enhanced Privacy Guard: dedicated switches for WiFi scan, clipboard access, notification access and vibration
The changes in detail
As announced last month, we have in addition looked systematically for patches in past android security bulletins, which were flagged as "not publicly available" and were able to find around 70 additional patches for our kernel, which we have applied, next to a few other missing patches from miscellaneous other repositories.
We have also applied CVE-2017-13218, which was listed by Google in the January 2018 bulletin as mitigation for the "Spectre / Meltdown" set of vulnerabilities (quote: "reduces access to high-precision timers, which helps limits side channel attacks (such as CVE-2017-5715, CVE-2017-5753, and CVE-2017-5754) of all known variants of ARM processors."). We are still not sure, whether "Spectre / Meltdown" are applicable to the CPU of our device, but the implemented patch is part of the upstream kernel, so it makes sense anyway.
We have enhanced the Privacy guard and made the scan for Wi-Fi networks an own switch, which will be prompted by the system. In Android 5, different from later releases, this activity is not bound to the coarse location permission and could so far be obtained independently by user apps. Further enhancements of the privacy guard allow now to restrict access to the clipboard, the notifications and also remove the vibrate activity from apps.
...
Click to expand...
Click to collapse

Wow! Previos build was very stable for me. Thank's a lot for you job.:good:

Thanks a lot for this build. I recently using resurrection remix 5.1.1 it was working awesome with stable battery and performance. This ROM is also working awesome and those latest patch for kernel I loved it. Thank you so much.

Mentioned patchlevel versus added patches

Some companies mention the latest patchlevel on our phone (info phone -> software) but "forget" to update all the patches. The firm security research lab looked into this problem.
https://www.wired.com/story/android-phones-hide-missed-security-updates-from-you/
Snoopsnitch is an app that checks if all patches before the mentioned patchlevel (date) are up to date.
For the J5 (2016) SM-J510FN only 7 out of 110 patches are inconclusive and 3 patches are missing. Don't know , but mostly it will be about deleted features if the numbers are that low.

[ROM][J510xx][TW-7.1.1][v2.0] SEP 8.5 Lite, a Galaxy J2 (2018) ROM

Changelog:
v2.0 - 2018-12-26:
- Updated Port version to J250YXXS2ARK1 (OMC)
- Updated Base version to J510FNXXU2BRJ4 (NEE)
- New security patch level 2018-11-01
- Merged additional CSC into OMC (CAM, THL, XME and XXV)
- Reworked troubleshoot options
- Introduced Night Light
- Removed Blue light filter
- Patched OMC to make most of CSC dependent features working on all CSC codes
- Search bar in quick settings
- Other under the hood improvements
v1.5.1 - 2018-10-02:
- Fixed booting issues
v1.5 - 2018-09-24:
- New Port version J250MUBS4ARH4 (OMC)
- New security patch level 2018-08-01
- Enhanced Troubleshoot options
- New debloat option in aroma installer
- Added Custom CSC feature (v2.0)
- Other under the hood improvements
- Removed NFC from Non-NFC variants
- Updated RIL libs for J510H variant
v1.0 - 2018-07-26:
- Initial release
F.A.Q
Q: How to root it?
A: Grab Magisk from here.
Q: Splash screen gets more and more greenish when I try to boot. Is that normal?
A: Of course not. This means you're not on Marshmallow/Nougat bootloader & Modem. Flash any MM/NN stock ROM first before you flash this ROM.
Q: ROM booted but there is no gallery, clock etc. Why did you removed it?
A: I didn't, YOU debloated them in aroma installer. Reflash the ROM again without wiping data and this time don't debloat them.
Q: There is no CSC folder in /system. How to add CSC features?
A: This ROM is featured with OMC, a new multi CSC solution. Locate to /system/omc and add your features to customcsc.xml.
Q: My GPS does not find my location. Any fix?
A: Download GPS Test app from Google play, run it, go outside and wait 10 minutes.
Q: Do I have to clean flash when there is a new update?
A: No, flash it over a previous version is ok.
Q: XYZ app does not work/force closes and I want create a log to help you. How can I create a logcat?
A: I'm glad you'd like to help. Follow this xda tutorial or download any logcat app from Google Play.
Q: Why still no Oreo or Pie port?
A: Samsung won't update any MSM8916 device to Oreo/Pie anymore.
Q: Why I can't enable 4G in second SIM?
A: Galaxy MSM8916 modems don't support dual LTE.
Q: Do I have to flash Galaxy J2 2018 mods, recoveries etc. when I use this ROM?
A: NO! This ROM will not transform your Galaxy to an J2. Only flash mods, recoveries etc. meant for your device variant.

Smart view in this rom?

duduaxe said:
Smart view in this rom?
Click to expand...
Click to collapse
J2 2018 does not support Smart View, so this ROM won't support it as well
Sent from my SM-A530F using XDA Labs

Good to finally see a lightweight TW rom. I will report if i notice anything. (Example: Performance Drops etc.)

Ok i continued a normal version this rom
I like this smart view play the games

Very nice and lite rom, battery friendly.

I didn't find any bugs exept blue light filter (which i don't need)
I still have a request though could you add in a option in aroma to change the model number to SM-J510FN ?

Flegmon said:
I didn't find any bugs exept blue light filter (which i don't need)
I still have a request though could you add in a option in aroma to change the model number to SM-J510FN ?
Click to expand...
Click to collapse
There won't be any modification options in aroma to keep ROM Lite.
If you want to change model no. to SM-J510FN, edit the following lines in build.prop from:
Code:
ro.build.flavor=j2y18ltexx-user
ro.product.model=SM-J250Y
ro.build.product=j2y18lte
ro.product.name=j2y18ltexx
ro.product.device=j2y18lte
to
Code:
ro.build.flavor=j5xnltexx-user
ro.product.model=SM-J510FN
ro.build.product=j5xnlte
ro.product.name=j5xnltexx
ro.product.device=j5xnlte
or edit ro.product.model=XXXXXXXX only to SM-J510FN.
I'm not sure but this may break some features which are meant for J250xx only.

Can you add capture screen(and screen recorder in this rom)?

N1ck31 said:
Can you add capture screen(and screen recorder in this rom)?
Click to expand...
Click to collapse
I won't add more features or I have to remove that "Lite" from the title. If you want more features, try SEP 8.5 (A8) ROM.

Great rom nice to have something different i.e from J2 2018.Performance super smooth and fast.Sound is great and plenty of features for a lite rom.Just perfect all round.Thanks for another great rom.

Finsnevis said:
Great rom nice to have something different i.e from J2 2018.Performance super smooth and fast.Sound is great and plenty of features for a lite rom.Just perfect all round.Thanks for another great rom.
Click to expand...
Click to collapse
Glad to hear that

Android go edition
Hello, can you port samsung j2 core (android go edition) for samsung j5 2016 user?
I hope you can grant my request
this video samsung j2 core (android go edition) check PM

cloning45 said:
Hello, can you port samsung j2 core (android go edition) for samsung j5 2016 user?
I hope you can grant my request
this video samsung j2 core (android go edition) check PM
Click to expand...
Click to collapse
ok now I got it, I mean your PM
It's not possible to port Android (8.1.0) Go from J2 Core to J5 2016 as both devices have different SoC chip and Android versions

Hello.
I'm running a J510MN. My procedures were: Flashed the original Samsung firmware through Odin, then flashed TWRP through Odin as well, on TWRP i did a full wipe (Dalvik, data, internal storage, cache, system and external_SD), then i moved the installation files to my SD Card and went to install it. Aroma reports "Compatibility check failed".
Here's the log. Cheers:
Code:
AROMA INSTALLER version 3.00
(c) 2013-2015 by amarullz.com
ROM Name : SEP 8.5 Lite, J2 (2018) ROM
ROM Version : v1.0
ROM Author : xXPR0T0TYPEXx
Device : Galaxy J5 2016
Start at : Wed Dec 31 21:32:50 1969
Checking for device compatibility first...
package_extract_file: no sep85/scripts/other/errorstatus.sh in package
about to run program [/tmp/errorstatus.sh] with 1 args
SEP 8.5 ROM aroma error report:
Errormessage: Can't read method 'is_substring(substring, string)' or device not supported
abandoning installation...
script aborted: <#ff0000>Device compatibility FAILED:
This ROM is for J510F/FN/FQ/GN/H/MN/UN only!<#ff0000></#>
Please check SEP 8.5 ROM Lite xda thread for further information
No changes were made in system...
<#ff0000>Device compatibility FAILED:
This ROM is for J510F/FN/FQ/GN/H/MN/UN only!<#ff0000></#>
Please check SEP 8.5 ROM Lite xda thread for further information
No changes were made in system...
Installer Error (Status 7)
End at : Wed Dec 31 21:32:50 1969

KruxConcept said:
Hello.
I'm running a J510MN. My procedures were: Flashed the original Samsung firmware through Odin, then flashed TWRP through Odin as well, on TWRP i did a full wipe (Dalvik, data, internal storage, cache, system and external_SD), then i moved the installation files to my SD Card and went to install it. Aroma reports "Compatibility check failed".
Here's the log. Cheers:
Code:
AROMA INSTALLER version 3.00
(c) 2013-2015 by amarullz.com
ROM Name : SEP 8.5 Lite, J2 (2018) ROM
ROM Version : v1.0
ROM Author : xXPR0T0TYPEXx
Device : Galaxy J5 2016
Start at : Wed Dec 31 21:32:50 1969
Checking for device compatibility first...
package_extract_file: no sep85/scripts/other/errorstatus.sh in package
about to run program [/tmp/errorstatus.sh] with 1 args
SEP 8.5 ROM aroma error report:
Errormessage: Can't read method 'is_substring(substring, string)' or device not supported
abandoning installation...
script aborted: <#ff0000>Device compatibility FAILED:
This ROM is for J510F/FN/FQ/GN/H/MN/UN only!<#ff0000></#>
Please check SEP 8.5 ROM Lite xda thread for further information
No changes were made in system...
<#ff0000>Device compatibility FAILED:
This ROM is for J510F/FN/FQ/GN/H/MN/UN only!<#ff0000></#>
Please check SEP 8.5 ROM Lite xda thread for further information
No changes were made in system...
Installer Error (Status 7)
End at : Wed Dec 31 21:32:50 1969
Click to expand...
Click to collapse
Did you let the original samsung firmware boot up first then in developer options enable OEM unlock then flash twrp preferably with 3.1.1.0 and no need whatsoever to delete ext sd card.Especially if you deleted it prior to flashing the rom.How is TWRP going to work if you deleted internal and external storage?The rom is on external storage.Don"t delete ext storage and you don't even need to delete internal all you need is 4 wipes dalvike data system and cache I got it installed on FN with that no problem.And have a look at that last line on your script december and 1969.You don't have the twrp set up properly because your rom is not set up properly i.e.the custom firmware you flashed through odin.I would advise to let the stock firmware boot up first and then you take twrp backup of stock rom in case you need to recover it.Then flash this rom with the right time and region settings which you can set in twrp first before flashing this rom

KruxConcept said:
Hello.
I'm running a J510MN. My procedures were: Flashed the original Samsung firmware through Odin, then flashed TWRP through Odin as well, on TWRP i did a full wipe (Dalvik, data, internal storage, cache, system and external_SD), then i moved the installation files to my SD Card and went to install it. Aroma reports "Compatibility check failed".
Here's the log. Cheers:
Code:
AROMA INSTALLER version 3.00
(c) 2013-2015 by amarullz.com
ROM Name : SEP 8.5 Lite, J2 (2018) ROM
ROM Version : v1.0
ROM Author : xXPR0T0TYPEXx
Device : Galaxy J5 2016
Start at : Wed Dec 31 21:32:50 1969
Checking for device compatibility first...
package_extract_file: no sep85/scripts/other/errorstatus.sh in package
about to run program [/tmp/errorstatus.sh] with 1 args
SEP 8.5 ROM aroma error report:
Errormessage: Can't read method 'is_substring(substring, string)' or device not supported
abandoning installation...
script aborted: <#ff0000>Device compatibility FAILED:
This ROM is for J510F/FN/FQ/GN/H/MN/UN only!<#ff0000></#>
Please check SEP 8.5 ROM Lite xda thread for further information
No changes were made in system...
<#ff0000>Device compatibility FAILED:
This ROM is for J510F/FN/FQ/GN/H/MN/UN only!<#ff0000></#>
Please check SEP 8.5 ROM Lite xda thread for further information
No changes were made in system...
Installer Error (Status 7)
End at : Wed Dec 31 21:32:50 1969
Click to expand...
Click to collapse
Flash with TWRP v3.1.1

Changelog v1.5:
- New Port version J250MUBS4ARH4 (OMC)
- New security patch level 2018-08-01
- Enhanced Troubleshoot options
- New debloat option in aroma installer
- Added Custom CSC feature (v2.0)
- Other under the hood improvements
- Removed NFC from Non-NFC variants
- Updated RIL libs for J510H variant
Note: Factory reset recommend as new port (J250M) version isn't same base as previous version (J250Y)
Download v1.5: AndroidFileHost
OP updated

xXPR0T0TYPEXx said:
Changelog v1.5:
- New Port version J250MUBS4ARH4 (OMC)
- New security patch level 2018-08-01
- Enhanced Troubleshoot options
- New debloat option in aroma installer
- Added Custom CSC feature (v2.0)
- Other under the hood improvements
- Removed NFC from Non-NFC variants
- Updated RIL libs for J510H variant
Note: Factory reset recommend as new port (J250M) version isn't same base as previous version (J250Y)
Download v1.5: AndroidFileHost
OP updated
Click to expand...
Click to collapse
Stuck in bootloop and sometimes the phone turns itself off when booting. I got that dark-green say updating apps but then the phone turned off.
I have a J5 2016 510FN with twrp 3.1.1

[UNOFFICIAL][ROM]BETA LineageOS 18.1 GO for Galaxy Tab A [SM-T350] June 9, 2023

PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
9. camera
Thanks
1. LineageOS team for source code.
2. Pre alpha testers for the Samsung Tab A/E roms who provided valuable feedback: lpedia, Schaagi, katochwa, Henrick Grimler
3. nubianprince for helping fix audio over bluetooth on SM-T350 on 18.1.
4. Huge thanks to Henrick Grimler https://github.com/Grimler91 for helping me reproduce a major bug in 18.1 which led me to find a solution. Henrick also helped fine tune some of the sepolicy as well.
5. Sebastiano Barezzi https://github.com/SebaUbuntu for giving the msm8916 repo some 18.1 code updates in March 2021.
6. Exynos5420 team for sharing it's knowledge in building roms.
7. msm8916 team for their repos
8. dylux for suggesting a fix for the front camera photo/record crashing by using stock SM-T350 media_profiles.xml.

FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2020 to March 2021 running into bug after bug. The least you can do is spend a few minutes reading everything before posting.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
GitHub - Galaxy-MSM8916/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.
MSM8916/MSM8929/MSM8939 kernel for Samsung devices. - GitHub - Galaxy-MSM8916/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.
github.com
The device tree files are at
GitHub - retiredtab/android_device_samsung_msm8916-common: Common MSM8916 tree for Samsung devices
Common MSM8916 tree for Samsung devices. Contribute to retiredtab/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
GitHub - retiredtab/device_samsung_gt58wifi
Contribute to retiredtab/device_samsung_gt58wifi development by creating an account on GitHub.
github.com
GitHub - retiredtab/device_samsung_gte-common at lineage-18.1
Contribute to retiredtab/device_samsung_gte-common development by creating an account on GitHub.
github.com
The vendor tree files are at
GitHub - retiredtab/vendor_samsung_msm8916-common
Contribute to retiredtab/vendor_samsung_msm8916-common development by creating an account on GitHub.
github.com
GitHub - retiredtab/android_vendor_samsung_gt58wifi
Contribute to retiredtab/android_vendor_samsung_gt58wifi development by creating an account on GitHub.
github.com
In addition, there is a repo diff file for device specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself.
Q2. Is this BETA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid March 2021 with no major issues.
Q3. What if my app, xyz, doesn't work?
A3. I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use TWRP 3.5.2_9. Get it from
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-11.0][v7.10][ANDROID 11] Galaxy Tab A 8.0
I am not responsible for bricked devices, or any other hardware malfunctions that comes as a result of flashing this ROM, Please do some research if you have any concerns about features included before flashing it, this ROM was built for the...
forum.xda-developers.com
Q6. Why should I use this rom?
A6. You don't. If you don't like this rom, then don't use it. Yes, it's that simple.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. Do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
Q10. Will you still build 17.1 for this device?
A10. Yes, for now, but I will probably discontinue building 17.1 at the end of 2021. I will likely be trying to build 19.0 once it's released so I don't want to maintain 3 releases.
Q11. Do I need to erase everything and format my data?
A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Q12. What gapps should I use?
A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary. It's reported that opengapps does no testing on their daily builds and some version results in bootloops, bitgapps may run out of disk space will installing apps and Mindthegapps as causing overall slowdown of the system.
The only recommendation I can make is to use the SMALLEST version of gapps which is PICO or equivalent naming convention. DO NOT use anything other than PICO. That is, do not use nano, mini, stock, etc.
If you are going to install gapps, flash the rom first, reboot into system/OS, reboot to recovery, flash gapps, reboot into system/OS. That is, do not flash/install the rom and gapps at the same time.
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
Q14. Why isn't my post answered?
A14. It's probably because it's answered in the FAQ or not relevant to the rom. Again, I do not run Windows OS or use gapps. Questions already answered in the FAQ will be completely ignored.
Q15. Can I turn off the on screen navigation keys?
A15. To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation. It's enabled by default because I find it useful. If you don't like it, you only need to disable once and your preference will be remembered. If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout
Q16. What speed up/optimization tips do you suggest?
A16.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
4. Use a web browser like Brave that has built in adblock and privacy features.
5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
6. Look for apps that are open source, ad free and lightweight.
Q17. Does this rom support Magisk?
A17. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.
Q18. Will this rom ever become official?
A18. Never. I don't want the responsibilities that come with being an official maintainer. In addition, I know my device trees, code organization and git commits will NOT meet LineageOS standards. Remember, I'm an unpaid volunteer doing this in my free time and sharing my work with you for free so you can get hundreds of hours of enjoyment from this tablet.
Q19. What is the difference between this rom and others?
A19. This rom tries to be pure LineageOS with little to no modifications. Other roms may have different UI, different bundled apps, etc. Use whatever meets your requirements.
Q20. Will there be any major 18.1 code modifications in the future?
A20. I don't anticipate any major modifications. There may be some slight tweaking to the sepolicy, small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 18.1 is working. Any major changes will be done in 19.0.
Q21. Why did you fork the device and vendor trees for 18.1?
A21. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.
In addition, since I'm building SM-T350, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not. I still have not figured out the best way to manage all my repos and it's a work in progress.
Q22. Can you build a variant of this device? For example, a LTE or S-pen version.
A22. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.
Q23. Can I load this rom on a variant devivce like LTE or S-pen version?
A23. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q24. Will this run on the SM-T355 or SM-P355?
A24. No. Someone has tried and it will result in a bootloop.
Q25. How do I know if I have a BOE panel?
A25. Some ST-350 tablets have a BOE display panel. In order for it to work with TWRP and any custom rom, you must have the correct bootloader installed on a BOE panel otherwise you will see a black/blank screen. To check to see if you have a BOE panel, open a terminal and
Code:
adb root
adb shell cat /proc/cmdline
The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,
mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none
There is a fix as documented at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
Q26. What is a GO build?
A26. A GO build uses less DRAM, disk space and supposed to be better suited for devices with 2GB DRAM or less. I have no idea whether it's true or not vs a NON GO build, but I figured I would try a GO build.
Some of the features removed in a GO build are documented in post #46 in this thread in addition to work profiles. If you need these features, you can edit a property in the build.prop as documented in post #49.
Q27. Okay, I understand the consequences and that this is BETA rom and willing to take the risks outlined, now where can I find the rom?
A27. Downloads are at
retiredtab - Browse /SM-T350/18.1 at SourceForge.net
sourceforge.net

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
June 9, 2023 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-06
2. Whatever LineageOS changed since last May release (about 5,500 files had to be recompiled).
May 7, 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-05
2. Whatever LineageOS changed since last Apr release (about 7,200 files had to be recompiled).
Apr 15, 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-04
2. Whatever LineageOS changed since last Mar release (about 28,000 files had to be recompiled).
March 20, 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-03
2. Whatever LineageOS changed since last Feb release (about 20,000 files had to be recompiled).
Feb 12, 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02
2. Whatever LineageOS changed since last Jan release (about 12,500 files had to be recompiled).
Jan 8, 2023 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
2. Whatever LineageOS changed since last Dec release (about 4,400 files had to be recompiled).
Dec 11, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
2. Whatever LineageOS changed since last Nov release (about 5,000 files had to be recompiled).
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
2. Whatever LineageOS changed since last Oct release (about 5,000 files had to be recompiled).
Oct 7, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
2. Whatever LineageOS changed since last Sept release (about 5,500 files had to be recompiled).
Sept 12, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Whatever LineageOS changed since last Aug release (about 12,500 files had to be recompiled).
Aug 5, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Whatever LineageOS changed since last July release (about 4,000 files had to be recompiled).
July 8, 2022 release notes
1. July 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
2. Whatever LineageOS changed since last June release (about 1,500 files had to be recompiled).
June 11, 2022 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
2. Whatever LineageOS changed since last May release (about 9,500 files had to be recompiled).
May 7, 2022 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
2. Whatever LineageOS changed since last April release (about 11,000 files had to be recompiled).
3. Selfie camera and video no longer crash with stock camera. Thanks to @dylux for suggesting these fixes which are commits
https://github.com/retiredtab/devic...mmit/c9ac11147f83d611e006731aad7c14108f293d64
and
https://github.com/retiredtab/devic...mmit/cfa55e0478b59821f3d16501104b51ceeef8b010
April 10, 2022 release notes
1. Arpil 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
2. Whatever LineageOS changed since last March release (about 11,000 files had to be recompiled).
Mar 12, 2022 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-03
2. Whatever LineageOS changed since last Feb release (about 5,700 files had to be recompiled).
Feb 12, 2022 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-02
2. Whatever LineageOS changed since last January release (about 34,500 files had to be recompiled).
Jan 20, 2022 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-01
2. Whatever LineageOS changed since last December release (about 10,000 files had to be recompiled).
Dec 10 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2021-12
2. Whatever LineageOS changed since last November release (about 11,000 files had to be recompiled).
Nov 7 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318560
2. I enabled zram swap with size 512MB. I noticed that the last couple of months that Clash Royale would crash/close and logs showed
Code:
10-28 14:26:01.412 0 0 I [2: kswapd0: 91] lowmemorykiller: Killing 'ell.clashroyale' (6730), adj 0,
Hopefully, by enabling zram, that will stop Clash Royale from crashing/closing.
Zswap is enabled on stock Nougat SM-T350 (part of the Samsung Tab A/E family that uses same msm8916 kernel code)
https://github.com/retiredtab/andro...mmit/2a6bf385e6dfe6073fe328b7b1c563ccd60a5ede
https://github.com/retiredtab/andro...mmit/438d5d3ad20cbc98f0f8c18eb610b6268de19395
This code uses the in kernel low memory killer (lmk). I tried using the Android OS lmk, but it doesn't work very well and shows this in the log.
Code:
E lowmemorykiller: /proc/zoneinfo parse error
E lowmemorykiller: Failed to get free memory!
3. Whatever LineageOS changed since last Oct release (about 7,200 files had to be recompiled). One of these changes has removed the built in terminal program from LineageOS as AOSP deprecated this app as per
https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/304043
Oct 10 release notes
1. Oct 1 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317001
2. Added https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/316839 to fix landscape mode system UI. This patch is not yet officially merged as of Oct 10 release.
3. Whatever LineageOS changed since last September release (about 6,100 files had to be recompiled).
Sept 10 release notes
1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
3. Whatever LineageOS changed since last August release (about 6,200 files had to be recompiled).
Aug 8 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
3. Whatever LineageOS changed since last July release (about 11,500 files had to be recompiled).
4. 18.1 continues to be my daily driver since March 2021.
July 10 release notes
1. Initial public release to XDA. This is an ALPHA build.
2. July 5 security patches as per https://review.lineageos.org/q/topic:"android-11.0.0_r39"+(statuspen OR status:merged)

Reserved.

New build called lineage-18.1-20210718-UNOFFICIAL-gt58wifi.zip
July 18 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added
Code:
allow hal_health_default sysfs_charger:dir search;
allow hal_health_default sysfs_charger:file r_file_perms;
to the hal_health_default.te file.
Other than that, there are no other changes. So if you already downloaded the July 10 release and don't mind this small bug, you can wait until the August security patches before updating the rom. The August security patches and all future versions will have this bug fix incorporated.

New build called lineage-18.1-20210808-UNOFFICIAL-gt58wifi.zip
Aug 8 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
3. Whatever LiineageOS changed since last July release (about 11,500 files had to be recompiled).
4. 18.1 continues to be my daily driver since March 2021.

@retiredtab
Thanks for your work on this rom. It's been working very well.

It seems BiTGApps can no longer be downloaded.

ovalseven said:
It seems BiTGApps can no longer be downloaded.
Click to expand...
Click to collapse
Use opengapps then. Remember, this is not the correct place to ask gapps related questions. It's only for the rom. This will be the last time I mention gapps.
FAQ 13
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.

retiredtab said:
Q15. Can I turn off the on screen navigation keys?
Click to expand...
Click to collapse
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
retiredtab said:
Use opengapps then. Remember, this is not the correct place to ask gapps related questions. It's only for the rom. This will be the last time I mention gapps.
FAQ 13
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
Click to expand...
Click to collapse
I was just letting you know your links didn't work.

ovalseven said:
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
I was just letting you know your links didn't work.
Click to expand...
Click to collapse
@ovalseven, the link in this thread's FAQ still works (for me, anyway) but the download link on that BiTGapps site appears not to be working. The BiTGapps thread [CUSTOM][GAPPS] BiTGApps for Android might have more information / an alternative download site.

ovalseven said:
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
Click to expand...
Click to collapse
Now added to FAQ.
If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout

Thanks for the info and for your work on this rom. Been using it all afternoon and it's running smoothly.

lpedia said:
@ovalseven, the link in this thread's FAQ still works (for me, anyway) but the download link on that BiTGapps site appears not to be working. The BiTGapps thread [CUSTOM][GAPPS] BiTGApps for Android might have more information / an alternative download site.
Click to expand...
Click to collapse
Thanks to @lpedia letting me know, but it seems the developer of bitgapps has removed his links because of some "disagreement" with some users. I'm not involved in this and don't want to be, but if people want bitgapps, they should check the link daily to see when/if the developer will re-enable his links.
So I have now removed all gapps links from my FAQ and it's up to the user now to use their favourite search engine to find whatever gapps or Aurora Store they want. And THIS will be the FINAL word I say on gapps again.

New build called lineage-18.1-20210910-UNOFFICIAL-gt58wifi.zip
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
18.1 continues to be my daily driver since March 2021.
Sept 10 release notes
1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
3. Whatever LiineageOS changed since last August release (about 6,200 files had to be recompiled).

This rom runs fantastic to anyone wondering. Easily the best running rom for t350 (i've tried them all). Thank you for your work on this.

Wikdclown said:
This rom runs fantastic to anyone wondering. Easily the best running rom for t350 (i've tried them all). Thank you for your work on this.
Click to expand...
Click to collapse
I totally agree with you! I just installed the Sept. 10th version on the 10th and it has made my tablet usable again. I will be sticking with this ROM from now on!

The ROM works very well, thank you @retiredtab !
All essential functionality works without caveats. Experimented with enabling pip and split screen and went back to this rom's default setting of being a "low memory" device, as it runs *much* smoother. Good choice of rom's default.
I ran into a couple of crashes in non-essential areas (setting a certain wallpaper crashed the settings, but then worked after reboot; turning on the hotspot then turning it off crashed settings, yet that was a pure curiosity, since there is no utility in the hotspot).
Have a question, pls. How to enable "Phone Ringtone" selection on the "Sound" page in Settings? Something in build.prop? [I use google voice as the voip app on other wifi-only tabs with same lineage version, works well, ringtone selection is there, just need to enable it in the rom for this t350 tab somehow].

Yxo 6o6uka said:
Have a question, pls. How to enable "Phone Ringtone" selection on the "Sound" page in Settings? Something in build.prop? [I use google voice as the voip app on other wifi-only tabs with same lineage version, works well, ringtone selection is there, just need to enable it in the rom for this t350 tab somehow].
Click to expand...
Click to collapse
Which wifi-only tabs give you that ringtone selection? I checked all my wifi 18.1 tablets msm8916 family, exynos 5420 and 5433 and none of them show the phone ringtone selection.

Samsung Tab Pro 8.4 SM-T320. Rom by Valera1978.

Better Mobile App

welcome