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

[Paquele]

Hi

the LineagOS install with OpenGAPPS works fine

but i have a Problem with root ( both ), after installing SuperSU or Magisk ( one of them ) and then installing the patched boot.img via TRPW , my t280 get stuck in a Bootloop.

any suggestions what i´am doing wrong?

it`s not the first Tablet or Mobile for me but somthing i`m doing wrong this time.

 

[steadfasterX]

Hi

the LineagOS install with OpenGAPPS works fine

but i have a Problem with root ( both ), after installing SuperSU or Magisk ( one of them ) and then installing the patched boot.img via TRPW , my t280 get stuck in a Bootloop.

any suggestions what i´am doing wrong?

it`s not the first Tablet or Mobile for me but somthing i`m doing wrong this time.

hmm try magisk v21

 

[Paquele]

hi, thanks for your answer...

i`d tried the two last releases 24 + 25 and it ends with no errors but after flash the boot image ( as boot ) it get stuck in Bootloop..

 

[2faraway2]

I have a working configuratin with magisk 20.4.
Anything >= magisk 23.0 gave me bootloops as well ..

 

[steadfasterX]

hi, thanks for your answer...

i`d tried the two last releases 24 + 25 and it ends with no errors but after flash the boot image ( as boot ) it get stuck in Bootloop..

Yes and i told try v21 or v20.

 

[Paquele]

I have a working configuratin with magisk 20.4.
Anything >= magisk 23.0 gave me bootloops as well ..

did you install after Magisk the patched img as boot ?

Yes and i told try v21 or v20.

sorry , meanwilhe i`ve tested and same Story...

i´ll try 20.4....

 

[Paquele]

@2faraway2

working whith 20.4 without flashing patched img....

thanks


Edit: this Rom works fine, after rooting i´ve install Androoster to tweak some Settings and now all works very well.

 

[Rodrigo Ben]

@2faraway2

working whith 20.4 without flashing patched img....

thanks


Edit: this Rom works fine, after rooting i´ve install Androoster to tweak some Settings and now all works very well.

Have you solved the wifi problems and random reboots?

 

[Paquele]

Have you solved the wifi problems and random reboots?

Wifi issue ist still a litten Problem but the tablet works fine with a Hotspot that provide my S21....

random reboots?
I've no random reboot, in this case all works fine.

 

[Ibrahim.1]

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

I successfully rooted my phone magisk 25.2 but the magisk manager won't open it is stuck on mask screen when I uninstall he root it opens but when I root my tab it won't open any helps?

 

[RFZ]

Hey all,
I also tried rooting my SM-T280 with SuperSU and got stuck on boot. I already had LineageOS 14.1 and TWRP installed and my bootloader unlocked.
I noticed that the patched boot-partition that the SuperSU install-script creates is missing the DHTB header at the start of the partition (first 512 Bytes). So I simply prepended the first 512 Bytes of my old boot partition and flashed it again, and it actually worked - at least with SuperSU 2.78.

I modified the SuperSU 2.78 install script to actually perform this step during install, just by adding this at the end before it flashes the image:

# Patch image to include additional 512 Bytes Header found on SM-T280 devices
if [ "$(dd if=$BOOTIMAGE count=4 bs=1)" = "DHTB" ]; then
  ui_print "- Found DHTB Header at 0x0000, expecting ANDR at 0x0200"
  if [ "$(dd if=$BOOTIMAGE count=4 bs=1 skip=512)" = "ANDR" ]; then
    ui_print "- Found ANDR Header at 0x0200, patching boot.img"
    dd if=$BOOTIMAGE of=/sutmp/prefix.img count=1 bs=512
    cat /sutmp/prefix.img /sutmp/boot.img > /sutmp/patched.img
    rm /sutmp/boot.img
    mv /sutmp/patched.img /sutmp/boot.img
  else
    ui_print "- ANDR Header NOT found at 0x0200, boot.img may not work!"
  fi
else
  ui_print "- DHTB Header at 0x0000 NOT found, skipping step"
fi

I guess the attached SuperSU should work for you too.

I tried the same with SuperSU 2.82 but even with the DHTB part it gets stuck on boot

I learned that the DHTB part is actually a signature for the following partition. So by just copying another signature I clearly use an invalid one, but it seems the bootloader doesn't care

Before you use my patched installer, make a backup of your boot partition, so you can restore it if it goes wrong

Edit: Download removed, see next post

 

[RFZ]

I tried the same with SuperSU 2.82 but even with the DHTB part it gets stuck on boot

I learned that the DHTB part is actually a signature for the following partition. So by just copying another signature I clearly use an invalid one, but it seems the bootloader doesn't care

Okay, the DHTB part not only contains a signature but also the payload length of the data the signature is generated over. I missed the last part and that length caused it to get stuck on boot with SuperSU 2.82.

I noticed that it boots fine if I just set signature and length to all zeroes.

So here is my version of the patched SuperSU, now also for 2.82.

# Patch image to include additional 512 Bytes Header found on SM-T280 devices
if [ "$(dd if=$BOOTIMAGE count=4 bs=1)" = "DHTB" ]; then 
  ui_print "- Found DHTB Header at 0x0000, expecting ANDR at 0x0200"
  if [ "$(dd if=$BOOTIMAGE count=4 bs=1 skip=512)" = "ANDR" ]; then
    ui_print "- Found ANDR Header at 0x0200, patching boot.img"
    dd if=$BOOTIMAGE of=/sutmp/prefix.img count=8 bs=1
    dd if=/dev/zero of=/sutmp/prefix-pad.img count=504 bs=1
    cat /sutmp/prefix.img /sutmp/prefix-pad.img /sutmp/boot.img > /sutmp/patched.img
    rm /sutmp/boot.img
    mv /sutmp/patched.img /sutmp/boot.img
  else
    ui_print "- ANDR Header NOT found at 0x0200, boot.img may not work!"
  fi
else
  ui_print "- DHTB Header at 0x0000 NOT found, skipping step"
fi

 

[chopperpl]

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!!!

 

[Miniblox Gaming]

Thanks it worked. By the way where did you get that?

 

[thisguy12win]

I love u man!!!

 

[TommyBt]

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!!!

chopperpl have you 6modifiled zip file ? I'm doing something wring while installing i get error:6
Can u share your files please ?

 

[Mays_McMuffin]

Okay, the DHTB part not only contains a signature but also the payload length of the data the signature is generated over. I missed the last part and that length caused it to get stuck on boot with SuperSU 2.82.

I noticed that it boots fine if I just set signature and length to all zeroes.

So here is my version of the patched SuperSU, now also for 2.82.

# Patch image to include additional 512 Bytes Header found on SM-T280 devices
if [ "$(dd if=$BOOTIMAGE count=4 bs=1)" = "DHTB" ]; then
  ui_print "- Found DHTB Header at 0x0000, expecting ANDR at 0x0200"
  if [ "$(dd if=$BOOTIMAGE count=4 bs=1 skip=512)" = "ANDR" ]; then
    ui_print "- Found ANDR Header at 0x0200, patching boot.img"
    dd if=$BOOTIMAGE of=/sutmp/prefix.img count=8 bs=1
    dd if=/dev/zero of=/sutmp/prefix-pad.img count=504 bs=1
    cat /sutmp/prefix.img /sutmp/prefix-pad.img /sutmp/boot.img > /sutmp/patched.img
    rm /sutmp/boot.img
    mv /sutmp/patched.img /sutmp/boot.img
  else
    ui_print "- ANDR Header NOT found at 0x0200, boot.img may not work!"
  fi
else
  ui_print "- DHTB Header at 0x0000 NOT found, skipping step"
fi

how did you get lineage to work, to begin with, it is being the biggest pain in my neck to have it installed because every time I try to do anything I get an error, I tried installing it with the 14.1 from May 12, 2020, and the also the latest from Feb 9, 2021, but it kept saying it failed because of ERROR:7. Then I tried to edit the file and rezipped the folder and now it just says either Zip signature failed or invalid zip file.

 

[RFZ]

how did you get lineage to work, to begin with, it is being the biggest pain in my neck to have it installed because every time I try to do anything I get an error, I tried installing it with the 14.1 from May 12, 2020, and the also the latest from Feb 9, 2021, but it kept saying it failed because of ERROR:7. Then I tried to edit the file and rezipped the folder and now it just says either Zip signature failed or invalid zip file.

I've installed lineage-14.1-20210209-UNOFFICIAL-gtexswifi.zip via TWRP, TWRP 3.1.1-0_mone to be exact. Wasn't an issue at all.

 

[Mays_McMuffin]

I've installed lineage-14.1-20210209-UNOFFICIAL-gtexswifi.zip via TWRP, TWRP 3.1.1-0_mone to be exact. Wasn't an issue at all.

Yeah, I tried with the same lineage but my TWRP is 3.2.1-1_ashyx, could that be the problem though?

edit: I just tried it again, with the 20210209 and it said "updater process ended with ERROR:7"

 

[Mays_McMuffin]

I've installed lineage-14.1-20210209-UNOFFICIAL-gtexswifi.zip via TWRP, TWRP 3.1.1-0_mone to be exact. Wasn't an issue at all.

Alright, somehow I got it installed with TWRP 3.1.1-0_mone and It had no problems like you said.