yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
Current build:

LOS Updates 2018-12-18

Security patch level 2018-12-05

added Samsung kernel updates imported by [MENTION=5480152]followmsi[/MENTION] (https://github.com/followmsi/android_kernel_samsung_exynos7870/tree/T580XXU3BRF1-nougat) to original kernel (because of https://xdaforums.com/showpost.php?p=78099899&postcount=500)

added patches to original kernel (https://github.com/cschsz/android_kernel_samsung_exynos7870/commits/CVE-stable)

CVE-2018-16658

CVE-2018-18386

Links

SM-T585 (gtaxllte)

ROM https://www.androidfilehost.com/?fid=11410963190603878413

MD5 https://www.androidfilehost.com/?fid=11410963190603878414

SM-T580 (gtaxlwifi) [untested]

ROM https://www.androidfilehost.com/?fid=11410963190603878422

MD5 https://www.androidfilehost.com/?fid=11410963190603878421
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UntouchedWagons:
How do I upgrade? I've got a build from maybe two months ago, do I just flash the new image and google apps?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
I always flash over the last installed build and wipe cache partition + dalvik cache, also this time it worked for me. Usually there is no need to flash gapps. Always keep the latest working build on the device, so if there is a problem you can easily go back...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
[MENTION=5480152]followmsi[/MENTION]:

I added patches to original kernel (https://github.com/cschsz/android_kernel_samsung_exynos7870/commits/CVE-stable):

CVE-2018-16658

CVE-2018-18386
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jst09dc:
[MENTION=8985367]cschsz[/MENTION] and [MENTION=5480152]followmsi[/MENTION] thanks for your continued work on the SM-T580/585 device.

With the new BRF1 shipped 32GB variant (SM-T580 / gtaxlwifi) running the latest cschcz-build (Dec 18; Post #135) and TWRP 3.2.3.4-OMNI6 (https://xdaforums.com/showpost.php?p=78148267&postcount=170) I'm still running into lines issues. However neither blue nor red but now grey-white lines.

The install works normal. The problem only appears when the screen is switched off to standby mode and then back on. In the background the device still seems to run normal, e.g. volume change works (and I suppose if one were to remember where to push for shutdown or restart - w/o screen working - the device would even do that).

Has anybody else with a 33GB/BRF1 device also experienced this problem?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vstrecker:
thank you so much for your hard work. flashed 2*585 yesterday and all works great.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Domenico F:
with the last update my sim card doesn't work anymore....anyone else? (Sm-t585).

edit.

at the 3rd reboot is working again
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
After flashing the new build my sim card wasn't detected, too. I "clicked" on the sim card icon on the status bar and the dialog to insert the pin popped up. Maybe you can try this next time instead of rebooting the device..
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
Did this https://xdaforums.com/showpost.php?p=78099899&postcount=500 worked for you on one of my last builds?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
You have the stripes in system but not in recovery ?

Install the kernel mentioned above via twrp and test again.

I did test RR Nougat version on BRF1 device without problems.

Good luck !
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jst09dc:
Unfortunately no. Flashing this kernel as last step did not help on my BRF1-shipped 32GB device so far:

Result with your previous November 14 build and TWRP 3.2.3.4-OMNI6: red stripes after screen is switched off/standby

Result with the December 18 build and TWRP 3.2.3.4-OMNI6: red stripes too

(My first test with December 18 build gave me white-grey stripes, all subsequent tests result in red stripes - really don't know why I got white-grey once)

I only get the stripes in system (not in recovery). I have not tested RR-builds, only cschsz's LOS nougat builds.

To rule out any leftover problems I went back to stock (BL, AP, CSC) and started from scratch. The stripes still appear on Nougat LOS builds (even with kernel flashed) . The only combination so far working on my BRF1/32GB device is followmsi's Lineage 16.0/32 with TWRP 3.2.3.4-OMNI6.

If you want me to try nougat RR builds I can do that, but I believe that something in nougat LOS builds is still not as it needs to be to work on BRF1 devices.

Please let me know in case any particular logs are helpful (aside from the screen the device appears to be running normal in the background, e.g. adb should be working).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Pls test latest RR nougat version.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jst09dc:
I tried latest RR nougat version (Nov 8, 2018; https://xdaforums.com/galaxy-tab-a/development/rom-2017-nov-30-t3713057). Result: red stripes.

I then additionally flashed the BRF1 kernel (https://xdaforums.com/showpost.php?p=78099899&postcount=500): Result: red stripes.

It is interesting that nougat on your BRF1 shipped device worked and in my case it does not. So far I only have one theory: I had updated my stock firmware to Oreo (8.1.0 / CRJ9) some time ago, maybe this is causing the problems? (Going back to stock today I noticed that I can no longer install BRF1 nougat stock rom. Odin complains about bootloader mismatch, found 4 expected 3 it said if I recall correctly).

The only LOS version running w/o red stripes on my 32GB device so far is your LOS 16.0 / 32 build (Dec 9). On my older 16GB device nougat LOS 14.1 is running flawless.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
You are funny .. :)

If you upgrade a BRF1 shipped device to Samsung stock Oreo you don't have a BRF1 device anymore.

As yo see you can't go down to BRF1 anymore.

I never upgraded my BRF1 device .. the reason why it's working for me.

This is the reason for latest TWRP version (ver. 4) to make recovery working on Samsung stock Oreo devices.

For "Oreo" devices running Nougat we have to "test" Oreo kernel to fix red stripes issue.

I will not play with Nougat anymore .. you may test a few kernels from my gdrive folder.

RR Oreo ROM should work for you .. and 64-bit lineage too .. and AICP 64-bit test ROM too.

Cheers

Edit:

For testing this issue on Nougat I do recommend Oreo kernel sources and Nougat kernel config .. testing with and without dtb.img

https://github.com/followmsi/android_kernel_samsung_exynos7870/commits/oreo-twrp

https://github.com/followmsi/androi...rch/arm64/configs/lineage-gtaxlwifi_defconfig

https://github.com/followmsi/androi...arch/arm64/configs/lineage-gtaxllte_defconfig
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AndroidJail:
Wifi direct

I have t580/32Gb. I had upgraded it to Samsung official Oreo then reverted back to latest official nougat. Yesterday I have downloaded and installed your latest rom. I was impressed to find out that both cameras work perfectly. The screen cast works too.

Issues:

_ Wi-Fi-direct not working

- fc in some applications
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AndroidJail:
Is WiFi direct working?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] RolandDeschain79:
Excellent Rom thank you, long days and pleasant nights to you :cowboy:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alesu69:
Hi there, I have an issue with this ROM on a T585. After screen unlocking, it displays only white stripes.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
Maybe this can help: https://xdaforums.com/showpost.php?p=78099899&postcount=500

Or you try the new Pie 64 Bit version: https://xdaforums.com/galaxy-tab-a/development/rom-lineageos-15-1-64bit-20180920-t3845016
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
I'm still waiting for the patches 2019-01-05 to be merged.... (https://review.lineageos.org/c/LineageOS/android_build/+/238631)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alesu69:
So I've tried all the kernels for T585 from the link you've provided and, unfortunately, none of them works. I guess i will be sticking with Oreo or newer ROMS. I knew for a fact that Nougat (stock or custom) was working flawlessly on this tablet. Too bad i updated it through OTA. No going back I guess.

Thanks for your help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dirkp1:
Thank your, works perfect. I hope for a newer month version
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
It seems like the merges for Android 7.1.2 are really slowed down. But finally they merged 2019-01-05 today..
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
This ROM does not support devices with BRF1 preinstalled!

- - - - - - - - - - - -

Current build:

LOS Updates 2019-02-07

Security patch level 2019-01-05

added Samsung kernel updates imported by [MENTION=5480152]followmsi[/MENTION] (https://github.com/followmsi/android_kernel_samsung_exynos7870/tree/T580XXU3BRF1-nougat) to original kernel (because of https://xdaforums.com/showpost.php?p=78099899&postcount=500)

added patches to original kernel (https://github.com/cschsz/android_kernel_samsung_exynos7870/commits/CVE-stable)

CVE-2018-16658

CVE-2018-18386

CVE-2018-18690

Links

SM-T585 (gtaxllte)

ROM https://www.androidfilehost.com/?fid=1395089523397886940

MD5 https://www.androidfilehost.com/?fid=1395089523397886941

SM-T580 (gtaxlwifi) [untested]

ROM https://www.androidfilehost.com/?fid=1395089523397886946

MD5 https://www.androidfilehost.com/?fid=1395089523397886947
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
[MENTION=5480152]followmsi[/MENTION]:

I added patches to original kernel (https://github.com/cschsz/android_ke...its/CVE-stable):

CVE-2018-16658

CVE-2018-18386

CVE-2018-18690 (NEW)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vstrecker:
Thank you so much. Works great on 2 * 585 here!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
Nine new CVEs to check... :eek:

CVE-2018-20511

CVE-2018-20169

CVE-2018-19854

CVE-2018-18397

CVE-2018-18281

CVE-2018-16885

CVE-2018-16882

CVE-2017-18360

CVE-2016-10741
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
[MENTION=5480152]followmsi[/MENTION]:

Added to https://github.com/cschsz/android_kernel_samsung_exynos7870/commits/CVE-stable:

CVE-2018-20511

CVE-2018-20169

CVE-2017-18360
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
Current build:

LOS Updates 2019-02-21

Security patch level 2019-02-05

added Samsung kernel updates imported by [MENTION=5480152]followmsi[/MENTION] (https://github.com/followmsi/android_kernel_samsung_exynos7870/tree/T580XXU3BRF1-nougat) to original kernel (because of https://xdaforums.com/showpost.php?p=78099899&postcount=500)

added patches to original kernel (https://github.com/cschsz/android_kernel_samsung_exynos7870/commits/CVE-stable)

CVE-2018-16658

CVE-2018-18386

CVE-2018-18690

CVE-2018-20511

CVE-2018-20169

CVE-2017-18360

Links

SM-T585 (gtaxllte)

ROM https://www.androidfilehost.com/?fid=1395089523397899137

MD5 https://www.androidfilehost.com/?fid=1395089523397899138

SM-T580 (gtaxlwifi) [untested]

ROM https://www.androidfilehost.com/?fid=1395089523397899130

MD5 https://www.androidfilehost.com/?fid=1395089523397899131
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vstrecker:
Hi and thank you so much! Just updated two TM585, everything fine! Greetings!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dirkp1:
I've flashed it over your previous SM-T580 und it works perfectly, thank you
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
Current build:

LOS Updates 2019-03-11

Security patch level 2019-03-05

added Samsung kernel updates imported by [MENTION=5480152]followmsi[/MENTION] (https://github.com/followmsi/android_kernel_samsung_exynos7870/tree/T580XXU3BRF1-nougat) to original kernel (because of https://xdaforums.com/showpost.php?p=78099899&postcount=500)

added patches to original kernel (https://github.com/cschsz/android_kernel_samsung_exynos7870/commits/CVE-stable)

CVE-2018-16658

CVE-2018-18386

CVE-2018-18690

CVE-2018-20511

CVE-2018-20169

CVE-2017-18360

Links

SM-T585 (gtaxllte)

ROM https://www.androidfilehost.com/?fid=1395089523397913920

MD5 https://www.androidfilehost.com/?fid=1395089523397913921

SM-T580 (gtaxlwifi) [untested]

ROM https://www.androidfilehost.com/?fid=1395089523397913925

MD5 https://www.androidfilehost.com/?fid=1395089523397913926
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vstrecker:
Installed on my 2 585. Works great. Thank you so much for your work.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
Current build:

LOS Updates 2019-04-08

Security patch level 2019-04-05

added Samsung kernel updates imported by [MENTION=5480152]followmsi[/MENTION] (https://github.com/followmsi/android_kernel_samsung_exynos7870/tree/T580XXU3BRF1-nougat) to original kernel (because of https://xdaforums.com/showpost.php?p=78099899&postcount=500)

added patches to original kernel (https://github.com/cschsz/android_kernel_samsung_exynos7870/commits/CVE-stable)

CVE-2018-16658

CVE-2018-18386

CVE-2018-18690

CVE-2018-20511

CVE-2018-20169

CVE-2017-18360

Links

SM-T585 (gtaxllte)

ROM https://www.androidfilehost.com/?fid=1395089523397937980

MD5 https://www.androidfilehost.com/?fid=1395089523397937979

SM-T580 (gtaxlwifi) [untested]

ROM https://www.androidfilehost.com/?fid=1395089523397937995

MD5 https://www.androidfilehost.com/?fid=1395089523397937996
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheArtfulPenguin:
Does this ROM have the deep sleep camera issue?

When i use apps that use the built in camera like KIK to chat and try to use the camera, specifically the back camera there are issues. Normally it SEEMS like it might be working but there is a single image for the entire video, or it is SUPER fast video.

Thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vstrecker:
THANK YOU SO MUCH for keeping the 585 tablets alive! Installed on my two 585, all fine and happy to have this very urgent security patches.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
Sorry, but I really don't know. I use the camera maybe once in a month to take a photo, but nothing more. Maybe anyone else here has an idea...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ferpalos:
not mirror available

Something is wrong with the link to mirror to the lastes image. I can't access to it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
I've checked the four links and it seems working - maybe there was a problem with android file host yesterday
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AndroidJail:
Battery Drains Fast

I installed lineage-14.1-20190408-UNOFFICIAL-gtaxlwifi.zip. the screen cast was far better as there was less lag. But the battery seems to drain very fast compared to stock rom. I hope this will be fixed in the next monthly update.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ssgr:
I have no issues with battery life.. fortunately.

The monthly builds' only purpose, however, is to incorporate safety updates into the custom image by [MENTION=2047373]Valera1978[/MENTION]:

(from the first post of this thread).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vstrecker:
No problems with battery here too. All works perfect and I want to say thank you for releasing build with security updates.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rakpere:
My tablet screen fails to wake after being turned off for a while, anyone else experiencing this?

EDIT

Also fails to turn on after manual lock.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
Google Play Store started crashing all the time since yesterday. Reboot didn't worked. So I've synced lineageos, compiled it and installed it. Now the Play Store seems working again.

(at the first reboot after flashing the new build over the old one - lineageos didn't start. So after 15 minutes I shut down the tablet. After that it seems working normal with the new build installed)

If someone has the same problem: uploads are coming...

Current build (description on page 1) with LOS Updates 2019-04-26:

SM-T585 (gtaxllte)

ROM https://www.androidfilehost.com/?fid=1395089523397953627

MD5 https://www.androidfilehost.com/?fid=1395089523397953628

SM-T580 (gtaxlwifi) [untested]

ROM https://www.androidfilehost.com/?fid=1395089523397953643

MD5 https://www.androidfilehost.com/?fid=1395089523397953642
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cschsz:
Maybe a newer device with BRF1 preinstalled?! Then try https://xdaforums.com/galaxy-tab-a/development/rom-lineageos-15-1-64bit-20180920-t3845016
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vstrecker:
had no problems with the last rom, no gapps, no google play here. updated for latest patches on 1 585. works fine here. thank you!
[OnePlus 5T  Questions & Answers] Cidious:
I have recently upgraded to open beta 6 with a clean install from beta 5. Wiped. The gallery worked fine at first as far as I know. But now it's directly crashing on opening. Another open 6 version was released today and I thought this one would fix the issue but not.

Cleaned cash and data already and also tried to disable and re-enable. No luck so far.

Running with magisk 16.3.

Anyone with the same problem? I don't feel like wiping it again just for a broken gallery app but I do want to get it working again.
[OnePlus 5T  Questions & Answers] djmcnz:
I don't have the problem but it could be a corrupt image file.

To eliminate this possibility put an empty file called

.nomedia

In the root directory of your internal ("SD Card") storage. Clear Gallery app data and cache again and then open the Gallery. No images should load. If the Gallery app works again then you know you need to hunt down the corrupt file (you can do this by moving that .nomedia file around to different folders or even create more of them). If this trick doesn't work then sorry I have no further suggestions (don't forget to delete the .nomedia file).
[OnePlus 5T  Questions & Answers] DevBug:
I had the same issue and the [MENTION=2084946]djmcnz[/MENTION] method didn't work for me. I fixed it by doing everything [MENTION=2084946]djmcnz[/MENTION] did (.nomedia and deleting app cache and data), going to the Google Play store and uninstalling updates from Gallery app and than updating it back.
[YU Yureka Q&A, Help & Troubleshooting] Manoharc:
I unlocked bootloader and installed lineage os 14.1 using twrp recovery.i did not backup before installing lineage os.I need to install original os for security reasons.please tell me a way.i don't want root my phone
[YU Yureka Q&A, Help & Troubleshooting] saurav007:
You want to rollback to Cyanogen OS?

Download Official images from here or flash through fastboot or recovery (your preferred method).
[Moto X4 Questions & Answers] irongas:
Hi Community,

I was rooted and got some nasty popup virus, then I factory reseted through settings. Everything was fine, then I entered in my software "superuser" and he said he would reinstall something, then booom bootloop!

I tried factory resetting through fastboot didnt work;

I tried flashing stockrom, latest rom, downgrade rom and the error is the same:

Verifying update package...

E: footer is wrong

Update package verification took 0.2 s (result 1).

E: Signature verification failed

E: error: 21

Installation aborted

ADB doesnt recognize my device!!! guess because after rebooting I never re authorized usb debugging mode or oem..

What Can I do now? any help appreciated
[Moto X4 Questions & Answers] sleeptab:
Hey, just try this Guide: https://xdaforums.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750

Everything is described there.

If your Device is on Android One, don't take the Rom from the thread but from this link: https://androidfilehost.com/?fid=673956719939834159

If you have further issues feel free to ask again:)
[Moto X4 Questions & Answers] irongas:
AdB dont recognize my device :( fastboot sees im plugged in but adb wont see the device
[Moto X4 Questions & Answers] screwyou00:
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
[Moto X4 Questions & Answers] irongas:
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
[Moto X4 Questions & Answers] sleeptab:
Did you install Motorola fastboot drivers?

The menu what you talk about is Recovery. Look if there's an option to boot to bootloader. If not go down to reboot the device and keep VOL-Down pressed so it reboots to bootloader. There you can just use fastboot commands.
[Moto X4 Questions & Answers] irongas:
RESOLVED!

hEY i JUST looked in device manager and there was a driver issue, then I reinstalled the driver from the pc adb phone, and it came back to liiiife!!! I just followed the second sequence and boom its working

Thank you a looot guys!!! sorry being such a noob! =)

Have a nice one!!
[Mogul, XV6800 ROM Development] Juicy47:
Flashed a ROM that didn't fully remove Sprint's Customization app, and my entire EPST setting have been changed.

I'm wondering if someone with TELUS can help me restore my settings. Specifically, what is the NAM name, and under M.IP Default Profile, what is the login structure? (e.g. is it the ESN in HEX@1X.TELUSMOBILITY.COM?)

Thanks for your help.

[UPDATE]

It looks like there is a similar discussion over at PPCGeeks, and the solution included flashing the stock TELUS ROM. Does anyone have an archive of it? The HTC Support site doesnt seem to have it at the moment.
[Mogul, XV6800 ROM Development] Dc_striker:
go flash another rom
[ONE Q&A, Help & Troubleshooting] amd-dude:
Hey guys, I was wondering if anyone else has this problem. When using the official COS 13 rom everything works but GPS is slow to get a fix and when it does, it is out of sync i.e. position is further back or forward from my real location.

When I flash to Nougat, GPS works as it should, locks pretty quickly and is accurate. I've tried changing modem firmwares, using TopNTP to patch the gps.conf file and nothing seems to work in COS 13, which is the OS I prefer since Kali Nethunter works on it with no hitches.

I would really like to go back to COS13 but I use GPS occasionally and as the old saying goes, you only wish you had it when you need it the most. Any help or thoughts would be appreciated. Thanks.
[ONE Q&A, Help & Troubleshooting] amd-dude:
Guess no one else ever heard about this.
[ONE Q&A, Help & Troubleshooting] Odysseus1962:
It's not that nobody has heard of it, but you're asking about an issue with an older version of Android that is no longer being actively developed, and due to security flaws is no longer safe to run on your handset. As with all versions of Android, the code is open sourced, so you are more than welcome to dig into the source code, get your hands dirty, and fix anything you want, but expecting anyone else to fix an issue on a deprecated OS is a bit much, IMHO.
[ONE Q&A, Help & Troubleshooting] amd-dude:
Never asked if anyone can fix it, I won't be so bold since I never did any Android development myself, hence is stated I flashed different firmware and used GPS.conf apps etc just asked if anyone else came across this issue since at one point in time we were all on cos13 and if it could be solved by flashing a zip or editing a conf file.