FORUMS
Remove All Ads from XDA

[RECOVERY][ROOT][TWRP 3.0.2-1][Magisk v7] Samsung Galaxy Tab A6 SM-T280

10,266 posts
Thanks Meter: 6,855
 
By ashyx, Recognized Contributor on 6th October 2016, 06:18 PM
Post Reply Email Thread


TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-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 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.

TWRP_3.0.2-1_SM-T280_261016


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.



For Systemless Root with SuperSu.

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

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 v7:


1. Download Magisk v7 to your device
Magisk v7

2. Install the Magisk v7 zip with TWRP

3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280

4. Reboot

To Install Magisk v7 with SuperSu:

1. Follow the instructions above to install SuperSu

2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7

3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280

4. Reboot

5. Install 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

The Following 30 Users Say Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
 
 
26th October 2016, 10:20 PM |#2  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 6,855
 
Donate to Me
More
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
The Following 7 Users Say Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
26th October 2016, 10:27 PM |#3  
Junior Member
Thanks Meter: 0
 
More
Help me root my phone


Sent from my SM-G903W using XDA Free mobile app
27th October 2016, 06:47 AM |#4  
Senior Member
Flag Bacoor
Thanks Meter: 320
 
Donate to Me
More
Quote:
Originally Posted by ashyx

GUI lag fix - Lag in the GUI should now be fixed
MTP fix

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
28th October 2016, 12:27 PM |#5  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 6,855
 
Donate to Me
More
Quote:
Originally Posted by jedld

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.
The Following 3 Users Say Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
30th October 2016, 01:56 AM |#6  
Member
Ecuador
Thanks Meter: 12
 
More
PRE-ROOTED boot image can be used on 285? (needed for Systemless Root ) same at magisk patched boot
30th October 2016, 08:23 AM |#7  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 6,855
 
Donate to Me
More
Quote:
Originally Posted by jaritico

PRE-ROOTED boot image can be used on 285? (needed for Systemless Root ) same at magisk patched boot

You don't need it for the T285.
31st October 2016, 10:13 AM |#8  
Senior Member
Thanks Meter: 75
 
More
Worked perfectly, first time.
Installed supersu via trwp and then img via boot in twrp also.
Thank you for the clear tutorial.
Excellent
3rd November 2016, 06:52 PM |#9  
Junior Member
Thanks Meter: 0
 
More
just about to root mine now are there any custom roms that can go on it?
3rd November 2016, 11:30 PM |#10  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by ashyx



TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-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 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.

TWRP_3.0.2-1_SM-T280_261016


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.



For Systemless Root with SuperSu.

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

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 v7:


1. Download Magisk v7 to your device
Magisk v7

2. Install the Magisk v7 zip with TWRP

3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280

4. Reboot

To Install Magisk v7 with SuperSu:

1. Follow the instructions above to install SuperSu

2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7

3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280

4. Reboot

5. Install 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

I don't know how this is working for others, but installing SuperSu uninstalled android.
The Following User Says Thank You to Ethan-56 For This Useful Post: [ View ] Gift Ethan-56 Ad-Free
3rd November 2016, 11:45 PM |#11  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 6,855
 
Donate to Me
More
Quote:
Originally Posted by Ethan-56

I don't know how this is working for others, but installing SuperSu uninstalled android.

It does what?
Also please don't quote the entire OP.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes