yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I have flashed the complete T385DXU2BRK3_XME_20181126094414 with the part CSC = CSC_, that is, with the reset of data

The result is the same - when you try to enter the recovery, the device enters the Downloading mode ...

T380DXU2BRK3 I can not flash on T385 ...

Can it work exclusively on the T380 model?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
On which model and firmware?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] djb77:
Its working :)

I was able to flash Magisk 18.0 via the new TWRP without any issues :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Once again I downloaded and flashed the recovery again - it does not start and goes into Downloading mode :(

I have a T385 with firmware T385DXU2BRK3, but I tried on different firmware
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] djb77:
Its coz the new update is only for T380 afaik
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
I'll upload another build that hopefully boots on your device.

https://www.androidfilehost.com/?fid=11410963190603891941
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Matty1993:
Works perfectly fine on my T380 running 8.1,

Rooted with magisk V18.0 currently

Big thanks to #ashyx for the quick turnaround since the source was released wasnt expecting it this quickly to be honest
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Thanks!

Recovery started, but not mounted Micro SD Card, size 0 bytes :(

With the built-in memory, nothing is set, since format data is being made ...

64GB card and in exFat format ,maybe this is the problem

I will try through OTG

The device saw a 32GB Fat32 card through OTG and successfully installed Magisk.zip v18.0

Waiting for download ...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
So the same card works via OTG, but not in the card slot?

Can you post the recovery log file?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
No, SdCard in exFat does not work through OTG either!

SdCard works in Fat32 format

Address log recovery? how to pull out?

found...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
So fat 32 works OK just not exfat?

Seems the exfat driver is not loaded by the kernel will have to take a look at that.

Go to advanced/save log.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Yes exactly!

I tried through OTG 2 SdCard in exFat & Fat32, only Fat32 works

In the apparatus did not insert, but I think it will also

P.S. recovery.log posted above
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Have you got the exfat sdcard inserted into the slot?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
The device has SdCard 64GB in exFat format and it does not work in recovery,

so I used SdCard 32GB in Fat32 format via the OTG port
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
[MENTION=9559283]Kbarker90[/MENTION] which file system is your microsd card using?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
A 64GB exFat card is installed and working in the device.

But in the recovery mode, it is not mounted: (

P.S. I connected to the port OTG Flash-card 32GB Fat32 via OTG adapter
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Shinko02:
I'm using Oreo 8.1 USA and I'm having problems repacking the boot image. Root apps don't work the whole thing is semi rooted.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
[MENTION=9559283]Kbarker90[/MENTION] has a 128gb sdcard that is mounted OK in twrp.

I want him to confirm what file system it uses.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Repacking? :confused:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Also Root access is not full

Titanium does not work and TWRP did not help in this

on firmware 7.1.1 everything was great

problem on 8.1.0
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Which version of magisk?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Shinko02:
17.3 tried 18.0, I rooted with data mount errors flashed dm verity 6.0 I still get one error that is "E:"
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
First 18.0, then 17.1 ,

the problem is the same

P.S. I noticed that after downloading to the system and back to recovery TWRP, the / data partition is not mounted again.

P.P.S. stock recovery sees my SdCard 64GB exFat :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Shinko02:
I tried to install magisk over magisk and it ended up failed to repack boot image
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
You guys need to install v18. DM-verity patch doesn't work on Oreo.

Only Magisk v18 can patch Oreo correctly.

It's important data is formatted first and magisk v18 are installed at the same time.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Shinko02:
On v18 I still get the failed to repack boot img error not through twrp but through magisk I can't install any magisk module either
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
OK, I'll put this plain and simple.

Magisk cannot patch the boot image via magisk manager, why you are using this method I don't know? :confused:

It MUST be installed via TWRP immediately *after* Formatting the DATA partition.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Used 18.0 & 18.1

I do in TWRP format data-yes, I install Magisk.zip, I reboot into the system - there is Root, but incomplete - Titanium does not work, Magisk does not complete the installation

P.S. I think the problem is in Magisk on firmware 8.1.0 and here we can not do anything :(
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
I'm guessing Samsung have made changes which makes the defex patch ineffective.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I agree!

and after all on our device there will be also 9 android Pie ;)

I will continue tomorrow ...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kevinscottt:
My OEM lock is off, but I still have that doggone RMM Status: Prenormal showing. Am I stuck in 7 day purgatory, or is there a way around it? Firmware updated and date set to 8 days ago hasn't helped yet.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
This should fix the root issue for now however MTP will have issues.

Flash with TWRP.

T380:

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

T385:

https://www.androidfilehost.com/?fid=11410963190603892139
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Shinko02:
Do you flash magisk with this?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Yes will need to follow the rest of the guide after flashing the boot.img.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Shinko02:
My screen is having green and blue colors show up and is saying unauthorized software is installed please restart to reset tablet.
[MENTION=4899305]ashyx[/MENTION]
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kbarker90:
I previously had it formatted to work on my Linux system, honestly I am not good at this stuff and can not remember what format it was before hand, but it was not registering properly in TWRP. That is why I was playing around with the partition sdcard function in twrp. I formatted it to ext4 from there (in twrp). After that it registered fine. Was able to save recovery logs and install zip files from it.

Edit: Checking it in the DiskInfo app shows the file system is sdcardfs. Idk if that is any help. LMK if there is anything I can do to provide more information.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Yep, having this too. Apparently after the screen goes off and I bring it on again, the whole screen goes in a sort of Accessibility mode, but is not. I can change it back to full colour by changing colour in display settings, but as soon as the screen goes off, the issue comes back.

Encryption still is there after flashing Magisk 18 and following all the steps of the first page.

I cannot flash anything after because of the data partition not mounting.

Cheers.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I flash with TWRP t385_defex_patched_boot.img as img for boot -

appeared stock recovery T385DXU2BRK3 ,when choosing Reboot system now

comes back to recovery ... after wipe data/factory reset comes back to recovery :(

I had to return the original kernel and recovery...

P.S. Need to disable memory encryption

Is it possible to adapt the patch Tabs3_oreo_forced+encryption_disabler.zip ,

he, too, for the platform Qualcomm Snapdragon ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Whoops sorry my error. Repacked the stock recovery instead of the boot image. :silly:

Magisk shouldn't really be having issues with patching decryption, but I can fix this also.

Do you have fstab.qcom in system/vendor/etc?

If you have it could you post it here.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
To fix the unauthorised software message, disable Securitylogagent apk.

Not sure about this blue screen thing though? Screenshot?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Here you go.

I had to take a photo since is only a display bug or something. It goes away if the blue filter is on, otherwise comes back after screen off, and on again.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
yes,I have file in zip
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
t380dxu2brk2
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
The kernel is based on BRK3 so maybe suggest updating first.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
BRK2 is latest for Australia, BRK3 is for KOREA only. There is no other update at the moment.

I dont think is that, there is another guy who also experienced this behaviour.

Anyways, i'll wait and see.

Thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
BRK3 is Samsungs latest source release. It's the CSC that is region specific not the kernel and rom.

Even Samsung themselves often mix all 3.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Evul1:
I need some clarification on this, as I'm still having an issue flashing TWRP, and this seems like it may potentially be the cause.

I'm running M1AJQ.T380DXU2BRK2, and according to my tablet when I go to Software Update, this is the latest update available. Developer options are enabled, USB debugging is enable, OEM Unlock is enabled, however RMM state is still Prenomral in download mode. When I try to flash twrp_3.2.3-1_sm-t380_oo_4119.tar in the AP slot in Odin, Odin fails and I get the infamous "only official binaries are allowed to be flashed error". This is peculiar since I know I'm well past the 7 day wait, as I haven't done anything to this tablet since it updated to Oreo weeks ago. Are you suggesting that I need to flash a BRK3 version of the firmware before this version of TWRP will flash? It seems unlikely that this is necessary, since no one else in this thread who has rooted with the new TRWP has mentioned having to do this, so I'm not sure what to do next...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
You will not be able to flash TWRP until RMM state is still Prenomral in download mode...

I recommend flashing the current firmware T380DXU2BRK2 or T380DXU2BRK3 necessarily with data reset,

using the CSC_ part (no HOME_CSC)

Or, reset the data from the device Settings

Is the Auto update system option enabled?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Evul1:
As I said in the post of mine you quoted, I'm already running the current firmware, T380DXU2BRK2, so I'm not sure why you would recommend that.

I just did a factory data reset, went through all the setup steps again for the tablet, made sure OEM Unlock, USB debugging, and Auto system update were all enabled, put the tab in download mode, and RMM state is still Prenormal.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Try to change the date, check the update and restart the device! on 7.1.1 it gave the result and gives the result on 8.0.0 other models...

If the problem is in the system, then this can be fixed only by flashing it — resetting it to the factory settings does not restore the integrity of the system ...

therefore, there was a recommendation to reinstall the current firmware
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
You are right, but what I meant is that the only build with BRK3 is Korea's. You can check Sammobile. ;)

Every other is BRK2. Just saying. Thats what I feel both should not be that different since the only difference is a number, not a letter.

As far as I know, usually the letter indicates a new "major" build. I could be wrong though.

Regards.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
You wouldnt think so would you, but Samsung have a habit of twiddling and breaking things.

It could simply be a change in the dtb. If you provide me your boot image I can repack the kernel with it and confirm.

Also im still scratching my head with this exfat scenario.

It works in android but not in twrp? :confused:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Attached the boot image from the AP folder, or if something wrong you can download it from here:

https://www.dropbox.com/s/0nqkivzd3u0elaf/boot-BRK2..zip?dl=0

Don't have any problem with SDCARD, I could read it from both, Android and TWRP. I formatted the card once via Android and no issues there.

The only two issues I found are the screen distortion, as you know, and the encryption which comes back no matter what. (Magisk 18 installed at the same time)

I'm currently back on stock, so I can confirm the issue is not hardware related. Ready to try new version of TWRP when ready.

Cheers,
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Yes,exFat it works in android but not in twrp (twrp_3.2.3-1_sm-t385_oo_5119) !

in stock recovery it works

But this is a problem only for those who have SdCard 64GB and more, the device formats up to 32GB in Far32 and they are visible in TWRP

Topical issue with memory encryption, how would I disable it?

P.S.

I'll attach the boot from the firmware T380DXU2BRK3 ,its size is slightly different from the T380DXU2BRK2
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Is your sd card exfat and what size is it?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Is 32 GB, not sure if exfat, I formatted it with Android.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
Memory cards up to 32GB are formatted by the device in Fat32 format, and 64GB or more in exFat format

You can check the format of your memory card on the computer ...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
According to DiskInfo app, the file system of my 32GB sdcard is SDCardFS

Apparently it was made by Samsung and adopted by Google on Oreo.

Cheers,
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Shinko02:
Do you guys think it's Magisk or TWRP not providing full unencryption? It might be that magisk that needs a new hexpatch into the new defex patch.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I turned off the memory encryption and now entering the recover mode again, the data section remains mounted,

can do nandroidbackup...

However, this did not change anything - Root access is incomplete - Titanium not working and magisk cannot reinstall :(
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
How did you turn it off, and where?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
If you have a T380 you need the boot image I posted a few posts back.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I used the edited patch from dear

ashyx

I use for T385 model,It works on the model T380,since the file /system/vendor/etc/fstab.qcom is the same ...

In TWRP we establish a patch, we do format data - yes, we establish Magisk.zip, we reboot the device in a system	...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
no, the file is necessary	/system/vendor/etc/fstab.qcom
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Did you modify the patch or is it already working as is?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
I'm referring to the defex patch not encryption.

My patched boot image is required for full root.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Is that boot image already fixed? I remember having bootloops after flashing it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
and where to take it for T385 and T380? or how to make it?

P.S. while installed the firmware 7.1.1 T385DDU1ARH1 and use full root rights,

tired of fighting 8.1.0 :(
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
That's because it's only for the T380. I have yet to upload a proper T385 version.

In any case the patched boot image is only a stop gap. It really needs fixing in Magisk as this issue is solely related to root not TWRP.

The way to get this fixed is to report it to the developer of Magisk.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Sorry mate, but my Tab is a T380 and I got bootloops when I tried.

I'm asking because you replied to someone that by mistake you use stock recovery for that image, is that correct or I misunderstood?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
the answer was given to me...

judging by the size 13.81 Mb is it patched the kernel to T380 ,and T385 here for incorrect size 17.93 Mb and it was patched recovery T385

if you only replace the kernel, then get bootloop, you need to apply Magisk.zip to disable protection...

try again :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I modified the patch using as a base patch for Tab S3 ... without modification, the extSdCard did not work

modified file /system/vendor/etc / fstab.qcom changed by analogy with the file in the patch Tab S3

link to the original patch: https://androidfilehost.com/?fid=890278863836288163
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
OK, saves me a job. ;)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
T380 boot image is OK, so should be working. Remember, you still have to install Magisk immediately after flashing the boot image.

T385 was repacked with recovery instead of boot by mistake.

Shall fix that.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Yep, I tried once more with Magisk after the boot image, no bootloops.

Unfortunately, I got the Color Issue on the screen, apparently that boot image is the culprit.

Maybe someone else could try and tell.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Austcool:
does the decryption zip patch work?

does it work with the sm-t380 Oreo?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Yep that's the issue at the moment until I can figure a way to fix it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Does what work? :confused:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Austcool:
does the decryption patch work on Oreo
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
the old memory encryption disable patch does not work on Oreo! working patch I posted on the previous page...the patch works on the model T385, will work on the model T380, as the file fstab.qcom same with T385
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
I can confirm it works on the T380!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Evul1:
This still didn't solve my issue. Changing the date never worked for me on 7.1.1, and it still doesn't. I did a clean flash of the stock firmware. RMM state still Prenormal, Odin still fails to flash TWRP and I still get the "only official binaries" message.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
I changed the date to 8 days ago, then 8 days in advance, then turned on the time autodetection and each time did a reboot and update check,as a result, there was an item unlock OEM and disappeared line RMM status Prenormal and it was on firmware 7.1.1

on firmware 8.1.0 I have enabled OEM Unlock and it remains after 50 firmwares... ;)

Yes, it must be enabled Wi-Fi or mobile network
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Evul1:
I'm not trying to be rude here, because you're trying to help and are the only one responding, but it looks like you maybe don't understand what my issue is.

I've been trying to root my tablet for 2 months. I've read every post in this forum about the T380. I've tried all the different methods to root. None of them worked for me on 7.1.1 Nougat or on Oreo. I was just mentioning that the date spoofing thing didn't work for me on Nougat, and its not effective on Oreo because, as you said, OEM Unlock is visible immediately regardless, even if you flash the firmware 50 times. So that part isn't the issue, clearly.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Talich52:
The problem with RMM status is not only on Tab A, I first saw it on Note 8 and there much depended on the region of the firmware

On firmware 7.1.1 of some regions, it was difficult or impossible to remove the lock, on others it was shot immediately after the firmware, try flashing the firmware of another region with resetting data ...

And yet - in some cases, the lock is not related to OEM, so look at the display of the device in Downloading mode, are there any other messages next to RMM status Prenormal? and status Prenormal or another?

P.S. Disabled OEM Unlock, in firmware mode it became FRP LOCK: ON; OEM LOCK: ON, the RMM Status Prenormal line did not appear, but the device does not boot and asks to install the stock firmware ... This is on firmware 8.1.0
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Austcool:
Yes I also have tried it and the data partition is now decrypted ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] duckredbeard:
Been following this thread for a while and I believe I am ready to do this. I am OEM lock = off, FRP lock = off, USB debugging enabled, running build M1AJQ.T380DXU2BRK2 (Android 8.1.0). I have attempted to download the twrp_3.2.3-1_sm-t380_oo_4119.tar file from the first post but W10 is flagging it as a Trojan threat. Same issue from all mirrors. What is up with that?

Is the "To disable forced encryption and mount internal storage (/DATA)" step required with my current configuration?

Is the "OREO ONLY: 5. Flash the RMM bypass zip" step required with my current configuration?

What do those steps accomplish?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Don't be paranoic, is just a false positive, you should know that.

Just Flash TWRP via ODIN

On TWRP Format Data

Then flash Magisk

then the file located on this post (click on the yellow arrow):

Then RMM. (I did not see any difference with or without it to be honest)

Reboot

You should be ok. Just remember you are the only one responsible of any issue from doing this. :)

Cheers,

---------- Post added at 09:27 AM ---------- Previous post was at 09:18 AM ----------

Ok, this is the way I would (did) do it.

1. Flash latest firmware from Sammobile via ODIN, use CSC to delete all data and start fresh. Run the setup normally

2. Enable OEM unlock, USB debugging in Dev Options.

3. Flash TWRP in AP slot via ODIN anddo all the rooting process explained here.

If that does not work, then my friend we cannot help you here. Something must be wrong with your tablet or country firmware.

Cheers,
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
If you are running Oreo and you don't install the RMM bypass zip you run the risk of being RMM locked by Samsung. You will lose all ability to flash anything and you may not get it back.

Read the last few pages of the thread and also search the forum for RMM bypass for more info.