• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU]

Status
Not open for further replies.
Search This thread

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,904


Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
   phone or causes thermonuclear war  and ends the
    world as we know it. You have been warned.

ROM Information


Device Names

Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-T560NU[/B] - [COLOR="DarkSlateBlue"][B]gtelwifiue[/B][/COLOR]

Download

All Jenkins builds are testing builds, and as such, are likely to be extremely unstable or
unusable.

Code:
[B]All builds:[/B] [url]https://download.msm8916.com/[/url]

[B]Jenkins Builds Builds:[/B] [url]https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_Tab_E/[/url]

[B]TWRP Builds:[/B] [url]https://jenkins.msm8916.com/job/TWRP_Builds/[/url]

[B]GApps:[/B] [url]http://opengapps.org/?arch=arm&variant=micro&api=7.1[/url]

[B]RSS:[/B] [url]https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_Tab_E/rssLatest[/url]


Instructions

If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).

You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.

Installation via recovery (TWRP/LineageOS Recovery)
* Download a recent .zip file from the links above for your device.

* Reboot into recovery mode [Press Power+Volume Up+Home].

* Wipe your data and cache partition (equivalent to doing a Factory Reset)
if you are coming from a stock ROM.


* Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:

* Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:

adb sideload name_of_zip.zip

to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.

* Download and flash GApps in the same way.

How to provide logcats

Under Windows:


Code:
[B]* Install samsung device drivers and then
 the adb utils from here:[/B]

[url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]

[b]* Then enable developer mode, connect your phone to usb,
 and from [B]cmd[/B] paste this command:[/b]

[I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]

[b]then try to reproduce the bug.[/b]

[b]* The logcat file will be on your desktop.[/b]



Under Linux:


Code:
[b]* Install the adb utils from your distribution's
 package manager and execute the command:[/b]

[I]adb logcat > ~/logcat.txt[/I]

[b]then try to reproduce the bug.[/b]

[b]* The logcat file will be on your home directory.[/b]

* Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.

* If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:

Code:
adb connect [ip address here]

And then the adb logcat command for windows.


Features

Code:
* OMS/Substratum theming support.
* The usual LineageOS features.
* All builds support over-the-air updates.


FAQ

Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.

Q: But I don't have that kind of money! What else?
A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.

Q: Are you accepting feature requests?
A: Unless you're willing to implement it yourself, no.

Q: Can you make XXX ROM as well as LOS?
A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.

Q: Can I throw money at you?
A: Most certainly. Donations are always welcome.


You want to help?

  • We need hardware power to get the builds done.
    If you want to help us go faster, send a PM to @kentone or
    @vince2678. Your computer will act as a client for our jenkins server.

  • In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.
  • As always, logcat any problem you find.



XDA:DevDB Information
[UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU], ROM for the Android General

Contributors
vince2678, deadman96385, minz1
Source Code: https://github.com/Galaxy-MSM8916

ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS

Version Information
Status: Stable
Stable Release Date: 2017-06-08

Created 2017-02-03
Last Updated 2018-06-24
 

Attachments

  • Screenshot_20170115-163746.jpg
    Screenshot_20170115-163746.jpg
    157.7 KB · Views: 10,131
  • Screenshot_20170115-163948.jpg
    Screenshot_20170115-163948.jpg
    146.4 KB · Views: 10,510
  • Screenshot_20170115-163814.jpg
    Screenshot_20170115-163814.jpg
    132.8 KB · Views: 10,399
  • Screenshot_20170115-163918.jpg
    Screenshot_20170115-163918.jpg
    236.7 KB · Views: 10,780
  • Screenshot_20170115-163851.jpg
    Screenshot_20170115-163851.jpg
    80 KB · Views: 10,289
  • Screenshot_20170115-163801.jpg
    Screenshot_20170115-163801.jpg
    88.2 KB · Views: 11,079
  • Screenshot_20170115-163756.jpg
    Screenshot_20170115-163756.jpg
    80.1 KB · Views: 10,625
  • Screenshot_20170115-163731.jpg
    Screenshot_20170115-163731.jpg
    103.3 KB · Views: 10,216
  • Screenshot_20170115-163826.jpg
    Screenshot_20170115-163826.jpg
    130.9 KB · Views: 8,958
Last edited:

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,904
Reserved

Changelog

NOTE: gtesqltespr (SM-T377P) builds have been disabled until someone steps up for testing to resolve the issue in recent builds.

For more detailed changelog information, see the changelog on the download or jenkins servers for each specific build.

Code:
[B][U]29/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Added KeyDisabler. For devices with touch keys controlled separately
  from the touch screen, this means that the virtual Nav Bar
  can be enabled in the Settings. [/B]

* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using a kernel driver for disabling touch devices
  when the screen is off instead of a user service for that. [/B]
  
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated kernel to the latest upstream AOSP and
  CAF tags. There should be a noticeable performance boost. [/B]
  
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using OSS GPS code instead of prebuilt libs.
   Location applications should be getting and reporting
   satellite fix information properly. [/B]
  
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Disabled cpusets support, which was slowing
  down the system performance. [/B]
  
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The auto time zone feature should now be working
  proper, (that is, without resetting the time zone
  to 0000 UTC).[/B]
  
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Data should be working fully on all devices. [/B]


Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should now be working [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The "message not sent" bug in text messaging
  app(s) should be gone. [/B]

Code:
[B][U]01/06/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and prima (wifi)
   driver to the latest caf branch LA.BR.1.2.9_rb1.18[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The reboots caused by errors in the
  prima kernel driver should be gone.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
   Updated F2FS code from upstream kernel sources and enabled
   security extended attribute support (for SElinux) to fix
   android support.[/B]

Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built-into the kernel again.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The sleep issue should be fixed in the latest build.
  This was due to the failure to set a critical kernel
  variable at boot because the kernel init system was
  not interpreting a boot command line variable correctly.[/B]
* [B][[COLOR="Red"]FEATURE[/COLOR]][/B][B] OMS/Substratum support is now built into the
  ROM.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS is enabled in-kernel, so F2FS filesystem
  mounting and formatting should be working fully.[/B]

Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is being built as a module for now,
  transitioning to a new kernel somehow broke the ability
   to build it into the kernel binary.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
  J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]  
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Builds now use sdcardfs from Google. This should
 result in faster file operations on the sdcard overall
 compared to using FUSE as an overlay.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Both cameras should now be working [/B]

Code:
[B][U]01/04/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] LineageOS updater can reboot to recovery properly.[/B]

Code:
[B][U]11/03/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Switched binary blob base from
    T377PSPT2BPJ1 (6.0.1) to T377PVPU1AOJ5 (5.1.1)[/B]

Code:
[B][U]16/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Decreased minimal scaling freq. to 200Mhz.  
The previous scaling frequency minimum of 800Mhz was pretty high,
 and could quickly cook your phone and kill power on mobile devices.
 Lowering to 200Mhz should significantly extend batery life
 on the stock scheduler. [/B]

[B][U]12/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.9_rb1.11 ] [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated kernel source [ to LA.BR.1.2.9_rb1.11 ] [/B]

[B][U]06/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Changed to a new kernel source [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Refactored device trees [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Monthly security fixes from Google [/B]

There are a lot more minor tweaks and fixes. I don't have the time to constantly be updating this; I expect you'll read the
changelogs anyways since I take my time to write the commit messages in detail.


Code:
[B][U]29/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Switched to LineageOS sources. [/B]

[B][U]20/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Made some substantial changes to our build
 infrastructure,  which should make my life substantially easier
 and using Jenkins and all a more pleasant experience. [/B]

[B][U]17/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Reboot bug should be fixed [/B]

[COLOR="RoyalBlue"][B]gtesqltespr[/B][/COLOR]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Wifi should be working (build >= 4) [/B]

Code:
[B][U]16/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.7_rb1.7 ] [/B]

Code:
[B][U]15/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Started builds for SM-T377P [/B]
* [B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added KSM and ZRAM. These have to be enabled manually by
   setting "ro.config.ksm" and "ro.config.zram" in the build.prop to true. [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Set maximum cpu frequency to 1209Mhz [/B]

[COLOR="RoyalBlue"][B]gtelwifiue[/B][/COLOR]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Rear camera is working [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] LiveDisplay feature is working [/B]

Code:
[B][U]11/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Switched binary blob base from
    T560NUUEU1BPI3 (6.0.1) to T560NUUEU1AOK1 (5.1.1)[/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Audio and wifi now work proper. [/B]

Code:
[B][U]08/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Created forum thread [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] First build completed. [/B]


Known Issues
Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] None [/B]
 
Last edited:

ElsaReyes

Senior Member
Apr 25, 2016
353
37
I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3
 

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,904
I'm aware of the bug. For now, you'll have to flash the latest CyanogenModRecovery to update the device until twrp works proper.
 
Last edited:
  • Like
Reactions: 42o247

ElsaReyes

Senior Member
Apr 25, 2016
353
37
I'm hoping you might know what I need to do here, but I installed a theme recently and it worked fine. But I ended up having to redo my tablet for a different reason, and ever since then whenever I try to use the same theme my system UI fails.
 

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,087
9,907
I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3

You can try the recoveries below, fully tested and working.

https://forum.xda-developers.com/showthread.php?t=3302935
 

42o247

Senior Member
Nov 10, 2010
550
63
im wondering if anyone knows the device name for the t377p, to edit in the updater script to try flashing this on a sm-t377p?
 

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,904
I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3

The reboot issue for recovery is now fixed.
 
  • Like
Reactions: 42o247

42o247

Senior Member
Nov 10, 2010
550
63
i got my t377p to boot all the way to the cm head logo by deleting the first line in the updater script and clean flashing the zip.
clean flash
restore boot partition from stock mm rom
boot
hangs at cm boot logo

ive begun reading how to make a custom kernel and the sources are available for the t377p. so if i dont get too frustrated i can try to compile one to make this rom work with my device
 

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,904
i got my t377p to boot all the way to the cm head logo by deleting the first line in the updater script and clean flashing the zip.
clean flash
restore boot partition from stock mm rom
boot
hangs at cm boot logo

ive begun reading how to make a custom kernel and the sources are available for the t377p. so if i dont get too frustrated i can try to compile one to make this rom work with my device

A lot of things would not work, for example, the touchscreen. As similar as devices may seem there will still be hardware differences between variants and I don't recommend cross flashing.
 

bigtom624

Senior Member
Jun 23, 2010
1,597
814
Philadelphia Pa.
Just flashed the 1/15 build and everything went well. I'm in the process of setting my Sm-t560nu up. I will report back after I'm finished. Thanks a lot for this Rom.
 

ElsaReyes

Senior Member
Apr 25, 2016
353
37
The reboot issue for recovery is now fixed.

Awesome. Thank you for all your work on this. Downloading the build now. :3

And just to keep you updated, it might not be in the newest build but I tried playing some of the videos I have saved on my sd card last night, and while the audio moves along just fine, the video plays all choppy and slow.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 28


    Code:
    ** Disclaimer
    I am not responsible if flashing this ROM bricks your
       phone or causes thermonuclear war  and ends the
        world as we know it. You have been warned.

    ROM Information


    Device Names

    Verify your device codename before downloading any firmwares or recovery images!
    Code:
    [B]SM-T560NU[/B] - [COLOR="DarkSlateBlue"][B]gtelwifiue[/B][/COLOR]

    Download

    All Jenkins builds are testing builds, and as such, are likely to be extremely unstable or
    unusable.

    Code:
    [B]All builds:[/B] [url]https://download.msm8916.com/[/url]
    
    [B]Jenkins Builds Builds:[/B] [url]https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_Tab_E/[/url]
    
    [B]TWRP Builds:[/B] [url]https://jenkins.msm8916.com/job/TWRP_Builds/[/url]
    
    [B]GApps:[/B] [url]http://opengapps.org/?arch=arm&variant=micro&api=7.1[/url]
    
    [B]RSS:[/B] [url]https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_Tab_E/rssLatest[/url]


    Instructions

    If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).

    You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.

    Installation via recovery (TWRP/LineageOS Recovery)
    * Download a recent .zip file from the links above for your device.

    * Reboot into recovery mode [Press Power+Volume Up+Home].

    * Wipe your data and cache partition (equivalent to doing a Factory Reset)
    if you are coming from a stock ROM.


    * Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:

    * Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
    Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:

    adb sideload name_of_zip.zip

    to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.

    * Download and flash GApps in the same way.

    How to provide logcats

    Under Windows:


    Code:
    [B]* Install samsung device drivers and then
     the adb utils from here:[/B]
    
    [url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]
    
    [b]* Then enable developer mode, connect your phone to usb,
     and from [B]cmd[/B] paste this command:[/b]
    
    [I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]
    
    [b]then try to reproduce the bug.[/b]
    
    [b]* The logcat file will be on your desktop.[/b]



    Under Linux:


    Code:
    [b]* Install the adb utils from your distribution's
     package manager and execute the command:[/b]
    
    [I]adb logcat > ~/logcat.txt[/I]
    
    [b]then try to reproduce the bug.[/b]
    
    [b]* The logcat file will be on your home directory.[/b]

    * Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.

    * If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:

    Code:
    adb connect [ip address here]

    And then the adb logcat command for windows.


    Features

    Code:
    * OMS/Substratum theming support.
    * The usual LineageOS features.
    * All builds support over-the-air updates.


    FAQ

    Q: Are you taking device requests?
    A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.

    Q: But I don't have that kind of money! What else?
    A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.

    Q: Are you accepting feature requests?
    A: Unless you're willing to implement it yourself, no.

    Q: Can you make XXX ROM as well as LOS?
    A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.

    Q: Can I throw money at you?
    A: Most certainly. Donations are always welcome.


    You want to help?

    • We need hardware power to get the builds done.
      If you want to help us go faster, send a PM to @kentone or
      @vince2678. Your computer will act as a client for our jenkins server.

    • In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.
    • As always, logcat any problem you find.



    XDA:DevDB Information
    [UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU], ROM for the Android General

    Contributors
    vince2678, deadman96385, minz1
    Source Code: https://github.com/Galaxy-MSM8916

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.10.x
    Based On: LineageOS

    Version Information
    Status: Stable
    Stable Release Date: 2017-06-08

    Created 2017-02-03
    Last Updated 2018-06-24
    5
    This thread has been abandoned for quite a bit, so instead of picking up O from here, we'll be opening a new thread soon for the SM-T377P and SM-T560NU, as well as any other tabs we happen to maintain for.

    Many thanks to Ian Sullivan for donating a T377P.
    4
    just curious. but is the lack of a device the reason development halted on the t377p branch?

    im pretty content with the software so far, so this is not meant to be a complaint or request. just wondering of what id need to do to help. but i got my tab e for $40 so i was also content with it being stock and rooted.

    youve done really good work with cm/linos and im glad that you included my device :good:

    New builds for M and N will be coming today.
    3
    Hi,

    I've tried to install builds from https://download.lineageos.org/gtelwifiue (tried 20171205 and 20171128), to no avail: the actual installation process via TWRP works fine with no errors, but then after reboot the Lineage startup bubble screen animation just go on and on indefinitely. Since I know the first boot can take a while, I've waited much time, even a whole night, without Lineage ever getting to the setup screen, and I've tried quite a few times. But then I found the current thread and installed https://download.msm8916.com/gtelwifiue/20170905, which worked right away. Any reasons why the builds on lineageos.org won't work for me? Am I missing something? Since they seem more recent, it looks to me they would be preferable? Thanks!

    Same, but 20171121 seems to work.
    3
    Can someone link me the version i have to download for the SM-T560 please ? I successfully installed TWRP but i don't know what to do know :/


    Guys, please clarify and make this clear in the OP:
    is dirty flashing (over a previous version of this ROM) OK?
    someone please update the device names in the OP, as it looks like the codes have changed

    Many thanks!

    Dirty flashing is only fine if you're flashing over LOS/CM

    The device names are correct and have not changed. None of the roms is compatible with the T560/T377.