Database Develop

Systemless root (Android 6.0) - Method for easy future OTA updates

I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?

Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.

yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk

@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.

Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk

quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).

Sounds good!
Sent from my MotoG3 using Tapatalk

quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.

Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?

Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?

Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.

Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!

Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?

ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.

Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.

you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk

caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!

ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks

H81120x OTA update out. Has anyone still using stock updated to this version?

https://support.t-mobile.com/docs/DOC-28979
Pushed out December 5th, H81120x, just over 79MB, described as "Google monthly security enhancements".
I've forgotten where OTA update files are downloaded too. Can anyone refresh my memory?
Thanks!

This is good to know. Any idea if I need to be worried about the phone being rooted\xposed? This is my first Android device in many years and can't remember how to handle OTAs.

pizzaboy192 said:
This is good to know. Any idea if I need to be worried about the phone being rooted\xposed? This is my first Android device in many years and can't remember how to handle OTAs.
Click to expand...
Click to collapse
some roms get ota some dont you must be on stock rom i guess. or wait till they release KDZ.

raptorddd said:
some roms get ota some dont you must be on stock rom i guess. or wait till they release KDZ.
Click to expand...
Click to collapse
I'm running rooted stock because I need band12 and volte where I live and only stock has that working.

pizzaboy192 said:
I'm running rooted stock because I need band12 and volte where I live and only stock has that working.
Click to expand...
Click to collapse
yeah well i have never recive one since am not in the USA. i always used KDZ. so either flash latest 20v or wait but not sure what rom seems all MM have not been updated.

raptorddd said:
yeah well i have never recive one since am not in the USA. i always used KDZ. so either flash latest 20v or wait but not sure what rom seems all MM have not been updated.
Click to expand...
Click to collapse
I just checked and no updates yet. Maybe Xposed and magisk are messing with it.

Is there a way to install it with TWRP installed? I got it and the phone rebooted but only to TWRP.

thejaredhuang said:
Is there a way to install it with TWRP installed? I got it and the phone rebooted but only to TWRP.
Click to expand...
Click to collapse
I think since the H811 has an unlocked bootloader the easiest way is going to be flashing the stock recovery through TWRP, reboot, install the OTA, and then fastboot back into TWRP and reinstall it. (Unless it keeps root through Magisk or something and then you can just use the TWRP app rooted to reinstall)

few days after updated, software version changed into H81120x, my camera suddenly and always crashed and getting hot not like usual. please help me fixing this problem

gregoriusaryanto said:
few days after updated, software version changed into H81120x, my camera suddenly and always crashed and getting hot not like usual. please help me fixing this problem
Click to expand...
Click to collapse
is there a KDZ available yet? maybe you need to do a refurbished flash of KDZ. 20x

pizzaboy192 said:
I think since the H811 has an unlocked bootloader the easiest way is going to be flashing the stock recovery through TWRP, reboot, install the OTA, and then fastboot back into TWRP and reinstall it. (Unless it keeps root through Magisk or something and then you can just use the TWRP app rooted to reinstall)
Click to expand...
Click to collapse
I'm not rooted so no worries. Its there a stock recovery image somewhere or do i need to extract one from the 20v kdz

So is there a directory where the OTA is downloaded to? I have the KDZ for 20v but I can't get a valid cab file to extract the DZ when I use LGExtractor (this is when I'm trying to extract the stock recovery.img).

Update file
Here is the update file for 20x, i extracted it from the /cache directory. I tried to flash it via TWRP but there is some ID checker that errors out and fails to install on TWRP
https://1drv.ms/u/s!AvCSuR2bvtpdg9tZBW-m9yVP6gYGng

For help about root
How to root and install twrp... Plzz help me... Given procedure not working stuck to send command port no.. Position.. Plzzz any one give some help or other way to get root and install twrp. My version is lg g4 h811 20x

Somnathdey said:
How to root and install twrp... Plzz help me... Given procedure not working stuck to send command port no.. Position.. Plzzz any one give some help or other way to get root and install twrp. My version is lg g4 h811 20x
Click to expand...
Click to collapse
THIS MIGHT FACTORY RESET YOUR PHONE. BE SURE YOU ARE OKAY WITH THAT.
1: make sure you've enabled Developer Options in settings (go to About Phone, tap the Build Number a bunch until it pops up saying you've enabled developer options.
2: Make sure you've enabled bootloader unlock in Developer options
3: make sure your device's ADB drivers are installed. The phone comes with the resource CD built in, so you can always use that to make sure it is set up
4: run ADB on your computer, type adb reboot fastboot to get into fastboot mode. The phone should reboot. If it does not, recheck steps 1, 2, and 3.
5: type "fastboot oem unlock". This it should report it as OK or Success. If so, type fastboot reboot. It may or may not factory reset your phone at this point. It didn't with mine but YMMV.
6: once Android has booted, follow the steps to install TWRP. Same steps as above but you'll be booting a TWRP image instead and then flashing it.

For help about root
Have tried this mathod bt still not working my phn stuck in fast boot mode.. In command after typing fastboot oem unlock not working.... Plzz send me some working * platform tools for root in which i can start the command and adb

Somnathdey said:
Have tried this mathod bt still not working my phn stuck in fast boot mode.. In command after typing fastboot oem unlock not working.... Plzz send me some working * platform tools for root in which i can start the command and adb
Click to expand...
Click to collapse
Sure thing. You'll get more help though posting a new thread instead of on one unrelated.

gregoriusaryanto said:
few days after updated, software version changed into H81120x, my camera suddenly and always crashed and getting hot not like usual. please help me fixing this problem
Click to expand...
Click to collapse
No problem here, try to reset the phone or at least clear the cache of camera.

So my phone finally presented me with the OTA, but it fails to install because of TWRP (expected). I grabbed the update.zip and did the basic modification to allow me to flash it via TWRP but it still fails. LG Bridge doesn't get past checking software version. I am running stock, rooted with Magisk, RCTD removed and some minor root-free debloat (The "uninstall apps for user 0" trick)
What LG OEM apps are required to get LG Bridge to work?
Edit: Could I dirty flash a full stock ROM over it (including stock recovery) to get the OTA to work and then just debloat again?)

Does the KDZ file only come from LG? I wonder if I can update and then somehow extract KDZ to share with everyone...

Cant flash TWRP Recovery

Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.

VortexHD said:
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
Click to expand...
Click to collapse
ARE YOU EXYNOS OR SNAPDRAGON ?? Below guide is for EXYNOS!!
Did you follow this guide --> https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143 ??
And did you do step 3 ? 3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card ??i haven't rooted my Note 9 yet but i think that's where you messed up!

Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f

rana14301 said:
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
Click to expand...
Click to collapse
read dr ketans guide in the general discussion thread.

Has anyone managed to root S6 edge G925a 7.0? (build version G925AUCS7ERC1)

I'm trying to root my Samsung Galaxy S6 Edge (build version G925AUCS7ERC1) running 7.0 nougat.
On this firmware, pingpong root does not work. So, today I tried to revert my phone back to android 5.0 by flashing an old rom (build version G925AUCU1AOCE).
It didn't work. I got an error message "REV. CHECK FAILED," which is specifically built in to prevent you from downgrading (**** you Samsung)
Does anyone know how to root this model/firmware?
Thanks

dude use magisk

anon_lastname said:
I'm trying to root my Samsung Galaxy S6 Edge (build version G925AUCS7ERC1) running 7.0 nougat.
On this firmware, pingpong root does not work. So, today I tried to revert my phone back to android 5.0 by flashing an old rom (build version G925AUCU1AOCE).
It didn't work. I got an error message "REV. CHECK FAILED," which is specifically built in to prevent you from downgrading (**** you Samsung)
Does anyone know how to root this model/firmware?
Thanks
Click to expand...
Click to collapse
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com

Zac C4rter said:
dude use magisk
Click to expand...
Click to collapse
That sounds promising. However, it seems TWRP is required to install Magisk. And it seems there is no TWRP image for G925a ( https://twrp.me/samsung/samsunggalaxys6edge.html)
Another problem is that I can't get fastboot to recognize the phone. "adb reboot bootloader" reboots the phone but it doesn't enter fastboot mode.
Do you have any advice on how to get magisk installed on this specific model?

anon_lastname said:
That sounds promising. However, it seems TWRP is required to install Magisk. And it seems there is no TWRP image for G925a ( https://twrp.me/samsung/samsunggalaxys6edge.html)
Another problem is that I can't get fastboot to recognize the phone. "adb reboot bootloader" reboots the phone but it doesn't enter fastboot mode.
Do you have any advice on how to get magisk installed on this specific model?
Click to expand...
Click to collapse
try this https://dl.twrp.me/zeroflte/twrp-3.3.1-0-zeroflte.img.tar.html

Zac C4rter said:
try this https://dl.twrp.me/zeroflte/twrp-3.3.1-0-zeroflte.img.tar.html
Click to expand...
Click to collapse
So, I tried to flash that recovery.img file to the recovery partition of my phone using Heimdall. It didn't work. (The reason I used heimdall is because my operating system is Linux. I'm pretty sure the behavior would be the same on Odin.)
The error message I got on the phone was "SECURE CHECK FAIL : (RECOVERY)"
After doing some research, it seems that on these "newer" Samsung models you're simply not allowed to write these partitions. It seems that Samsung supports installing a custom OS like Lineage, but they don't want you to mess around with the proprietary OS.

anon_lastname said:
So, I tried to flash that recovery.img file to the recovery partition of my phone using Heimdall. It didn't work. (The reason I used heimdall is because my operating system is Linux. I'm pretty sure the behavior would be the same on Odin.)
The error message I got on the phone was "SECURE CHECK FAIL : (RECOVERY)"
After doing some research, it seems that on these "newer" Samsung models you're simply not allowed to write these partitions. It seems that Samsung supports installing a custom OS like Lineage, but they don't want you to mess around with the proprietary OS.
Click to expand...
Click to collapse
This looks like the exact problem I am having:
No OEM Unlock in Developer Options SM-G925A
hi, I have a SM-G925A with Nougat 7.0 and August 2017 security patch, but I can't find OEM Unlock option in developer options, most posts online say that means it should be already unlocked, but when trying to flash twrp with odin in download...
forum.xda-developers.com

Ran into the same problem. PIT file is correct but heimdall and JOdin3 both have issues trying to put TWRP into recovery. I did manage to get JOdin3 to work by adding/replacing the /etc/udev/rules.d/51-android.rules (see attached), but it did not take. Go figure.

Stuck on Odin download

Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?

22350 said:
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
Click to expand...
Click to collapse
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?

lewmur said:
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
Click to expand...
Click to collapse
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.

22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse

this is what the screen says when i try to flash

no content in your post

22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.

lewmur said:
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
Click to expand...
Click to collapse
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways

22350 said:
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
Click to expand...
Click to collapse
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.

lewmur said:
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
Click to expand...
Click to collapse
Yea, well that's the issue. i am in odin downloading, with the correct rom from samobile, but the flash fails each time

i ended up using these two
Stock ROM for the SM-T380 Android 9, Bloatware free TWRP backup
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal...
forum.xda-developers.com
[TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018
Unofficial release -TWRP recovery for the Galaxy Tab A - T380/T385, Qualcomm MSM8917 TWRP 3.2.1-0 Released Dec 9, 2017 TWRP 3.2.1-0 is out now for most currently supported devices. What's new in 3.2.1-0: * minui fixes (cryptomilk) *...
forum.xda-developers.com