yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] :
I tried to flash it several times using ODIN on my T815, but every single time the device reboots, with an " <ID:0/005> RQT_CLOSE !!". I've enabled the developer options and USB debugging, but i cannot find the "OEM Unlock" slider, it's missing. I've also tried rebooting it into fast boot in order to send a "fastboot oem unlock" command but it boots normally. Tried on several computers.

UPDATE: Flashing back from Nougat to Marshmallow Stock didn't help.

Do i have to wait 7 days for the option to appear like with the Note 8/ S8?
[Galaxy Tab S2 Original Android Development] gantagavin:
Does it work for the AT&T version, T817A?
[Galaxy Tab S2 Original Android Development] ubergeek77:
Did we really never resolve the landscape/portrait touchscreen issue with Aroma on the T810? It's driving me insane. OP mentioned that there was a portrait fix for T710 and T715. Will that fix really not work for the T810? I'm trying to build TWRP from source with this fix applied myself, but I've never built Android from source, and it's incredibly complex (not to mention cloning repositories and building stuff is going to take an obscene amount of time for new environments).

While waiting on that (though I have zero confidence in it working), I also tried a custom theme. But when I tried changing the rotation, I ended up cutting off the bottom half of the screen and had to revert the theme.

I'm really just looking for any solution here. Any solution at all. Even if it requires a custom TWRP theme of some sort, compiling from source, trying an experimental build, you name it.
[Galaxy Tab S2 Original Android Development] ripee:
This has long been fixed when I bumped the version to 3.2.1-1.
[Galaxy Tab S2 Original Android Development] ubergeek77:
Great! Thank you for your dedication to keeping this tablet alive.

Where can I get a copy of the 3.2.1-1 build? As I said, I have a T810 (gts210wifi). I see you're the maintainer for the official TWRP builds, but I only see downloads for 3.2.1-0 for this device.
[Galaxy Tab S2 Original Android Development] ripee:
My mistake, I bumped it to 3.2.1-1 for T710 and T715 to avoid the landscape inconsistency. T810 and T815 are at 3.2.1-0 because they work as expected in landscape orientation.
[Galaxy Tab S2 Original Android Development] ubergeek77:
Ok, I don't have the other versions of this tablet, so I'm assuming that means they were broken to some extent in landscape mode. But as I'm sure you're aware, flashable zips that use AROMA don't behave correctly with the touch screen. The UI elements are displayed as landscape, and stretch appropriately, but the touch inputs behave as though they're being displayed in portrait.

In my case, this is happening with this version of TWRP (3.2.1-0), on the T810, when flashing open_gapps-arm-8.1-aroma-20180527.zip, which uses AROMA version 2.70RC2.

Is there a workaround for this touchscreen issue that you know of?

By the way, I completely forgot to mention - adb and MTP in recovery does not work at all in this build of TWRP. I've tried across both Windows and Linux machines, and nothing I do works, even after enabling USB debugging and accepting my computer's fingerprint. It doesn't even show up as "offline" under "adb devices." It's as though the tablet isn't connected via USB at all, like the USB port is disabled. In another modified version of TWRP I used, MTP worked, but adb still didn't (and admittedly that build was a bit buggy).
[Galaxy Tab S2 Original Android Development] gantagavin:
sorry, but can it works for the AT&T variant, T817A? Will the T815 version compatible for it?

And will it be okay if i flash the AT&T version through Odin?

thanks before
[Galaxy Tab S2 Original Android Development] NeWONEx:
MTP doesn't work on T815 Installed driver multiple times, it work when boot to system but not in TWRP . tried every single option to get it works but no luck . maybe there is something you missed to implant .
[Galaxy Tab S2 Original Android Development] ripee:
ashyx's 3.1.0-1 also suffered from this, and I compared his code to mine, as well as jcadduono's code, so it must be something else.
[Galaxy Tab S2 Original Android Development] NeWONEx:
Is there anyway to fix it ?

Thanks for the effort
[Galaxy Tab S2 Original Android Development] ripee:
What did I just write?
[Galaxy Tab S2 Original Android Development] NeWONEx:
ashyx's 3.1.0-1 also suffered from this, and I compared his code to mine, as well as jcadduono's code, so it must be something else.

This is what you just write !

Did you mention if it is fixable or not ? As well as you need to mention it in bug list.
[Galaxy Tab S2 Original Android Development] ripee:
Unless I can determine the cause, I won't know if it's fixable for our tablets, or if it's a bug on twrp's end.

Edit: In comparing gts210vewifi's twrp device tree, I'm pretty sure adb and mtp are determined in the kernel. One possible solution would be to build twrp using bonuzzz's oreo kernel, as that is the only version of his I've been able to compile. I'll look into it.
[Galaxy Tab S2 Original Android Development] bonuzzz:
[MENTION=6005084]ripee[/MENTION] not working mtp is not twrp or kernel issue. just config and init scripts.

take a look in my git more deep. maybe you'll find something interesting and don't forget t710 is my primary dev tablet.

ps: i don't want to publish any unofficial twrp because you have already official ones. And my builds will be only ones because of shared sources. But I dont want to make work for you and fix your bugs, because I continue to think you are very hurry to make official twrp and if you decided to be maintainer you have to publish quality product, because looking at your product we as users evaluate all product (twrp) at all.
[Galaxy Tab S2 Original Android Development] ubergeek77:
I just want to add my two cents and say that ADB doesn't work in recovery either. Hopefully whatever fix is needed for MTP will also cover ADB.
[Galaxy Tab S2 Original Android Development] ripee:
It's not that I was in a hurry to release 3.2.1, it's that I got tired if waiting for others to do so.

I think I know how to fix MTP, but I'll look into it tonight because I work today.
[Galaxy Tab S2 Original Android Development] bonuzzz:
[MENTION=6005084]ripee[/MENTION] for adb find my twrp sources for note4. It has adb working there.
[Galaxy Tab S2 Original Android Development] ripee:
I will tonight, thanks.
[Galaxy Tab S2 Original Android Development] ripee:
Your twrp sources for note4 are nowhere to be found.
[Galaxy Tab S2 Original Android Development] ripee:
I was expecting a bit more maturity from someone who knows more about this than me than a passive-aggressive comment. Here's a very crazy idea: how about you either help me with MTP or take over yourself? This isn't about who does what, it's about making the best builds available to the community.
[Galaxy Tab S2 Original Android Development] bonuzzz:
That's funny. Just interesting, how many official recoveries have you already made?

I told you where you can find fixes. but I will not do your work for you. If you can't, so leave it as it. That's all.

Nobody forced you to be official maintainer. It was only your decision.

I'm really scared to use official twrp for any devices after that.

ps: I didn't, don't and will not pretend to be maintainer on lineage, twrp or elsewhere.
[Galaxy Tab S2 Original Android Development] ripee:
I can't find your fixes because you deleted your trelte repo.

If you're not a maintainer, then what would you call your work on android?

Anyway, I just managed to fix MTP on T810. The others will follow in a few minutes and I'll update the OP then.
[Galaxy Tab S2 Original Android Development] bonuzzz:
[MENTION=6005084]ripee[/MENTION] I mean maintainer of official repos.

forget about adb.
[Galaxy Tab S2 Original Android Development] ripee:
Thanks for the tip of taking a look at your treltexx twrp device tree. You did delete it from your GitHub, but user fuzhengqu had forked it before you had, so I was able to see your work in the recovery/root folder.

I managed to fix both MTP and ADB in my TWRP builds, thanks to your previous work. I am very grateful for your contribution. :)
[Galaxy Tab S2 Original Android Development] hurray:
Hello [MENTION=6005084]ripee[/MENTION]: Thank you for updating the TWRP. :)

I just made a new test-backup with the current TWRP from you and like my last test in december 2017 I get the error message:

==> set selinux context: u:object_r:system_file:s0
E:recv error on uevent

during the backup. Just to inform you that there is still a bug in TWRP which prevents the complete usage (I cant trust a backup which throws errors even at the backup stage).

I am now back on "twrp_3.1.0-1_sm-t810_13317" and everything is good again => Backup and Restore are working correctly

I read a little bit around and found out that there are other TWRP users which have exact the same problem without a solution for now ( I read only the last 5 pages of the thread and there are multiple replies to this error):

https://xdaforums.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084/page220

So I think that there is a bug in TWRP which is not bound to an explicit phone/tablet.

Btw: I am running now your "lineage-14.1-20180427-UNOFFICIAL-gts210wifi.zip" with success. :)
[Galaxy Tab S2 Original Android Development] ripee:
That error message is entirely innocent. I have no idea what's causing it, but my backups restore and boot normally. Sorry that you jumped to the conclusion that this was a showstopper for you. I can assure you that it isn't. Because this is a minor annoyance, I hadn't bothered looking into it so far, but I will.
[Galaxy Tab S2 Original Android Development] hurray:
For me it looks like an error which depending on selinux and that twrp can't read a file. But my knowledge about selinux is limited so I can't help much in this case. It were easier to find the cause if the depending file name was shown also.

The error comes if a backup from /system is running and at a backup of /data.
[Galaxy Tab S2 Original Android Development] ripee:
I added a detailed description of this in the OP, along with bigbiff's reassurance that it's totally harmless.
[Galaxy Tab S2 Original Android Development] hurray:
Thank you for the information!
[Galaxy Tab S2 Original Android Development] t-o-f-u:
ripee, it seems that the changes made to https://github.com/TeamWin/android_device_samsung_gts210wifi on june 4th "Fix MTP and ADB" somehow did not make it into the official twrp-3.2.2-0-gts210wifi.img found at twrp.me.

i was able to unpack the .img, apply the patch from github to the extracted ramdisk, and then repack and flash. my tab s2 then *does* enumerate via usb, and shows up as an mtp device (verified in a win10 vm to work)

however, "adb shell" is not working. adb push/pull seems to work OK, though. the error returned when trying to connect with "adb shell" is:

CANNOT LINK EXECUTABLE "/sbin/sh": library "libc.so" not found

i tried several things, including playing with LD_LIBRARY_PATH in various places in init.rc and init.recovery.usb.rc, launching adbd from twrp terminal after setenforce 0, etc., but i could not get it to work. fwiw, running /sbin/sh from twrp terminal works without any issues.

kinda stumped for the time being.

thanks!
[Galaxy Tab S2 Original Android Development] ripee:
Did you encounter the same problem with 3.2.1?
[Galaxy Tab S2 Original Android Development] t-o-f-u:
usb did not work in 3.2.1 either. are you suggesting to unpack 3.2.1, apply the changes to init.recovery.usb.rc etc., and see if the libc.so error appears then?
[Galaxy Tab S2 Original Android Development] ripee:
I asked because it worked for me on 3.2.1, but I can confirm that it doesn't on 3.2.2. But ya go ahead and unpack 3.2.1 and let us know.
[Galaxy Tab S2 Original Android Development] t-o-f-u:
i just unpacked/patched/repacked 3.2.1. got the same error after trying adb shell:

CANNOT LINK EXECUTABLE "/sbin/sh": library "libc.so" not found

usb otherwise works though.
[Galaxy Tab S2 Original Android Development] t-o-f-u:
[MENTION=6005084]ripee[/MENTION], somehow twrp-3.2.3-0-gts210wifi.img *still* doesn't have the usb patch (to init.recovery.usb.rc and ueventd.universal5433.rc) applied. is twrp's build system pulling an old revision from your repo? i had to manually unpack/patch the files. after unpacking, patching, repacking, and flashing, my SM-T810 as expected enumerated via USB. however, i still got the same "CANNOT LINK EXECUTABLE ERROR".

i had a suspicion something was up with the kernel, and it turned out to be correct. the following change to https://github.com/LineageOS/android_kernel_samsung_gts2 is necessary:

diff --git a/arch/arm/configs/lineage_gts210wifi_defconfig b/arch/arm/configs/lineage_gts210wifi_defconfig
index 524077d2..a9db94ab 100644
--- a/arch/arm/configs/lineage_gts210wifi_defconfig
+++ b/arch/arm/configs/lineage_gts210wifi_defconfig
@@ -4490,10 +4490,7 @@ CONFIG_UNCOMPRESS_INCLUDE="mach/uncompress.h"
#
# Samsung Rooting Restriction Feature
#
-CONFIG_SEC_RESTRICT_ROOTING=y
-CONFIG_SEC_RESTRICT_SETUID=y
-CONFIG_SEC_RESTRICT_FORK=y
-CONFIG_SEC_RESTRICT_ROOTING_LOG=y
+# CONFIG_SEC_RESTRICT_ROOTING is not set

#
# Security options

after making that change and rebuilding, adb shell works as expected:

matt@aquos:~/devel/tab_s2$ adb shell
~ # uname -a
Linux localhost 3.10.9-g1fde4b48 #2 SMP PREEMPT Wed Aug 8 03:57:03 EDT 2018 armv7l GNU/Linux
~ # getprop ro.bootimage.build.fingerprint
samsung/omni_gts210wifi/gts210wifi:7.1.2/NJH47F/6:eng/test-keys

attached is a .zip of a fixed (both usb detected AND adb shell working, no other testing done) twrp 3.2.3 for SM-T810:
[Galaxy Tab S2 Original Android Development] ripee:
So you mean that those 4 lines needs to be commented out or just set equal to n?

cm_exynos5433-gts28lte_defconfig and cm_exynos5433-gts28lte_defconfig have these 4 lines set to n.
[Galaxy Tab S2 Original Android Development] t-o-f-u:
in kernel configs, there is no "n" in the file. it's either =y, =m, # ... is not set, or set to a specific value for example CONFIG_LOCALVERSION="someValue". you could comment out the 4 lines, or delete the 4 lines and add "# CONFIG_SEC_RESTRICT_ROOTING is not set" in their place. it should have the same effect. some utilities that e.g. merge kernel configs would possibly get hung up if you just commented out the lines, though.

basically, once CONFIG_SEC_RESTRICT_ROOTING has been unset, it removes the other options since they are dependent on that. you should just be able to fork the kernel repo and then apply the patch i posted.

it should look like this (i added some lines for context):

# CONFIG_OC_ETM is not set
# CONFIG_PID_IN_CONTEXTIDR is not set

#
# Samsung Rooting Restriction Feature
#
# CONFIG_SEC_RESTRICT_ROOTING is not set

#
# Security options
#
[Galaxy Tab S2 Original Android Development] ripee:
Since when is there no "n"?
[Galaxy Tab S2 Original Android Development] t-o-f-u:
since always?

matt@aquos:~/devel/tab_s2/android_kernel_samsung_gts2$ fgrep =n .config|wc -l
0
matt@aquos:~/devel/tab_s2/android_kernel_samsung_gts2$ fgrep =y .config|wc -l
1309
matt@aquos:~/devel/tab_s2/android_kernel_samsung_gts2$ fgrep =m .config|wc -l
0
matt@aquos:~/devel/tab_s2/android_kernel_samsung_gts2$ fgrep 'is not set' .config|wc -l
2463
[Galaxy Tab S2 Original Android Development] ripee:
Take a look at the rest of the defconfig ;) either y or n or not set. I'll rebuild the kernels later today and build new twrps.
[Galaxy Tab S2 Original Android Development] ripee:
Could you please apply your patch to gts210ltexx and post only the kernel file? In the meantime, I will rebuild twrp-3.2.3-0-gts210wifi. I'm asking you to do it because my build environment is set up right now for lineage-15.1 and I don't have enough space for the cm-14.1 branch from which I cooked the pre-build kernels to use in the twrp android-7.1 branch.

Edit: Nvm, I did it myself. Links in the OP updated to version 3.2.3-1.
[Galaxy Tab S2 Original Android Development] t-o-f-u:
i'm not sure what you're referring to, i'm kind of confused at this point. you are talking about the kernel defconfigs in arch/arm/configs, yes?

edit: ok, i see the configs you linked to on github in the twrp_android_kernel_samsung_gts2 repo. that's not correct syntax. the files were apparently edited by hand at some point.
[Galaxy Tab S2 Original Android Development] ripee:
What are you talking about? What incorrect syntax? How does it matter how those 4 lines were edited? Unless I misinterpreted the patch, why create a patch to modify only 4 simple lines? Seems like the hard way of doing something easy.

You seem to think that only your solution is the right one. Commenting out a line or setting it as "is not set" achieves the same thing.

What does your patch do that I haven't already done?

Can you try the build I came up with and tell me if it accomplishes what your patch intends?

Please do whatever it is you did to gts210wifi to the other 3 variants as well.

Edit: My way works, thanks for bringing this to our attention, but I still think a patch is unnecessary to make this minor change in the defconfig.
[Galaxy Tab S2 Original Android Development] BzZzZz888:
Hi everyone!

I have twrp-3.2.3-1 and when I make a backup the error emerges

I have Leniage OS 14, official.

The same story with twrp-3.2.3-0

Please help :(
[Galaxy Tab S2 Original Android Development] ripee:
Please read the OP.
[Galaxy Tab S2 Original Android Development] BzZzZz888:
Sorry, missed it.

By the way, the error emerges more often when the compression option is on, when it's off the error only emerges at the end of the backup process after "Created digest" and the backup finishes successfully, but I have not restored the backup yet, it might be broken...
[Galaxy Tab S2 Original Android Development] ripee:
Please attempt to restore the backup. If it's not as harmless as I wrote in the OP, I'll ask bigbiff to look into it deeper.
[Galaxy Tab S2 Original Android Development] BzZzZz888:
I've created another backup and this time there were no errors whatsoever :), during restoring the error emerged one time at the end though , but the backup has restored successfully. :)

And one more thing, should I include 'modem' and 'efs' in a backup ? :confused:
[Galaxy Tab S2 Original Android Development] ripee:
Even if your tablet is one of the LTE variants, there's no point in backing up efs or the modem.
[Galaxy Tab S2 Original Android Development] mlinfoot:
Can't boot into recovery

I can flash the official twrp-3.2.3-0-gts28wifi.img successfully from the TWRP app, from TWRP 3.1, and using heimdall, but in each case, I cannot boot into recovery. Holding the power+vol up+home keys brings up the familiar bold white lettering "Samsung ... Android", but it doesn't go into TWRP. Eventually, the screen goes blank and then back to the bold white lettering and this repeats as long as the 3 keys are pressed. I can boot into the system, no problem.

I have the T710 model with TWRP 3.1 and the Nekid-Nook ROM installed. I was hoping to flash LineageOS but it needs TWRP 3.2+. Any ideas, suggestions would be greatly appreciated.
[Galaxy Tab S2 Original Android Development] :
Same issue here (T713 gts28wifi) as above and stuck on (possibly 3.1.x) but unable to load anything else at present. Attempting a heimdall flash soon and will report if the downgrade is successful.

Edit: 3.1.x working from here S2 9.7? Am I missing something? or just a sleepy head today...?

Edit: My error T713 branch is here 3.2.x working fine now
[Galaxy Tab S2 Original Android Development] ripee:
This could be related with twrp 3.1's settings being incompatible with 3.2+. Boot into your rom and navigate to the TWRP folder in internal storage. There will be a hidden file called .twrp or something like that. This contains twrp's UI settings. Delete this file and re-flash 3.2.3-0. You will need to set up all your settings in it, but it should boot properly.
[Galaxy Tab S2 Original Android Development] mlinfoot:
I was so excited to see a reply after all this time, and something that looked plausible, but sadly it did not work. I located the .twrps file and moved it to the trash. Then used the official TWRP app to flash the latest recovery, but when it rebooted it went into a boot loop and would not let me back into recovery. Heimdall flashed the previous 3.1 img and am back where I started.

I do appreciate your reply -- thanks so much. Any other suggestions?
[Galaxy Tab S2 Original Android Development] ripee:
Then it could be that the Nekid-Nook ROM's kernel is incompatible for whatever reason. Make a backup of your rom in twrp 3.1, flash any 7.0 stock image, the start with twrp 3.2.3-0 with Heimdall from scratch.
[Galaxy Tab S2 Original Android Development] mlinfoot:
That did it. A good part of the day spent flashing, rebooting, failing and starting again, and then restoring from backups, but I now have a beautiful LineageOS tablet with a current TWRP recovery. Thank you for your invaluable help.
[Galaxy Tab S2 Original Android Development] tripLr:
Yay found it
[Galaxy Tab S2 Original Android Development] dannychow:
Does any one can format the data (or cache) partition as F2FS?

When I did this, it failed and showed "Failed to mount /data (operation not supported on transport endpoint)".

My device is T815
[Galaxy Tab S2 Original Android Development] MathewSmart:
Any chance of getting a treble supported twrp for the 815 seeing as we won't get any pie ROMs...?
[Galaxy Tab S2 Original Android Development] ripee:
Work has started on Pie, but treble was attempted to be implemented in an unconventional way in Oreo. Sorry but it's not a priority. Once Pie is as stable as Oreo, then we can take a look at treble, but not before then.
[Galaxy Tab S2 Original Android Development] MathewSmart:
Cheers, sounds good. Will keep an eye for Pie then. But if you get treble working, wouldn't making a Pie rom be obsolete seeing as you could just use a gsi?
[Galaxy Tab S2 Original Android Development] adzo73:
Greetings to alk,im feeling my way through this so bare with me please.815y i wish to root?? Op v7.0 no option for OEM unlock in dev options.?.. am I in the right place and is it doable?????
[Galaxy Tab S2 Original Android Development] tripLr:
Set developer mode then ..

So yes, you just download twrp and Odin to your computer

Download magisk 18.1 and magisk manager to your device if you want to keep stock ROM

Flashbtwrp with Odin, immediate boot to download mode then flash magisk then boot to stock install magisk manager.

No need to unlock
[Galaxy Tab S2 Original Android Development] ogilviea:
Hey Folks,

I'm pretty experienced with flashing twrp and custom roms on other devices, but this is my first time with a Samsung device (SM-T710).

I tried updating the bootloader and installing twrp using the latest version of odin. In both cases, the process appears to complete successfully, but neither the bootloader nor the recovery are updated.

I don't have an OEM unlock option in Developer Options.

Any ideas?

---------- Post added at 10:44 PM ---------- Previous post was at 10:23 PM

Forget it! I figured it out [emoji4] At least for twrp, anyway.

Home + Volume Down + Power immediately after flashing twrp (after remembering to disable auto reboot on odin), then switch from Volume Down to Volume Up while holding the other buttons.

A bit fiddly, but it works [emoji4]

Hope this helps someone else with the same problem in future.
[Galaxy Tab S2 Original Android Development] hurray:
[MENTION=6005084]ripee[/MENTION]: Thank you for the TWRP 3.3.0-0. The installation works without problems and the creation of a full backup under Oreo runs without any error messages on my TabS2 (T-810). :good:
[Galaxy Tab S2 Original Android Development] tripLr:
Very common issue
[Galaxy Tab S2 Original Android Development] muaddip:
Hi,

I just flashed the T810XXU2DRJ1.tar bootloader and newest version of TWRP on my T-810 using Odin and it hangs on the startup screen when I boot to Recovery (Power + Volume Up + Home) and my Wi-Fi is also not working, just sits on Turing on and won't toggle on or off.

Any help to fix would be greatly appreciated!!

Thanks