Database Users

Android Pay Compatibility?

Hi,
Wondering if anyone has succeeded in using Android Pay on their Mi Note 2?
I have the bootloader unlocked on mine and while I've had a play with Magisk and such, unsurprisingly since the bootloader is unlocked I'm not getting anywhere.
I'm aware there are kernel hacks that can return support to unlocked devices but I'm having a hard time telling if I'd require the full kernel source in order to implement them or if there are any other ways around this or if it is simply to MIUI being an unsupported ROM. I have heard that running stock MIUI with a an originally locked bootloader still fails SafetyNet and is incompatible. With the difficulties Xiaomi place on unlocking/relocking the bootloader etc
I was hoping someone who is still running stock would be able to verify it works on a stock device
If you could also post a screenshot of the ROM you're using that would be great. With so many devices shipping with vendor ROMs rather than the official it only complicates things further.
I'm happy to keep trying and post a tutorial for others if I can get it working but frankly at this stage if the issue is MIUI itself rather than the state of the bootlock then I'd rather not waste any more hours on this.
Cheers,
StoneTrap

Can confirm Android Pay works - I am using a rom provided by Hong Kong Goldway. I haven't rooted yet but I will see if it works afterwards.

thedeejay said:
Can confirm Android Pay works - I am using MIUI Global Stable 8.0.9.0.0. I haven't rooted yet but I will see if it works afterwards.
Click to expand...
Click to collapse
That's great to know.
I'm guessing your bootloader is still locked if you're unrooted. I'm fairly sure that's the only thing left tripping safetynet. AFAIK there's no bypass until we can build our own kernel but I'd love for someone to porve me wrong.

Did you try to lock bootloader again?
I think the Magisk trick is for hiding root, not unlocked bootloader.

terstor said:
Did you try to lock bootloader again?
I think the Magisk trick is for hiding root, not unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the reply.
Like I said, I realise the issue is the unlocked bootloader. I know what Magisk is for
What I was asking is if a full kernel source is needed to build a hacked kernel that supports an unlocked bootloader meeting SafetyNet or if there are is any way of patching or rebuilding a pre-existing one?
There are already compatibility issues with some MIUI versions and Android Pay even with a locked bootloader. Rather than testing every rom myself I was wondering if anyone here had any experience with it working on a certain rom.

I know that you know
I'm just curious if android pay will work again if you lock bootloader again for example using 'fastboot oem lock'.
If someone is unlocking bootloader to install custom recovery only, it would be good idea to unlock -> install recovery -> lock -> install android Pay.
But does anyone know if this will work? Is this fastboot "lock" differs from the original "lock"?

terstor said:
I know that you know
I'm just curious if android pay will work again if you lock bootloader again for example using 'fastboot oem lock'.
If someone is unlocking bootloader to install custom recovery only, it would be good idea to unlock -> install recovery -> lock -> install android Pay.
But does anyone know if this will work? Is this fastboot "lock" differs from the original "lock"?
Click to expand...
Click to collapse
Ah sorry it's hard to tell sometimes when people are making posts just to hit that first 5 posts for access. If there was a signed recovery file, Magisk would be perfect for all sorts of hi-jinx (Like for example on the ZTE Axon 7)
Unfortunately because of the way xiaomi controls unlocking the bootloader there is no way to have a custom recovery and a locked bootloader. The recovery would have to be signed by xiaomi in order to boot it.
Signing system components isn't something I know much about, all we seem to have access to is the firehose in the fastboot images but even then with the way xiaomi have locked down fastboot it seems to require some kind of authorisation first.
I was able to flash the custom recovery with a locked bootloader by modifying a fastboot image before flashing and reclocking. This just forces the phone into EDL mode when trying to boot into recovery. The system itself continues to work and will quickly overwrite the unsigned recovery with the MIUI one if an attempt to boot into recovery doesn't happen.
The locks are all the same, this can be checked with
Code:
fastboot oem device-status
on locked and unlocked phones.

Ok, so if I understood correctly, custom recovery will stop working when i will lock the bootloader.
Sorry for the little offtop, but i have another question connected with this issue. And i can't verify it by myself because i'm still waiting for unlock approval. What will happen in this scenerio:
stock rom *stable* (not dev) -> unlock bootloader -> install custom recovery -> flash eg. SuperSu.zip (to get root) via recovery -> instal magisk/xposed -> lock bootloader.
3 questions:
1. Will root 'survive' after locking or not?
2. Will xposed/magisk survive and works correctly or not?
3. OTA updates will be available or not?

I can confirm locking the boot loader and flashing original firmware global works with Android pay
Sent from my Mi Note 2 using Tapatalk

I am able to get Xiaomi Mi Note 2 and Android Pay working WITH Magisk and unlocked bootloader.
1. Install Magisk
2. Install this patch
There are some issues with files unmounting correctly. I had to manually stop and start magisk hide to get this working.
But right now, I have Android Pay confirmed working, with an unlocked phone.

thedeejay said:
I am able to get Xiaomi Mi Note 2 and Android Pay working WITH Magisk and unlocked bootloader.
1. Install Magisk
2. Install this patch
There are some issues with files unmounting correctly. I had to manually stop and start magisk hide to get this working.
But right now, I have Android Pay confirmed working, with an unlocked phone.
Click to expand...
Click to collapse
Sorry, I have one more question. Which root did you use? (SuperSU, MagiskSU, or ?)

Felixweaster said:
Sorry, I have one more question. Which root did you use? (SuperSU, MagiskSU, or ?)
Click to expand...
Click to collapse
MagiskSU

thedeejay said:
MagiskSU
Click to expand...
Click to collapse
Sorry, which ROM do you install in phone?
I installed the modified MIUI 8 China Developer ROM 7.5.6 without root in my phone.
After flash Magisk V.12 in twrp 3.0.2.0, the Magisk do nothing in my phone.

Felixweaster said:
Sorry, which ROM do you install in phone?
I installed the modified MIUI 8 China Developer ROM 7.5.6 without root in my phone.
After flash Magisk V.12 in twrp 3.0.2.0, the Magisk do nothing in my phone.
Click to expand...
Click to collapse
I am using MIUI Global Stable 8.2.5. However, with the patch (which I think you haven't installed), it shouldn't matter which ROM you are using - China or Global, Stable or Dev. What the patch does is mainly changes the build.prop to a recognised device version and a few other things on the back end to hide being unlocked.

thedeejay said:
I am using MIUI Global Stable 8.2.5. However, with the patch (which I think you haven't installed), it shouldn't matter which ROM you are using - China or Global, Stable or Dev. What the patch does is mainly changes the build.prop to a recognised device version and a few other things on the back end to hide being unlocked.
Click to expand...
Click to collapse
My problem is nothing working after flash Magisk only or with patch!! Q___Q!
I will test and discuss with other people and developer on Sunday with new ROM.
Thank you very much.

Felixweaster said:
My problem is nothing working after flash Magisk only or with patch!! Q___Q!
I will test and discuss with other people and developer on Sunday with new ROM.
Thank you very much.
Click to expand...
Click to collapse
Can you send a copy of your Magisk log? Go to Magisk -> Log and click on Magisk.
I have a feeling that the issue may be that Magisk might not be unmounting correctly. There is quite a bit of a discussion on this (as well as even MORE patches to get this to work)
(and to make sure, you also don't have xposed?)

thedeejay said:
Can you send a copy of your Magisk log? Go to Magisk -> Log and click on Magisk.
I have a feeling that the issue may be that Magisk might not be unmounting correctly. There is quite a bit of a discussion on this (as well as even MORE patches to get this to work)
(and to make sure, you also don't have xposed?)
Click to expand...
Click to collapse
You can find the log as attached.
I did NOT have xposed.

Felixweaster said:
You can find the log as attached.
I did NOT have xposed.
Click to expand...
Click to collapse
It is mounting xposed so you still have traces of it left. Go through these steps:
flash this file in TWRP: - Xposed Uninstaller
Reboot. Check if Magisk is working. If it is not, reboot back into TWRP and flash Magisk v12.0 again: Latest Magisk
Reboot. Do a few keypresses before going back into TWRP. Flash This patch here: Xiaomi safetynet fix v1.3
Reboot back into system, and check if SafetyNet is working (can be done in Magisk Manager). If it isn't, reboot into TWRP once again and flash THIS one here: Magisk v12.0 fix
(So total of 4 files that need to be flashed and cycled through).
Also make sure that you DO NOT clear cache/dalvik cache at any stage!
Give that a shot and let me know how it goes.

thedeejay said:
It is mounting xposed so you still have traces of it left. Go through these steps:
flash this file in TWRP: - Xposed Uninstaller
Reboot. Check if Magisk is working. If it is not, reboot back into TWRP and flash Magisk v12.0 again: Latest Magisk
Reboot. Do a few keypresses before going back into TWRP. Flash This patch here: Xiaomi safetynet fix v1.3
Reboot back into system, and check if SafetyNet is working (can be done in Magisk Manager). If it isn't, reboot into TWRP once again and flash THIS one here: Magisk v12.0 fix
(So total of 4 files that need to be flashed and cycled through).
Also make sure that you DO NOT clear cache/dalvik cache at any stage!
Give that a shot and let me know how it goes.
Click to expand...
Click to collapse
After flash Xposed Uninstaller & reboot => magisk nothing working
After flash Magisk v12.0 => magisk nothing working
After flash Magisk v12.0 again & Xiaomi safetynet fix v1.3 => magisk nothing working
After flash Magisk v12.0 again & Xiaomi safetynet fix v1.3 again & Magisk v12.0 fix => magisk nothing working
After flash Xiaomi official root
I get the same error log as attached.
I also attach the recovery log in attachment.
When I check the recovery log, there are something strange as below.
============
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
grep: init.rc: No such file or directory
sed: init.rc: No such file or directory
sed: init.rc: No such file or directory
Cannot open init.rc
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Cannot find the file entry [sepolicy]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Can't open 'sepolicy': No such file or directory
Could not load policy
Cannot open sepolicy
......
......
- Flashing new boot image
I:Set overlay: ''
5745+0 records in
5745+0 records out
23531520 bytes (22.4MB) copied, 0.291553 seconds, 77.0MB/s
- Unmounting partitions
losetup: /dev/block/loop0: No such device or address
umount: can't unmount /system: Device or resource busy
- Done
I:Updater process ended with RC=0
I:Legacy property environment disabled.
I:Install took 30 second(s).
I:Install zip Success,and install cofface-no-verity by cofface.
================

1. After flash the TWRP Unofficial TWRP 3.1.0-0 Mi Note 2 (scorpio)
2. Mount the /system read-write (I'm NOT sure do it cause something wrong?)
3. flash Magisk v12.0 => magisk working, saftnet false
4. Xiaomi safetynet fix v1.3 => magisk working, saftnet false
5. flash Magisk v12.0 fix => magisk working, saftnet true (before check saftnet, I found Magisk Hide in Magisk Manager and I also selected the safetynet attest app.)
Three more question
1. When you flash Magisk, is the /system read-only ?
2. Where do you have Magisk v12.0 fix ??
3. Why do you ask to flash Xiaomi safetynet fix v1.3 not Xiaomi safetynet fix v1.6 ?
thedeejay!! Thank you very much!!

CTS Mistmatch... tried 'everything'. Help me fix?

Hi, my set up was working fine, safety net passed etc.
I'm on the latest 7.1 rom, patched stock kernel (ta_poc etc)
But today I encrypted my device and then flashed the new TWRP we have - https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
I then notice in Magisk that there is a CTS mismatch...
Maybe the cause of the CTS mismatching happened a few days ago, I'm not sure.
Anyway, I want to fix it!
I tried flashing the latest rom via flashtool, I did a factory restore from system settings, I also tried flashtool again + wipe data in flashtool, I tried using the 'old' TWRP.
Each time, I flash Magisk v12, install the magisk manager 4.3.3.
I still get a CTS mismatch.
I have tried toggling magisk hide, then rebooting, toggling core mode, then rebooting, nothing seems to work.
Does anyone have any advice that can help me?
Will anything bad happen if I tick all of the boxes to 'wipe' in flashtool? (apps_log, diag, persist, qnovo, ssd? userdata - (that one's safe I know))
I would really appreciate it.
Thank you.

Ok, some news.
From what I understand, the safety net check is online.
So, it can be updated and improved by Google/Android, to detect our hacks.
I can only assume that whatever state my system was in, was no longer good enough or no longer hidden enough to pass the check.
I flashed the only true custom kernel we have, Genesis kernel (1.05), I didn't patch my TA keys in using ta_poc, I read Magisk v13 has problems with ta_poc.
I simply used the drm_fix version, as long as the features are all there (I read drmfix fixes everything apart from wideside, I don't know what that is...)
I flashed the drmfix version, installed Magisk v13, it is recognized and works! (unlike on my patched stock kernel) -- and my device passes safety check again

qvmuhuuxz said:
I read Magisk v13 has problems with ta_poc.
Click to expand...
Click to collapse
Don't you have to use ta_poc and the RootKernel tool together for Magisk to work properly?

XperienceD said:
Don't you have to use ta_poc and the RootKernel tool together for Magisk to work properly?
Click to expand...
Click to collapse
Yes I did that, and it was working with magisk v12 but not 13.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342
" 4. Tobias tool has to be used to repack the boot image because I found that if PoC image is used directly, phone will reboot unexpectedly after Magisk is installed. "
With genesis kernel I have updated magisk and safety net passes, plus I am using the new trwp we have so my device is encrypted.
I'm very happy

Rooting OREO (41.3.A.2.24)

I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?

Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?

deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!

Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148

Can't Install Magisk [Lineage 15.1] [ZE552KL]

I've installed the Magisk manager and can't quite get the Magisk file installed. TWRP gives an error, which I'll throw down here
Code:
- Mounting /system, /vendor, /cache, /data
- Device platform: arm64
- Constructing environment
- Adding addon.d survival script
- Found Boot Image: /dev/block/mmcblk0p58
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! Please restore stock boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v14.0-zf2-20170906.zip'
Updating partition details...
...done
Do I really have to reinstall a stock image? I don't want to lose all my installed data. I've reflashed the phone a billion times getting various things to work, and now that I'm on a stable ROM, I don't want to move over. I've heard this can be an issue with having SuperSU installed. I'm just trying to get certain apps to work, like Fire Emblem Heroes or Animal Crossing Pocket Camp.
I'm welcome to answer any questions anyone has, I just want it fixed.

Kaisogen said:
I've installed the Magisk manager and can't quite get the Magisk file installed. TWRP gives an error, which I'll throw down here
Do I really have to reinstall a stock image? I don't want to lose all my installed data. I've reflashed the phone a billion times getting various things to work, and now that I'm on a stable ROM, I don't want to move over. I've heard this can be an issue with having SuperSU installed. I'm just trying to get certain apps to work, like Fire Emblem Heroes or Animal Crossing Pocket Camp.
I'm welcome to answer any questions anyone has, I just want it fixed.
Click to expand...
Click to collapse
Why did you flash older version of Magisk? Try flashing Magisk V16 or Magisk Beta V16.3.
https://forum.xda-developers.com/apps/magisk

Saktis_STi said:
Why did you flash older version of Magisk? Try flashing Magisk V16 or Magisk Beta V16.3.
https://forum.xda-developers.com/apps/magisk
Click to expand...
Click to collapse
That was from earlier. I have tried the newer version, it still gives the same error. I've also tried unrooting and it still does.

Kaisogen said:
That was from earlier. I have tried the newer version, it still gives the same error. I've also tried unrooting and it still does.
Click to expand...
Click to collapse
Reflash newer TWRP and try again.

Saktis_STi said:
Reflash newer TWRP and try again.
Click to expand...
Click to collapse
Doesn't change anything, still gives the same error. Magisk 16, and TWRP 3.2.1 for ZE552KL Unofficial

Kaisogen said:
Doesn't change anything, still gives the same error. Magisk 16, and TWRP 3.2.1 for ZE552KL Unofficial
Click to expand...
Click to collapse
Try this method:
1) Flash Oreo RAW
Link: https://forum.xda-developers.com/zenfone-3/development/updated-unlock-relock-bootloader-t3749456 (end of the main post)
2) Boot phone until homescreen
3) Flash TWRP 3.2.1 by @planet9 (make sure you flash the latest version of TWRP)
4) Flash Magisk Beta (v 16.3)
5) Reboot
P.S: Make sure you've backed up all of your important data before flashing

With "Please restore stock boot image" the Magisk installer just want's to tell you to reflash the currently installed ROM: Simply reflash the zip of your ROM (LineageOS), then flash Magisk. No data will be lost by doing that.
The word "stock" is quite misleading here as it doesn't refer to the asus rom.

Rooting SM-T380 with Pie

I am trying to re-root my SM-T380 after updating to Pie and am following the latest process per [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but am running into some issues with steps 3 & 4.:
Boot to TWRP
Format the Data partition (not wipe) using the FORMAT DATA button under Wipe options
Install the memory decryption patch
Assume this is the file found in Ashyx's siganture Samsung encryption disable patch but I can't find any mirrors when trying to download it. Is this the right file for the memory decryption patch?
Install the modified kernel
The file for the SM-T380 found in this post appears to be for the T380DXU3CSI5 but the current stock image is T380DXU3CSL2 for the latest firmware installation (Jan 2020 security patch). I assume a new kernel is needed for this latest version. Is that the case? Also, the file is in tar format but need in zip format to flash in TWRP. Is it as simple as repackaging the tar into a zip file instead?
Install Magisk
Thanks for the help!

I will write out what I just got to work with the latest update of Android Pie for the Samsung Galaxy Tab A T380 running T380DXU3CSL2, security patch January 2020. I have tried all of the methods on the main TWRP/Root thread (which is now closed) and only had success with one.
To clarify, yes - using the patched boot.img from ashyx that was made from T380DXU3CSI5 WILL work with T380DXU3CSL2 (latest as of time of writing) just fine. Make sure to flash Stock first and OEM Unlock.
Ashyx does give some files still needed in his/her first post on the main TWRP thread, but the boot image and the DM-verity are buried within a 66 page thread. Out of respect for ashyx's wishes I will not direct link to files. Get TWRP from the first post here. The patched boot image and DM verity no encrypt get from the guide here by user zfk110. Pg. 65 of the TWRP thread. The guide itself did not work for me though. Just grab the files.
So, files you will need:
>twrp_3.2.3-1_sm-t380_oo_4119.tar (TWRP)
>T380DXU3CSI5_patched_boot_111119.tar (boot.img inside the .tar)
>Latest Magisk version here
>Tab_A_2017_Pie_forced+encryption_disabler-1.zip (no-verity-no-encrypt)
Not only have I found RMM Bypass unnecessary, but in my many trials I think maybe it was causing an issue for me. Perhaps someone much smarter than I can explain, but there is no setting in build.prop to need it - I did check.
TWRP/Root:
>Flash TWRP with Odin with "Auto Reboot" setting turned off: (file: twrp_3.2.3-1_sm-t380_oo_4119.tar in AP slot)
>Boot straight to TWRP (home + vol down + power to get out of download mode then as soon as the screen flashes swap to home + vol up + power),
>In TWRP main menu press "Wipe" and the "Format Data", type "yes" to proceed.
>Reboot to TWRP by going back to main menu of TWRP, select "Reboot" then "Recovery"
>Install boot.img to your boot partition from your external SD card in TWRP (there is a YT video how to do this within TWRP if you need help, just Google it. The file you need is: T380DXU3CSI5_patched_boot_111119.tar then extract boot.img from that for TWRP (use ZArchiver or a program that will unzip .tar). It MUST be in .img to install it with the TWRP "Image" button. TWRP won't even read that the .tar is there, and I don't recommend Odin for this)
>Install Magisk from your external SD card (I used the latest, 20.4 just fine)
>Install the DM-Verity Forced Encryption Patch from your external SD card (file: Tab_A_2017_Pie_forced+encryption_disabler-1.zip)
>Wipe Cache and Dalvik
>Reboot to System
Notes:
Boot image must be first before flashing the others. I tried it after Magisk et.al as with a number of people's directions and several other configurations in addition both in TWRP and with Odin (and the other boot image as well on the thread: t380_boot_pp.img - no luck on XSA for me at least) and it caused a bootloop every time. I don't know why. The smart guys are on the TWRP thread but it's closed (and confusing). I just try things.
To the other OP question here - use the later version of the DM-verity patch - the original one (no-verity-no-encrypt_ashyx) you are referring to is a different size and structure (I have it archived) so it is probably necessary to use the Tab_A_2017_Pie_forced+encryption_disabler-1.zip. It's on pg.65 on zfk110's guide that I linked above (though again, the guide itself did not work for me).
Edit: I know someone could find this method out from the big thread but I know what it is like to feel newby and get confused and want to give up. And the number of different methods and files on that dang thread was a bit maddening honestly and frequently in direct conflict with each other.

Thank you for the guide Winston Churchill, I tried following it for my device Samsung Tab A T380 (build T380DXU3CTH4) but I am stuck at installing Magisk. The patched boot.img is installed successfully but when I go to the system and Magisk does not appear so I have to install it manually with Magisk.apk file. Then when I check the status it says "Installed N/A, Ramdisk Yes, A/B No, SAR No" and root is not active.
I really appreciate any help on this!!

Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.

Moondroid said:
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Click to expand...
Click to collapse
So many conflicting instructions - Why exactly are people flashing this modified boot image and then magisk? Correct me if Im wrong, but isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? I only FINALLY got this working after I ignored the patched boot.img step completely and simply - flash twrp in odin, reboot rocovery, format data, reboot recovery, flash magisk, disable verity whatever, reboot system..

Dick_Stickitinski said:
So many conflicting instructions . . .
. . . isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? . . .
Click to expand...
Click to collapse
Magisk patches boot.img for Root access. Sometimes there are also other reasons for flashing a boot.img. I'm not an Android coder so I can't explain every reason why flashing boot.img might be necessary in this case.
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
At any rate, my method worked for me and yours (however you actually did it) worked for you. I can say for sure that Android itself can be quirky, for example, my recent experiences with a Galaxy S9 on Pie where, after reflashing the exact same build 5-6 times -- because trying to set a security PIN for some screwy reason kept crashing the system (?!!) -- from one reflash to the next I got different app-disabling experiences. For example, a few built-in apps (like google movies etc) showed the option to Uninstall instead of the expected Disable. The same generic reason why an S8 G950U on Pie v8 can be rooted successfully using @jrkruse's Extreme Syndicate method, and other S8 G950s on Pie v8 will brick. Quirky? Weird, I don't know, can't explain, I just go with the flow as it flows and count my blessings when it works.

Moondroid said:
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
Click to expand...
Click to collapse
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.

Dick_Stickitinski said:
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
As of January last year, okay. On older phones/tabs I almost always go with older Magisk versions that were more current with the older device's firmware.
Dick_Stickitinski said:
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Click to expand...
Click to collapse
Just a suggestion, maybe try using an older Magisk. I flashed Magisk v20.4 in TWRP and Magisk Manager v7.5.1 after booting to system. Older Magisk (zip and Manager) can be found on topjohnwu's GitHub.
Note, doing it this way, I always have to reboot one more time to see Magisk fully installed and working.