[RECOVERY][ROOT][TWRP 3.2.1-1][Magisk v14] Samsung Galaxy Tab A6 SM-T280/SM-T285

Search This thread
May 15, 2020
21
3
Derbyshire
I can confirm the device gtexswifixx can be flashed with this ROM after you adopt the META data inside of this package according to this method:
Update to 0.18 on SM-G870F with lineage-18.1-20201225-UNOFFICIAL-recovery-klteactivexx.img - #15 by piero 21
It seems everything I've tried (except camera) is working. It is enough for me to use this old tablet as Home Assistant wall mounted panel. Thanks to contributors!!!
Please could you explain exactly which part of the tread you followed or what steps you did? Looking at the thread, it seems they are talking about the klte, the Samsung s5 and not the gtexwifixx. I would really like to run a more well supported version of android on this tablet but I do not understand this tutorial
 
teamwin-recovery-project-twrp-logo.jpg


TWRP custom recovery for the Tab A SM-T280/T285. Latest build is 3.2.1-1

Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.

NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.



UPDATE 08/01/2018 - TWRP updated to version 3.2.1-1

UPDATE 21/11/2017 - Magisk updated to v14

UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed

MTP fix - MTP should now be working


To install TWRP:


1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.

2. Load the respective file below into the AP slot and hit start.

3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.

DOWNLOAD:
TWRP_3.0.2-1_SM-T280_261016

twrp_3.2.1-1_sm-t280_080118

twrp_3.2.1-1_sm-t285_080118


NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
(FIXED)


For Systemless Root with SuperSu.

1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031

This step only required for the SM-T280
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280

3. Reboot

4. Check you have root


To install Magisk v14:

1. Download Magisk v14 to your device
Magisk v14

2. Install the Magisk v14 zip with TWRP

This step only required for the T280
3. Flash the patched boot image below with TWRP.
magiskv14_boot_aqd1

4. Reboot

5. Install Magisk manager
Magisk Manager


PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.


DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

Anyone got a link for this patched magisk file? There are no mirrors given the age ... Wanting root to rid some of the crap from this device...


Regards
 

Top Liked Posts

  • There are no posts matching your filters.
  • 56
    teamwin-recovery-project-twrp-logo.jpg


    TWRP custom recovery for the Tab A SM-T280/T285. Latest build is 3.2.1-1

    Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.

    NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
    Settings -> Developer Options -> OEM unlocking
    AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.



    UPDATE 08/01/2018 - TWRP updated to version 3.2.1-1

    UPDATE 21/11/2017 - Magisk updated to v14

    UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
    MTP fix - MTP should now be working



    To install TWRP:

    1. Flash with ODIN 3.10.7 in the AP slot.
    Uncheck Auto reboot.

    2. Load the respective file below into the AP slot and hit start.

    3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
    As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
    You should now see TWRP recovery.

    DOWNLOAD:
    TWRP_3.0.2-1_SM-T280_261016

    twrp_3.2.1-1_sm-t280_080118

    twrp_3.2.1-1_sm-t285_080118


    NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
    (FIXED)


    For Systemless Root with SuperSu.

    1. Install Supersu via TWRP
    SR1-SuperSU-v2.78-SR1-20160915123031

    This step only required for the SM-T280
    2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
    supersu_2.78_SR1_systemless_boot_t280

    3. Reboot

    4. Check you have root


    To install Magisk v14:


    1. Download Magisk v14 to your device
    Magisk v14

    2. Install the Magisk v14 zip with TWRP

    This step only required for the T280
    3. Flash the patched boot image below with TWRP.
    magiskv14_boot_aqd1

    4. Reboot

    5. Install Magisk manager
    Magisk Manager


    PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.


    DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

    10
    GUI lag fix - Lag in the GUI should now be fixed
    MTP fix
    5
    interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
    Hi Jed, after trying various different configs in twrp and even modifying the graphics source code it made no difference.
    Using the the touch debugger in twrp it was apparent that the touch was responding fine.

    So I turned my attention to the kernel.
    After several builds of modifying the cpu config making no difference, it turns out TWRP only supports double buffering, but the kernel was forcing triple buffering.
    It seems this was causing an extra frame to be displayed causing what seemed like lag and explains why when pressing the screen a second time would cause the frame to update.

    The page that was in ram had changed when tapping a button, but the wrong frame in the buffer was displayed until the next touch which then updated the display.

    Disabling triple buffering in the kernel fixed the issue.
    3
    I hope the patched boot image for Magisk v14 come soon. I have been preparing my SM-T280 for this. Backing up everything on it, stocking up the stock images for emergency, etc.

    (BTW, a noob question, I thought Magisk is doing the patch on boot.img when it is installed. SM-T280 is different?)
    Magisk updated to v14.
    2
    Long story short, is it currently safe to flash magisk v14 on this device, or do I need to go down to v7, and also, what is the difference between them?

    Do not update to V14.
    Install patched kernel will result in bootloop.