yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
on firmware 7.1.1 in the file /system/build.prop there is a line ro.security.vaultkeeper.feature=1,

the RMM patch changes 1 to 0 and then the OEM Unlock item does not disappear and the RMM Status Prenormal line does not appear...

but here is on firmware 8.1.0 Oreo in file build.prop no line ro.security.vaultkeeper.feature=1, and there's nothing to edit ;)

P.S. tried 8.1.0 firmware of all regions for T385 and even for T385M & T385C (it is clear without the bootloader and the modem(part of the BL & CP), they from T385 ) and never saw RMM Status Prenormal

put stock firmware and got Root times 50 or more ...

don't understand why...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Well I can't explain the above, however the simple fact of the matter is if you see STATUS = PRENORMAL in download mode then this is because of RMM lock.

If you don't flash the RMM bypass zip then you will likely get RMM locked.

Also be aware there is more than one build.prop on Oreo.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kbarker90:
Is there any fix to the screen distortion yet? LMK if there is anything I can help with or help test anything.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Yes, in the N950F firmware file there is a line ro.security.vaultkeeper.feature = 1

However: 1) it is a different device, not the T380 / T385 discussed

2) this is not firmware 8.1.0, but only 8.0.0

I believe that Samsung in firmware 8.1.0 for model T380 / T385 removed RMM Status, but strengthened the protection of the kernel, which even Magisk v18.0 does not take

and if the device was 7.1.1 and had the status Prenormal,but it has been updated by air(OTA) or ODIN to 8.1.0 Oreo, then this device will never be able to customize ,since with firmware 8.1.0 you can’t downgrade to 7.1.1 in full, including the bootloader ...

(in the above firmware T385DDU1ARH1 bootloader version 2)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rooble88:
Troubles finding Magisk file

Thanks for the guide! I am having trouble with installing magisk though.

I have a Samsung Galaxy Tab A SM-T380 with Android 8.1.0. I'm following this (I think) guide on this forum, but I keep having trouble finding the Magisk.zip file in TWRP. Here's a recap of my steps.

1-Installed Magisk manager on tablet & downloaded most recent magisk.zip through that. It is saving to Internal Storage/Downloads.

2-Enabling Developer options, USB Debugging and OEM in system settings.

3-Flashing TWRP (twrp_3.2.3-1_sm-t380_oo_4119.tar linked in OP) via Odin.

4-In TWRP recovery, under "wipe" using the "format data", then rebooting back to TWRP.

5-Attempt to flash Magisk.zip, but I cannot even find the downloads folder. I have checked data, data/media, sdcard, sys, and system and a few various subfolders of the one's mentioned as well as a few others that seemed like a longshot.

I guess my question is what am I doing wrong? do I need to manually save/move the zip to another location (couldn't find a way to do that via magisk manager). Or do i need to get an external sd with the zip on it? Any help would be appreciated.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
in point 1, you copy the file to the built-in memory, and in point 4 after format data this memory is cleared ...

Copy Magisk.zip to extSdCard (external memory card),

in TWRP this is Micro SDCard

After Format Data, choose Install - Select Storage - MicroSDCard - OK - select the file Magisk-v18.0.zip - make Swipe ...

You can also use FlashCard via the OTG adapter.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rooble88:
That's what i figured, but the guide didn't specify that, so I thought that the format data function wasn't actually a wipe, but rather a way to de-encrypt so you had full access to folders. I'll give it a try tomorrow when I can pick up an SD card. I'll let you know if it works.

Edit: Apparently I can't read and missed the whole "this will wipe internal storage" part of the guide.... I feel like the guide should mention that downloading magisk to external storage is required. The last time I rooted a tablet, you could save internally.. I assume this is because of security update.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Yes, format data is done to decrypt the memory, but before that you must apply the encryption disable patch, otherwise the memory will be encrypted again ...

The patch was posted above on page 32 :

https://xdaforums.com/showpost.php?p=78626163&postcount=311
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rooble88:
Okay, just saw this post and now I'm mildly confused. So i need to apply this patch before formatting data? I got a micro sd with the latest Magisk on it, but it would appear that I'm unable to access the micro SD through TWRP currently (/external_sd is empty). I'm available for the immediate future if anyone is willing to help me.

Edit: Just to clarify, I cannot select other storage options. I'm going to try going through the process from a fresh install just to make sure that the tablet is connecting with the SD card properly. I did notice that the most recent version of TWRP may have some compatibility issues with some SD cards.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Yes, first apply the encryption disable patch, then take the format data and installation Magisk.zip.

Memory card, use no more than 32 GB, since 64 GB and more cards are formatted in exFat, which TWRP does not understand
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
TWRP has its own partitioning and formatting tools.

Its not strictly the size but the Format that is the issue.

Use TWRP to partition and format the sd card to FAT32 or any other windows partition tool such as Mini partition tool or even Windows itself will be fine.

There is also an app called Aparted.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Did you format your SDcard in Android Oreo as a Portable Storage?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I have a 64GB card and it is formatted on the computer in exFat, in the device it will also be formatted in exFat

the map works without problems, including in the stock recovery,

however, in the new TWRP for firmware 8.1.0 it is not visible,

therefore, I use FlashCard 32 GB Fat32 via OTG adapter

don't want to reformat the 64 GB extSdCard to Fat32,as it is possible to map only 32 GB :(

P.S. the card up to 32 GB will be formatted by the device in Fat32 and will work in TWRP Oreo
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Don't confuse Windows file/partition size limits with actual limits.

Fat32 actually supports partitions up to 2TB and a 4gb file size.

It is also possible with 3rd party tools to change the file system without loss of data.

Even TWRP is able to do this without data loss if I remember rightly.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Thanks for clarifying!

You can change the file system in TWRP, but there are exotic formats, except exFat & FAT

I prefer the exFat format, so I will not change it, for TWRP I use FlashCard 32GB in Fat32 format via an OTG adapter, I even backup to it and successfully :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Well hopefully I will figure out the issue and have it fixed soon.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] duckredbeard:
Can the OP be updated with a list of known issues?

I believe I have read that Titanium Backup isn't working and TWRP may not be able to read the External SD card. Can anyone confirm these or add any info?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] yousry2:
Does this work for TAB A 8.0 4G LTE SM-T387 Android 8.1 Qualcomm MSM8917

thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Yes, when obtaining Root rights via Magisk_v18.0, we have a non-working Titanium

TWRP for firmware 8.1.0 does not see a memory card in exFat format, this format is automatically set when formatting 64GB or more cards in the device

If you use cards up to 32GB, then they are formatted by the device in Fat32 format and work in TWRP
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] duckredbeard:
Do ad blockers get necessary root privileges ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I can not answer, because I do not use ad blockers, except those built into the same UC Browser

Often, because of the blocker,you will not go to the desired link ...

root privileges is received by all applications and Titanium, but something is not enough for it to work ...

MagiskManager does not work either, it cannot reinstall Magisk.zip and then I do it through TWRP

The problem is in Magisk itself, in the incomplete support of our device on firmware 8.1.0, a respected ashyx wrote about it

All other applications work - RootExplorer,X-plore,BK Manager,Phone Info,TTL Master,Terminal,Quick Reboot and others...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Evul1:
Well thanks guys. At least NOW I know I won't ever be able to root this tablet and I've been wasting my time for several weeks. I'm pretty sure when my tablet updated to Oreo back in December, I was in the midst of the 7-day wait after one of the multiple failed attempts to root Nougat. So this means the RMM status was likely Prenormal when the tablet updated to Oreo, which apparently means it's now stuck that way for good.

I'd imagine I'm not the only one whose tablet updated this way, then went on to spend a bunch of time trying to find a root solution in futility. The OP should include a disclaimer that if your tablet was updated to Oreo during a 7 day wait, and it displays an RMM status of Prenormal in download mode, you won't be able to use this root guide.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Have a look at this: https://xdaforums.com/samsung-a-series-2017/how-to/guide-root-install-twrp-samsung-t3747535

Hope you can better understand this issue and fix it. Just remember that ROOT for OREO is not yet 100% reliable (beta status) so I recommend you to wait till a new update comes along.

Only thing I can do is suggest you to flash latest firmware via ODIN choosing CSC (not Home CSC), enable OEM Unlock if available, if not wait 7 days without rebooting the device and try again.

Cheers.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] juzzdoit:
So with the beta status of Root that would explain why titanium, link2sd and repetitouch cannot gain root privelege? Just a case of wait for a new release? I followed the instructions and rooted successfully just cannot get the apps I want working properly.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Evul1:
I appreciate the response but unfortunately this isn't anything I haven't already tried. I've already flashed the latest US and Korean firmware and used the CSC file instead of the Home_CSC file in the CSC slot in Odin. As previously discussed, OEM Unlock isn't the issue as it is available as soon as you unlock developer options after a clean flash of Oreo. I'll check download mode again in a couple days and if RMM status finally goes to Normal, then great, I'll try flashing TWRP again, but I'm certainly not holding my breath.

This so-called "security feature" from Samsung really is silly. It locks you out of the bootloader simply if your device updated at the wrong time. It's supposed to deter theft, but all it's deterring is me buying another Samsung tablet.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Yes, I see 2 options: 1)to buy the new device and to consider experience of it 2) to roll back a firmware from 8.1.0 on 7.1.1 ,including a loader . But this is only possible on a computer running Linux . I did not do it myself,but there is a message from the user Mef_poter on the forum 4pda.ru about successful rollback to firmware 7.1.1

don't know if you can give a link to the message forum 4pda.ru but you can find it there in the subject Samsung SM-T380/T385 Galaxy Tab A 8.0 - Discussion...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
I'm afraid we need to. I rooted my tab just to get Adoptable Storage, but with Oreo, I just can't.

I gave up and I'm staying with Official Oreo till an improved TWRP arrives. :crying:

Cheers,
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Evul1:
Well I'm definitely not buying another one seeing as how much of a pain this one has been. But as far as going to another forum and reading through another dozen pages of posts, digging out my linux live usb, figuring out how to use Heimdall, rolling back to Nougat (which is reportedly impossible because there is a physical fuse inside the tablet that is destroyed once it updates to Oreo), then going to back to the beginning and trying to root Nougat using methods that didn't work for me previously...I just don't think it's worth the time. This is a cheap, decent tablet even without root, and I'd like to just customize it and use it normally and not have to worry about downloading and flashing 2gb files with Odin just to get the OS to load. I'll check back periodically to see if there' s ever an official TWRP release that comes out for the t380, but otherwise, I'm done chasing my tail. I've never had a device that was this difficult to root.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
This is not so, there is no physical protection,there is only software protection from downgrading the bootloader version and firmware parts...

read this: https://xdaforums.com/galaxy-tab-a/...10-02-2018-t3747564/post78578657#post78578657

Returned several times on the firmware 7.1.1 T385DDU1ARH1, but it loader version 2, and dear Mef_poter returned to the original 7.1.1 completely, but by means of Linux

A tablet is very good and without Root-rights! has excellent autonomy on 7.1.1 and even better on 8.1.0

Also found a way to save and restore applications and data for many of them, using tools SmartSwitchMobile + extSDCard and Helium program to save data of many applications

Good luck!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Austcool:
Has anyone gotten the good old Systemd supersu to work

---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------

Wait your talking about downgrading the SM-T380 brother please explain the process

---------- Post added at 06:43 PM ---------- Previous post was at 06:07 PM ----------

[MENTION=4899305]ashyx[/MENTION] I have a self build kernel How can I repack it with memory decryption
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I tried to use SuperSU - I get a bootloop, because the SuperSU version is old and does not disable kernel protection :(

For the T380 there is no transition firmware of the type T385DDU1ARH1, which is version 7.1.1, but has a bootloader version 2! that is why it is possible to roll back on it with firmware 8.1.0

You can downgrade the version to 7.1.1 using Linux, but this is a question for the user Mef_poter

To disable encryption on Oreo, you need to patch not the kernel, but the file /system/vendor/etc/fstab.qcom

the patch was posted here on page 32 : https://xdaforums.com/showpost.php?p=78626163&postcount=311
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Tami Andranunes:
What have I done wrong?

in status appears RMM State= Prenormal, but in developer OEM says is disabled !?

https://drive.google.com/file/d/1qC7hHabsbjRBcYe2KlZBjxQinLW2rWMi/view?usp=sharing

When doing the root it appears "Only official released binaries are allowed to be flashed"

https://drive.google.com/file/d/1tnGVtCLVwVGOEH3Mr15_C8S6-NHwKn24/view?usp=sharing

my settings

https://drive.google.com/file/d/12umbLAC2a8zx1WNXkf-AcFKYFDhH2vfQ/view?usp=sharing
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Maybe you rushed to upgrade to firmware 8.1.0 already having the status of Prenormal and now it is not known how to get rid of it ...

There is a user in the subject with a similar problem with the T380 device

What is the current firmware (build)?

You seem to be able to return to firmware 7.1.1 version 2A, for example T385MUBS2ARJ1

Firmware can be downloaded from here: https://updato.com/firmware-archive...85M&exact=1&r=&v=Nougat(Android+7.1.1)&rpp=25

When flashing, use the CSC_ part (not HOME_CSC)

wait for the absence of the RMM Status: Prenormal line and then flash 8.1.0
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Tami Andranunes:
OK, I'll try this.

thks!

edit: I tried to go back to 7.1.1, but it was not successful. "getting device tree address failed. Can not get fdt. Download Mode."

I'm tired of so many mistakes to get a decent root.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I recommend when installing firmware 7.1.1, first select and flash the BL & CP parts and then, without turning off the device, flash the AP and CSC parts

this procedure is chosen practice

after flashing part of BL & CP, the device will reboot with the new bootloader,which will allow to flash further parts of AP & CSC .

P.S. On firmware type T385MUBU 1A RC1 version 7.1.1 will not be able to return, because the bootloader is version 1, and the version bootloader cannot be downgraded

Good luck!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Austcool:
[MENTION=4899305]ashyx[/MENTION] the kernel you posted on Android file host with the defex patch is confirmed to work on the sm-t380 with magisk v18 it gives me full root but has after awhile of running the device I get a nasty distorted color bug after a reboot it works fine for awhile then it randomly triggurs after using the device for awhile.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
I'm aware of that bug. I need to rebuild the kernel again. Not sure what's actually causing it though.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Austcool:
Ok thanks keep me posted.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Austcool:
[MENTION=4899305]ashyx[/MENTION] when I build the kernel with the defex disabled I get this error

arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 8 of arch/arm/crypto/built-in.o is not in EXIDX output section
arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 1463 of kernel/built-in.o is not in EXIDX output section
arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 602 of mm/built-in.o is not in EXIDX output section
arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 1047 of fs/built-in.o is not in EXIDX output section
arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 181 of security/built-in.o is not in EXIDX output section
arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 53 of crypto/built-in.o is not in EXIDX output section
arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 541 of block/built-in.o is not in EXIDX output section
arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 460 of lib/built-in.o is not in EXIDX output section
arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 102 of drivers/built-in.o is not in EXIDX output section
arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 6 of sound/built-in.o is not in EXIDX output section
arm-linux-androideabi-ld: warning: unwinding may not work because EXIDX input section 1001 of net/built-in.o is not in EXIDX output section
net/built-in.o:sock.c:function sock_set_dns_pid: error: undefined reference to 'check_ncm_flag'
net/built-in.o:rmnet_data_stats.c:function sk_alloc: error: undefined reference to 'check_ncm_flag'
net/built-in.o:nf_conntrack_core.c:function nf_ct_add_to_dying_list: error: undefined reference to 'check_ncm_flag'
net/built-in.o:nf_conntrack_core.c:function nf_ct_add_to_dying_list: error: undefined reference to 'knox_collect_conntrack_data'
net/built-in.o:rmnet_data_stats.c:function __udp4_lib_rcv: error: undefined reference to 'check_ncm_flag'
net/built-in.o:rmnet_data_stats.c:function __udp4_lib_rcv: error: undefined reference to 'knox_collect_conntrack_data'
make[1]: *** [/home/noire/Desktop/Android/kernels/SM-T380_SEA_OO_Opensource/Kernel/Makefile:956: vmlinux] Error 1
make[1]: Leaving directory '/home/noire/Desktop/Android/kernels/SM-T380_SEA_OO_Opensource/Kernel/out'
make: *** [Makefile:145: sub-make] Error 2
make: Leaving directory '/home/noire/Desktop/Android/kernels/SM-T380_SEA_OO_Opensource/Kernel'
cp: cannot stat 'out/arch/arm/boot/zImage': No such file or directory

I'm going to try putting "is not set"
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Austcool:
If anyone is interested in helping expand the information in this here https://github.com/Austcool-Walker/android_device_samsung_gta2swifi.git
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Austcool:
That tree above is a unfinished LineageOS tree for the sm-t380 it was made by my friend [MENTION=8080659]andr01dfr3ak[/MENTION]
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jerrylee8:
Hello i flash twrp TWRP_3.2.3-1_sm-t380_4119 Oreo and i don't access to internal storage and Micro SD Card but only 64GB and 128GB. Card 8GB it's working. How to make two silent cards work too ? All cards are the same formatted.

How to make internal storage work and not show 0MB.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
You need to apply the decryption file:

https://xdaforums.com/galaxy-tab-a/...10-02-2018-t3747564/post78626163#post78626163

Install the patch from TWRP and do format data (yes), after which the built-in memory will be available.

for 64GB & 128GB cards to work, you need to enter exFat format support into the current version of TWRP.

Either format a 64 or 128GB card in fat32 on a computer, then they will be visible in TWRP
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Apologies, I have no idea where the HOME bit went from they key combo, it should be there! That's standard procedure on Samsung devices.

Corrected.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Winston Churchill:
lol Thanks mate. Wasn't just you... couple of other root tutorials on here had it wrong too. I said on another thread where I pointed out I thought maybe you were wrong that most of you super wizards just know your buttons and come to the tutes to get the files but I've spent years on cheap crappy old devices so it's a bit of a boon to get 2 Samsung devices within 9 months.... plus when I do flash stuff (not often) it's usually just root....first time I've ever had a device that TWRP could run on :)

Some of us are pretty clueless and need to be told what to do XD hehehehe.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Winston Churchill:
ashyx - might you consider adding a post script to your tutorial about OEM-unlock and "only officially released binaries are allowed to be boot..."?

I had read about this in another thread somewhere, sort of forgot about it, it's late and was half asleep and as you didn't mention it here I rebooted to go into TWRP after checking root was fine (it was) and to set backup location to my SD card and OOOPS! I'm in a bootloop of that error message.... as a few others reported on another thread.... so tomorrow when I'm awake I'll flash stock ROM and go through it all again.

Maybe add the bit where you're supposed to do this....just for us sort of newbs who aren't all that savvy and can then get what we need in the one place? I think this is what you have to do to stop this problem:

>By TWRP file manager make sure that in "build.prop" file option "ro.security.vaultkeeper.feature" set to NULL: ro.security.vaultkeeper.feature=0

>Delete app "Rlc". To do this you need to mount /system, go to "/system/priv-app" & del "Rlc" dir.

(or do it in a Root Explorer before you reboot again which would be easier for somebody like me. All this mounting of things is a bit new to me).

Just a thought :)