yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] peacepipe:
OK, what is the huge difference of your kernel ashyx and the stock kernel? What was the reason to exclude the encryption support?
[Galaxy Tab S2 Android Development] ashyx:
I suggest you read the OP and a few pages of the thread.
[Galaxy Tab S2 Android Development] Windsor1959:
I have flashed this TWRP. I get adb access when running TWRP. Adb shell works. Reboot commands work. However, when running system, and I try using adb, I still get the "device unauthorized" error.
[Galaxy Tab S2 Android Development] ashyx:
Please explain a little further.

You can get an ADB shell when booted to twrp?

What do you mean you get 'device unauthorized' when running system?

Also could you run the following in ADB and post the output:

adb shell getenforce

Thanks.
[Galaxy Tab S2 Android Development] Lightn1ng:
~ # getenforce
Disabled
~ #

I ran it from a terminal in TWRP, as I don't have access to a computer right now.

When running system with your kernel, "adb" commands respond with "Device Unauthorized." There is no prompt for access on the device. ADB works fine when booted into the TWRP you linked earlier, according to Windsor.
[Galaxy Tab S2 Android Development] ashyx:
OK, so just be clear what you are saying is that adb is now working in twrp?

When you say 'system' you mean booted to the android OS?

To get adb access in the OS you need to enable usb debugging in developer options then accept the prompt when asked to connect to adb.
[Galaxy Tab S2 Android Development] Windsor1959:
I'm busy now but I'll do this late today.
[Galaxy Tab S2 Android Development] dxxvi:
I'll do that this evening. Thanks for something that I can try on :)

Edit: replied too early. Somebody already did that.
[Galaxy Tab S2 Android Development] cengiz.87:
Installing the stock firmware and then rooting solved the problem

-Install the stock firmware with odin, you can find it

http://xdaforums.com/tab-s2/development/stock-official-t713-stock-firmware-t3392404

-After installing the firmware go to recovery and click on factory reset, otherwise you will stuck at samsung logo

-after have a successfull boot on new stock firmware, restart in download mode and follow steps in op

[MENTION=4899305]ashyx[/MENTION] could you add this to the op? That people must be on stock firmware and add the link, before rooting
[Galaxy Tab S2 Android Development] ashyx:
http://xdaforums.com/showthread.php?t=3425938
[Galaxy Tab S2 Android Development] Lightn1ng:
1. Yes, according to Windsor, adb works in TWRP

2. System is booted into Android, yes

3. Yes I know you need to enable debugging and accept the prompt. The problem is that the prompt on the device never appears.
[Galaxy Tab S2 Android Development] ashyx:
Even with usb debugging enabled in developer settings?
[Galaxy Tab S2 Android Development] Windsor1959:
Okay. I don't know if this is still needed or not, but here goes.

When I type the command adb shell getenforce when running MM, this is what I get:

error: device unauthorized.

This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device.

I get this same error when I try anything with adb when MM is running.

When I type the command adb shell getenforce when TWRP is running, I get: Disabled

Yes, usb debugging is enabled on my T-713.

Ashyx, thanks for the wonderful work you do. If I can help you further, please let me know.
[Galaxy Tab S2 Android Development] Lightn1ng:
Yep, its enabled.
[Galaxy Tab S2 Android Development] ashyx:
Try deleting the .android folder in C:\Users\*your_username*\

Then connect your device.
[Galaxy Tab S2 Android Development] Windsor1959:
Sorry, I omitted one important piece of info. My laptop is a Mac. I have adb set up in Terminal.
[Galaxy Tab S2 Android Development] ashyx:
Do you get the option to switch to ptp when you pull down the notification shade?
[Galaxy Tab S2 Android Development] Lightn1ng:
I tried this a few days ago. It didn't work.
[Galaxy Tab S2 Android Development] Windsor1959:
Yes. Should I select it?
[Galaxy Tab S2 Android Development] ashyx:
Try it.
[Galaxy Tab S2 Android Development] Windsor1959:
Same results.

I tried setting up adb in my Windows 10 virtual machine on my Mac. Same results with that.
[Galaxy Tab S2 Android Development] ashyx:
That won't make any difference, it will need to be authorized on the actual host PC for it to work.

Have you tried to simply turn off then on usb debugging while connected.

Also does the revoke option show when searching for usb debugging in the search bar in settings?
[Galaxy Tab S2 Android Development] staakman:
Thanks! Will try this later today! :)
[Galaxy Tab S2 Android Development] staakman:
[MENTION=7105000]cengiz.87[/MENTION] How did you manage to send SuperSU to the tablet? Did you manage to send the files from the pc with adb? Or did you actually send them through some other method?
[Galaxy Tab S2 Android Development] cengiz.87:
[MENTION=7613517]staakman[/MENTION] after installing twrp and boot image from odin, restart your tablet and connect it to your pc and you can transfer Su and xposed to your tablet. After that restart into recovery and install it with twrp.
[Galaxy Tab S2 Android Development] taingster:
Wifi disable issue

Hello. I have the sm-t713NZKEXAR model. Have read all the post and followed everything. After flashing T713XXU1ADP9_no_encryptable_boot wifi is disable. If I don't flash it....it doesn't boot. Can someone help me. I've been doing this over and over now by and restoring through Kies many times already. TIA
[Galaxy Tab S2 Android Development] taingster:
Build number of said tablet is MMB29M.T713XXU1APG1 with July 1, 2016 security patch level. Thanks.
[Galaxy Tab S2 Android Development] ashyx:
Post up your boot.img and I'll patch it.
[Galaxy Tab S2 Android Development] taingster:
Thanks for reply ashyx. Wish I was more knowledgeable. I did read your link to xdaforums.com/android/software-hacking/development-mkbootimg-tools-t2895954 It's foreign language to me. Is there an app to extract boot.img? Only asking as I finally got root and wifi working but with encryption of data partition. Also any disadvantages of root without the encryption. Sorry if its a noob question that's been already explained.
[Galaxy Tab S2 Android Development] ashyx:
You can pull it out of the stock firmware with 7zip.

You only need the boot.img if you want to mount data in twrp.
[Galaxy Tab S2 Android Development] taingster:
Got it. For my purpose, I don't think I'll ever need to mount data in twrp as I can mount external sdcard. Thank you!
[Galaxy Tab S2 Android Development] ashyx:
That's your prerogative, most people like access to data so they can back it up.
[Galaxy Tab S2 Android Development] taingster:
Oh...now that is language I understand. Nevertheless I was up all night trying to do the rooting thing. Already got yelled at by the wife with the amount of time I'm spending tinkering with this new toy. I'll continue to lurk around to see if someone can upload this particular boot.img. Thanks again.
[Galaxy Tab S2 Android Development] jemping:
I have the same problem with disabled wifi on SM-T713; firmware version T713XXU1APG1. Here is the boot.img.
[Galaxy Tab S2 Android Development] texdroid:
thanks for posting it Jemping i have the same problem with disabled Wifi on SM-T713, thanks in advance ashyx
[Galaxy Tab S2 Android Development] staakman:
I've had the same problem, as someone else mentioned before: Installing the stock firmware and then rooting solved the problem.

Step 1: Download the stock firmware from: http://xdaforums.com/tab-s2/development/stock-official-t713-stock-firmware-t3392404

Step 2: After installing the firmware (the *.tar.md5 file) go to recovery and click on factory reset, otherwise you will get stuck at samsung logo.

Step 3: After a successfull boot on new stock firmware, restart in download mode and follow steps in op.

This way the boot.img file posted by OP should work.

Make sure to follow the INSTALL steps and the IMPORTANT steps in the original post.

After you've followed the steps correctly, copy the SUPERSU files to the download folder on your tablet and root it in twrp.

I've copied the files from windows to my tablet .

It's not that hard once you understand what to do :)
[Galaxy Tab S2 Android Development] ashyx:
Can you or anyone else test this boot image patcher to remove DM-verity and Forced encryption.

Instead of flashing one of the boot images in the OP flash the zip below with TWRP.

This was built by jcadduono not me, so props to him, I just modified it for our device and to remove the SEANDROID ENFORCING message.

no-verity-no-encrypt_ashyx

Thanks.
[Galaxy Tab S2 Android Development] psynce:
Thank you

Thanks for the details, DeeXii - this was my first rooting experience and after locating a little additional context to supplement the techbeasts instructions, I was able to get TWRP, 3.0.2-1, and SuperSU onto my SM-T813.

The only issue that I have is that the tablet will no longer charge unless it's booted to download menu. I've set the USB setting in Marshmallow to "Charge your device via USB" and it does not sleep when connected to a PC ("Stay Awake" turned on) Is there a setting somewhere to regulate charging?

Thanks again.

-psynce
[Galaxy Tab S2 Android Development] ashyx:
Shutdown from the OS not twrp.
[Galaxy Tab S2 Android Development] texdroid:
Thanks staakman, worked like a charm!
[Galaxy Tab S2 Android Development] Tyrion74:
Sorry for My bad english. I can not wipe data with twrp. SM-T819
[Galaxy Tab S2 Android Development] ashyx:
Please follow the instructions it states to format NOT wipe.
[Galaxy Tab S2 Android Development] tinlans:
I'm new to the Android world. After reading all posts of this thread, I understand I need a correct patched boot.img matching my SM-T713 device. Unfortunately, I couldn't find it, and I'm unable to unstandand how to use the boot image patcher.

The version string shown on the system information page is MMB29M.T713ZSU1APD5, and the corresponding filename of its stock firmware is BRI-T713ZSU1APD5-20160510145650.zip. I extracted it and got the file T713ZSU1APD5_T713OZS1APD5_HOME.tar.md5. And I renamed it to T713ZSU1APD5_T713OZS1APD5_HOME.tar and extracted the boot.img. I'm not sure if it's the boot.img you need when you help someone patch the boot.img, because I saw other people got it by adb shell. Hence I cannot make sure what's the one directly put into the stock firmware archive. Would you like to help me patch it if it's the right one?
[Galaxy Tab S2 Android Development] ashyx:
No boot.img needed. Just install twrp, select install in twrp and install the boot patcher zip. Format data. Done.
[Galaxy Tab S2 Android Development] taingster:
Tried method on my t713 just now....doesn't boot up. Stuck on samsung logo.

---------- Post added at 03:10 PM ---------- Previous post was at 02:43 PM ----------

I stand corrected....it did boot. Just had to wait a while. But when going back to install supersu root in twrp....it didn't boot.
[Galaxy Tab S2 Android Development] ashyx:
Download supersu v2.76, should work.
[Galaxy Tab S2 Android Development] taingster:
Tinkered around with reinstalling in different orders in twrp between beta-supersu and the no-verity-no-encrypt_ashyx.zip. Got everything booted and working now. Only problem is titanium Backup didn't work. Will need to install apps and configure settings over...not a big deal. Thanks!
[Galaxy Tab S2 Android Development] ashyx:
The order should be: twrp>no-verity-opt-encrypt.zip>format data>supersu
[Galaxy Tab S2 Android Development] taingster:
Yes. What I did initially that didn't boot was twrp>no-verity-opt-encrypt.zip>format data>ran first boot...then went back twrp and supersu.
[Galaxy Tab S2 Android Development] ashyx:
You're saying it didn't boot or you didn't wait long enough with twrp>no-verity-opt-encrypt.zip>format data

Should have been no issues with that.
[Galaxy Tab S2 Android Development] taingster:
It's possible I didn't wait long enough....about 15minutes.

---------- Post added at 07:22 PM ---------- Previous post was at 07:16 PM ----------

Let me clarify. It did boot the 1st boot. Then i rebooted back to twrp to install supersu...that's when it didn't boot ( but it's possible that i didn't wait long enough). But i'm happy everything is working now and can finally do a full nandroid backup.
[Galaxy Tab S2 Android Development] tinlans:
I'm sorry that I'm asking a basic question. The guide I'm trying to follow is the page you mentioned in the thread: techbeasts.com/root-and-install-twrp-recovery-on-galaxy-tab-s2-97-2016-t813n-t819n/ (I cannot post any outside links before I have 10 posts here, so I discard the http prefix.)

Because you suggest I use the boot image patcher now, items after the step 11 are much different. I booted to TWRP (step 11), and I found no ways to send the boot image pacther from my PC to my SM-T713 device. The method described in the step 17 doesn't work because I couldn't find "mount the USB storage" in the Mount menu. I guess it would be shown after flashing the boot image at the step 14, but I have just finished the step 11.

Now there are only 5 checkboxes in the Mount menu: System, Data, Cache, Micro SDCard and USB OTG:

View attachment 3829678

I can only check System and Cache boxes because I haven't purcahsed a microSD card. Should I purchased a microSD card or a USB OTG cable in order to put the boot image patcher and SuperSU to the place where TWRP is able to see it?

I also found a way to send zip files via adb sideload. I will try it tomorrow.
[Galaxy Tab S2 Android Development] psynce:
Thanks ashyx, but I'm not sure what you mean - would you mind elaborating?
[Galaxy Tab S2 Android Development] Datamagi:
Just bought a brand new one but with the build: MMB29MT813XXU1APDB. Shall I wait for a new 'no encryptable boot' for this one or will one of the others work?
[Galaxy Tab S2 Android Development] ashyx:
Doesn't anyone read the OP or the thread? [emoji53]

The boot.img is not required any more, use the BOOT IMAGE PATCHER.
[Galaxy Tab S2 Android Development] tinlans:
The reason might be the content of the guide hasn't been updated. It still tells us to use boot.img:

According to your description, I guess the new steps since the step 12 should be like these:

But now I'm stuck at the new step 12 because I cannot see any mountable USB storage on the Mount menu and have no idea to send no-verity-no-encrypt_ashyx.zip from my PC to TWRP.
[Galaxy Tab S2 Android Development] ashyx:
The guide within the OP is secondary to updates posted in the actual OP and is just for reference.

I cannot change the guide as I did not create it.

After flashing the no-verity-no-encrypt_ashyx.zip and formating the data partition the internal storage will be mountable.

Copy the SuperSU zip to it via MTP or use adb sideload.

USB OTG needs a suitable OTG cable to be mounted.
[Galaxy Tab S2 Android Development] tinlans:
Thank you. I've rooted my SM-T713 device successfully.

I used adb sideload to flash no-verity-no-encrypt_ashyx.zip and SuperSU v2.76. The main issue is that my Windows 7 x64 PC didn't recgonize the adb device. It caused the command "adb devices" listed nothing. I should manually replace it with the Google USB driver which can be found in Android SDK; Samsung Android USB Driver didn't help me. A minor issue is that the BusyBox installation was stuck more than 30 minutes when it showed "removing old copies...". I terminated the process, ran the installation again, and everythong worked smoothly.
[Galaxy Tab S2 Android Development] ashyx:
Fixed version of twrp with working adb.

https://www.androidfilehost.com/?fid=24591000424949357

Ensure MTP is disabled and install the adb drivers whilst in recovery.
[Galaxy Tab S2 Android Development] ashyx:
Sorry post #11.
[Galaxy Tab S2 Android Development] DeeXii:


---------- Post added at 05:31 PM ---------- Previous post was at 05:06 PM ----------

TWRP Bugs so far:

Internal Storage wont mount (external SD will)

/data will not mount (invalid argument)

MTP is not working (nothing mounts in windows while conntected via USB)

CPU Temp is incorrect

ADB Sideload doesnt work.

There is a mouse like cursor stuck in the middle of the screen

Wiping Dalvik fails
[Galaxy Tab S2 Android Development] ashyx:
Data and storage won't mount because they are encrypted.

This also means dalvik cache can't be wiped.

Format data and storage and they'll mount.

ADB won't work as previously stated because of Samsung's root protection, custom kernel is needed.

No idea on the mouse cursor, no one else has reported it, did you have your USB cable attached at the time?

CPU temp is a per device issue, for some it works and some it doesn't.

MTP won't work until I can build a custom kernel.

Out of that lot the only issue that concerns me is being unable to mount encrypted partitions.

TWRP should at least ask for the password

I need the recovery log posting. Nothing can be done without it and I'm still waiting for the output from:

ls -l /dev/block/bootdevice/by-name/
[Galaxy Tab S2 Android Development] DeeXii:
Format data and storage how?

No I did not have a USB cable attached at the time.

will try and get that output for you.
[Galaxy Tab S2 Android Development] ashyx:
Using the advanced wipe options in twrp.
[Galaxy Tab S2 Android Development] DeeXii:
Is that the ideal way to handle that?
[Galaxy Tab S2 Android Development] ashyx:
Well it's up to you, do you really have a need to have an encrypted device?

I don't and wouldn't because of the issues it brings.
[Galaxy Tab S2 Android Development] suzook:
I am getting aT813 this week, will be forward to using this! I guess custom kernel wont be around till sources are released?
[Galaxy Tab S2 Android Development] ashyx:
Ah my old friend, I know I can rely on you! :D
[Galaxy Tab S2 Android Development] suzook:
:D Yup! I can test anything you have up your sleeve.
[Galaxy Tab S2 Android Development] DeeXii:
So MM auto encrypts on setup?
[Galaxy Tab S2 Android Development] ashyx:
Yep, encrypted by default. Unless you're unusually anal about device security I'd rather not have it.

For a start you can't access any of your data by any other means, except on the device itself.

Yes an unlocked device can be plugged in and accessed via a PC, but what happens if you forget your password/pin.

What's gonna happen if your device somehow becomes corrupt or you need to get some data off it, but you can't boot the OS?

Yes then custom recovery becomes your lifeline.

Not only that it was abandoned in Android 5 because it just wasn't usable on many slower devices.

It affects performance, obviously this depends on your device.

Can you post me the recovery log I need.

Not a lot I can do without it because I'm still a little confused as to why twrp isn't at least asking for the password.

I know the flags I have set are correct, so need to see what the log says.
[Galaxy Tab S2 Android Development] DeeXii:
u0_a138@gts28vewifi:/ $ ls -l /dev/block/bootdevice/by-name/

lrwxrwxrwx root root 2016-01-22 13:49 aboot -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2016-01-22 13:49 apnhlos -> /dev/block/mmcblk0p34

lrwxrwxrwx root root 2016-01-22 13:49 backup -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 2016-01-22 13:49 boot -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 2016-01-22 13:49 bota -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 2016-01-22 13:49 cache -> /dev/block/mmcblk0p37

lrwxrwxrwx root root 2016-01-22 13:49 cmnlib -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2016-01-22 13:49 config -> /dev/block/mmcblk0p29

lrwxrwxrwx root root 2016-01-22 13:49 ddr -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2016-01-22 13:49 devcfg -> /dev/block/mmcblk0p31

lrwxrwxrwx root root 2016-01-22 13:49 dsp -> /dev/block/mmcblk0p32

lrwxrwxrwx root root 2016-01-22 13:49 efs -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 2016-01-22 13:49 fota -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 2016-01-22 13:49 fsc -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 2016-01-22 13:49 fsg -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2016-01-22 13:49 hidden -> /dev/block/mmcblk0p38

lrwxrwxrwx root root 2016-01-22 13:49 hyp -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2016-01-22 13:49 keymaster -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2016-01-22 13:49 keystore -> /dev/block/mmcblk0p28

lrwxrwxrwx root root 2016-01-22 13:49 limits -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2016-01-22 13:49 modem -> /dev/block/mmcblk0p33

lrwxrwxrwx root root 2016-01-22 13:49 modemst1 -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2016-01-22 13:49 modemst2 -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 2016-01-22 13:49 mota -> /dev/block/mmcblk0p30

lrwxrwxrwx root root 2016-01-22 13:49 pad -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2016-01-22 13:49 param -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2016-01-22 13:49 persdata -> /dev/block/mmcblk0p35

lrwxrwxrwx root root 2016-01-22 13:49 persist -> /dev/block/mmcblk0p25

lrwxrwxrwx root root 2016-01-22 13:49 persistent -> /dev/block/mmcblk0p26

lrwxrwxrwx root root 2016-01-22 13:49 recovery -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 2016-01-22 13:49 rpm -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2016-01-22 13:49 sbl1 -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2016-01-22 13:49 sbl1bak -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2016-01-22 13:49 sec -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2016-01-22 13:49 ssd -> /dev/block/mmcblk0p24

lrwxrwxrwx root root 2016-01-22 13:49 steady -> /dev/block/mmcblk0p27

lrwxrwxrwx root root 2016-01-22 13:49 system -> /dev/block/mmcblk0p36

lrwxrwxrwx root root 2016-01-22 13:49 tz -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2016-01-22 13:49 userdata -> /dev/block/mmcblk0p39

u0_a138@gts28vewifi:/ $

---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------

Is there a way to disable encryption from within the OS with out formatting each?
[Galaxy Tab S2 Android Development] ashyx:
Not that I know of.

Thanks for the post above, but I also need the recovery log.

It's under Advanced in TWRP.
[Galaxy Tab S2 Android Development] DeeXii:
What file name does it generate?

---------- Post added at 04:45 PM ---------- Previous post was at 04:30 PM ----------

OK so I tried a few things...

First I tried to wipe data and internal storage in TWRP. This failed with the same mount message. How can one wipe something that won't mount?

Next tried to export the log. It said it saved a log to data/media but nothing was there. There was some sort of recovery log in data/log but that might not be the one you are looking for. I assumed the reason it didn't save to data/media was because TWRP still cannot mount data or internal storage.

Attached is a screenie of the mouse cursor I was talking about.

Also I noticed that when I chose "never show this screen during boot again" on the keep system read only, it doesn't stick. I can restart and it still shows that screen.
[Galaxy Tab S2 Android Development] ashyx:
Your issues are all interrelated to the inability to mount data.

You can't save the recovery log to internal storage if it can't be mounted.

Your settings don't stick for the same reason.

You need to change the default storage to sdcard under MOUNT that should fix both of those issues.

You need to format NOT wipe the data partition.

Select WIPE then hit the FORMAT DATA button.

I need the log BEFORE you format data.
[Galaxy Tab S2 Android Development] DeeXii:
Let me know if its okay to format now. :)
[Galaxy Tab S2 Android Development] ashyx:
Thanks you're good to go.
[Galaxy Tab S2 Android Development] DeeXii:
Did that log help you?
[Galaxy Tab S2 Android Development] ashyx:
It does, it at least tells me what the error is but not why.

It seems the information that it needs to decrypt which should be at the end of the data partition, either can't be read or is missing.
[Galaxy Tab S2 Android Development] micger21:
hello,

What is the process to just root the tablet without installing TWRP?

?Thank you for your reply.
[Galaxy Tab S2 Android Development] micger21:
Hello

Je pense que ce n'est pas possible au regard du nombre de réponses à ma question ...
[Galaxy Tab S2 Android Development] ashyx:
English translation please.