[TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018

Status
Not open for further replies.
Search This thread

Talich52

Senior Member
  • Dec 24, 2010
    296
    117
    I flashed Magisk many times but could not get root access. I think this file is what I missed. I am happy I found but sadly 'The file was deleted' Can you please upload one. I am very badly in need. Please.
    The file is not deleted and I downloaded it, but You need the kernel from post 567 for T380: https://forum.xda-developers.com/showpost.php?p=80863641&postcount=567
    But the core is the link: http://s000.tinyupload.com/index.php?file_id=04461652675934069019
    P.S. Try it, but I think you need the core T380DXU3CSI5 from post 567 on the link above
     
    Last edited:

    FPThatea

    Senior Member
    Dec 19, 2013
    284
    79
    Roing
    Thank you very much! Everything worked and even Titanium.
    Updated Magisk! at the same time, the update is installed in the recommended direct way, that is, from Magisk itself
    :)

    Can I have the same file for T385. This is what I am looking for. I misquoted above. I understand that this file (unfortunately deleted) is what I exactly need to give me root access.

    ---------- Post added at 10:34 AM ---------- Previous post was at 10:31 AM ----------

    On the t385 model, the core from the T380 will not work. : (
    I will now attach it to the T385 model...

    Thanks...Eagerly waiting.

    ---------- Post added at 10:41 AM ---------- Previous post was at 10:34 AM ----------

    On the t385 model, the core from the T380 will not work. : (
    I will now attach kernel to the T385 model...

    Got the attachment thank you. Do you mean that I should flash this before Magisk and then Magisk(root access) will works fine. I am on Pie.

    I have got a file from Androidfilehost, 't385_defex_patched_boot.img' Should I flash this, is this for Pie? I am in confuse.
     

    Talich52

    Senior Member
  • Dec 24, 2010
    296
    117
    Got the attachment thank you. Do you mean that I should flash this before Magisk and then Magisk(root access) will works fine. I am on Pie.

    I have got a file from Androidfilehost, 't385_defex_patched_boot.img' Should I flash this, is this for Pie? I am in confuse.
    You need to unpack the zip archive and the boot.img file install as img from TWRP to the boot partition, then install Magisk.zip from TWRP.

    P.S. Androidfilehost, 't385_defex_patched_boot.img'
    I don't know anything about such a core...
     
    Last edited:
    • Like
    Reactions: FPThatea

    Nickstar005

    Member
    Aug 15, 2017
    13
    1
    Amazon Fire TV
    You need to unpack the zip archive and the boot.img file install as img from TWRP to the boot partition, then install Magisk.zip from TWRP.
    Sorry... I don't quite understand this part. I have unpacked the zip, tried to place the img file on device.. but twrp doesn't find it.
    What am I doing wrong?
    EDIT: I worked it out thanks. Magisk up and running :)
     
    Last edited:

    zfk110

    Senior Member
  • Jan 11, 2014
    996
    199
    Atlanta
    Would it be possible for someone to write the updated routing method and all files to be flashed, it would be very, much appreciated

    This guide how to upgrade to Pie on T380 and install TWRP, Kernel and RMM patch

    download Pie updates within software updates under settings if that fails then download Pie firmware here

    https://www.sammobile.com/samsung/g...are/SM-T380/XEF/download/T380DXU3CSL2/312343/
    flash it's using Odin

    once its done updating then go back to developer options and enable OEM

    reboot back into download mode

    then flash TWRP using Odin

    Pie's TWRP Here

    https://androidfilehost.com/?fid=11410963190603890373


    go to advance wipe and then do the format

    reboot back in twrp


    then flash Magisk within TWRP Download the latest Magisk release:

    https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

    install OREO/PIE ONLY within TWRP on top of Magisk
    Flash the RMM bypass zip

    https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795


    reboot tablet in download mode then flash this kernel using Odin

    Pie's Kernel for Magisk to work flash this using Odin

    https://androidfilehost.com/?fid=4349826312261626422


    once done it will reboot the tablet

    1st update the Pie, enable OEM, flash TWRP, Format, reboot back into TWRP, flash Magisk, RMM, reboot into download mode flash kernel.

    I tested on my tablet and its working fine. Thanks to @ashyx, @FPThatea
     

    Eclipserazer

    Senior Member
    Sep 17, 2012
    65
    11
    Newcastle
    Tried following your guide to the letter @zfk110 i appreciate the help

    But unfortunately something isnt working properly for me, and after following the guide i get into a Boot Loop. Any idea what i could be missing or doing wrong from your 'guide'?

    and reading through this entire thread is so confusing, because theres patch this patch that, use this one not that one and then you have some people talking about 385 and others about 380 but they dont always specify so how are we to know.
     
    Last edited:

    zfk110

    Senior Member
  • Jan 11, 2014
    996
    199
    Atlanta
    Tried following your guide to the letter @zfk110 I appreciate the help

    But unfortunately something isn't working properly for me, and after following the guide I get into a Boot Loop. Any idea what I could be missing or doing wrong from your 'guide'?

    And reading through this entire thread is so confusing, because there's patch this patch that, use this one not that one and then you have some people talking about 385 and others about 380, but they don't always specify so how are we to know.

    I know there are so many patches this and that, that's why I have that guide just for T380 which I followed wrote word by word and step by step to get my tablet going, also you didn't give any info which tablet you are working on, and did you upgraded to pie or not?
     

    CaptainChris2018

    Senior Member
    Aug 29, 2018
    58
    6
    Puyallup, WA
    Is the reason why magisk is not installing is that I don't have the t380_pp_boot image being installed in Odin? I got TWRP and RMM Bypass working. Also btw, I believe my Knox counter is two by 2x2, so I got TWRP installed twice. The first time, I forgot to install the RMM Bypass. And I reinstalled One UI, I waited seven days. Made sure that OEM Unlock is on. Then reinstalled TWRP, and installed RMM Bypass. It's been a couple weeks. My device is not going locked so I'm good.
     

    Attachments

    • Screenshot_20200314-091504.png
      Screenshot_20200314-091504.png
      43.8 KB · Views: 92

    zfk110

    Senior Member
  • Jan 11, 2014
    996
    199
    Atlanta
    Is the reason why magisk is not installing is that I don't have the t380_pp_boot image being installed in Odin? I got TWRP and RMM Bypass working. Also btw, I believe my Knox counter is two by 2x2, so I got TWRP installed twice. The first time, I forgot to install the RMM Bypass. And I reinstalled One UI, I waited seven days. Made sure that OEM Unlock is on. Then reinstalled TWRP, and installed RMM Bypass. It's been a couple weeks. My device is not going locked so I'm good.

    Yes if you are on pie then you have to flash that kernel using odin, as long you are using T380
     

    Eclipserazer

    Senior Member
    Sep 17, 2012
    65
    11
    Newcastle
    I know there are so many patches this and that, that's why I have that guide just for T380 which I followed wrote word by word and step by step to get my tablet going, also you didn't give any info which tablet you are working on, and did you upgraded to pie or not?

    I'm using T380, updated to pie.

    I've tried finding and using different patches and encryption patches etc. throughout this thread and your post, most of the time after I flash/install everything im supposed to, I either get into a recovery bootloop but it never actually enters recovery, and others it attempts to start and gets stuck on the "Samsung" screen.
     

    zfk110

    Senior Member
  • Jan 11, 2014
    996
    199
    Atlanta
    I'm using T380, updated to pie.

    I've tried finding and using different patches and encryption patches etc. throughout this thread and your post, most of the time after I flash/install everything IM supposed to, I either get into a recovery boot loop but it never actually enters recovery, and others it attempts to start and gets stuck on the "Samsung" screen.

    At this point I will freshly install Pie stock firmware using odin first then enable oem then go from there.

    1st update the Pie using odin, enable OEM, flash TWRP using odin, Format, reboot back into TWRP, flash Magisk using TWRP, RMM using TWRP, reboot into download mode(use twrp to boot into download mode) flash kernel using odin.

    You don't have to download all those patches and files, just use those which I have listed on that guide and you should be good to go since I tested personally, so many patches, files from here and there will make it worst.
     

    CaptainChris2018

    Senior Member
    Aug 29, 2018
    58
    6
    Puyallup, WA
    Yes if you are on pie then you have to flash that kernel using odin, as long you are using T380
    YES, I have the T380. Once I next get on my computer, I will real quickly back up the Rom via Google One (I have a membership), and Install Magisak, then go to Odin and flash t380_pp_boot. What slot do I flash the file too? Should I reinstall RMM Bypass, or am I Good? Also, after root, is there a way to turn off the Read/Write lock for TWRP? Also, after I install Magisak, do I need to install Magisak Manger Manually. I know before, when I tried to install Magisak, the Magisak Manger app did not install automatically. Will it this time?
     

    Eclipserazer

    Senior Member
    Sep 17, 2012
    65
    11
    Newcastle
    At this point I will freshly install Pie stock firmware using odin first then enable oem then go from there.

    1st update the Pie using odin, enable OEM, flash TWRP using odin, Format, reboot back into TWRP, flash Magisk using TWRP, RMM using TWRP, reboot into download mode(use twrp to boot into download mode) flash kernel using odin.

    You don't have to download all those patches and files, just use those which I have listed on that guide and you should be good to go since I tested personally, so many patches, files from here and there will make it worst.

    Following this i get constant Reboots every 10 seconds of the "Samsung Galaxy Tab A powered by Android" with the yellow writing "Set Warrenty Bit : Kernel"
     

    CaptainChris2018

    Senior Member
    Aug 29, 2018
    58
    6
    Puyallup, WA
    I have a t380 running android 8.1. Can i simply follow the instructions in the first post of this thread? Or are there other additional steps outlined in some in between posts? Sorry, not sure if the first post has been updated or not
    I had isscues with my t380 when installing Magisak on my T380, IT was with TWRP, but i am running Pie and Magisak Manger is working fine! Update to pie than follow the instructions a few posts above. You will get One UI 1.0 with it since it's a offcail update. You will need a Windows PC with Odin on it. You can something like Jodin3 if you are a user of macOS or Linux. One UI is worth it because you get stuff like dark mode, Good Lock (If you download nice lock and you sideload the modules), better one hand use, Android Pie, and more. It does not have gestures bescuse the device has hardware buttons, but if you don't like the Samsung Look. You can use apps like power shade, Nova launcher, and The Google apps like GClock and GPhotos, I don't think the device works with GCam, but you can use open camera. The cameras on the device are basic, and it would be silly to take pictures with a tablet, so I don't think you would need a camera app. But if you want the the Samsung stuff in Nova launcher, you can use Nova launcher prime to hide the Samsung apps. I don't mind the Samsung stuff myself.

    ---------- Post added 27th March 2020 at 12:04 AM ---------- Previous post was 26th March 2020 at 11:50 PM ----------

    Following this i get constant Reboots every 10 seconds of the "Samsung Galaxy Tab A powered by Android" with the yellow writing "Set Warrenty Bit : Kernel"
    Set Warranty Bit indicates if your going to the System (Kernel), or you are going to TWRP (Recovery). That's normal when the bootloader is unlocked. But to fix the bootloop, download One UI 1.0 for (T380/T385, Only do the one with your model number) from Sammobile. When I downloaded mine, it said Galaxy Tab A 2018 (T380) even though the T380 is the 2017. Then import the Rom into Odin. It will be in mupilte files. I had to import the files on my USB hard drive bescuse it wouldn't on my computer's internal hard drive. Then when your done. It will reboot the tablet and it go in the setup screen. Do know if your model number is not T380 or T385, you have clicked on the wrong therad. Also, you may have used the wrong filed (Example T380 files on T385.)
     
    Status
    Not open for further replies.

    Top Liked Posts

    • There are no posts matching your filters.
    • 16
      Unofficial release -TWRP recovery for the Galaxy Tab A - T380/T385, Qualcomm MSM8917

      teamwin-recovery-project-twrp-logo.jpg



      TWRP 3.2.1-0 Released

      Dec 9, 2017

      TWRP 3.2.1-0 is out now for most currently supported devices.

      What's new in 3.2.1-0:

      * minui fixes (cryptomilk)
      * Better android-8.0 compatibility in ROM trees (Dees_Troy)
      * Fix missing library in android-8.0 (nkk71)
      * Fix inconsistent SDCard naming (DevUt)
      * Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot


      Update 05/01/2019
      TWRP 3.2.3-1 OO build released.
      Current status: Beta



      Update 02/02/2017
      TWRP 3.2.1-1 NN build released.
      Current status: Stable


      Features:

      MTP working
      ADB working
      SEANDROID warning fix
      TWRP and Kernel built from latest source
      Raw SYSTEM image backup
      NTFS support
      Twrp app support




      You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.


      Instructions:


      Flash with odin in the AP slot.
      Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
      Uncheck Auto reboot.
      Load the respective file below into the AP slot and hit start.
      After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN
      As soon as the screen goes blank change to POWER + HOME + VOL UP
      You should now see TWRP recovery.
      FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY


      Do NOT boot the OS, move on to the root instructions below.

      NOTE: ON ANDROID 5.1.1+ DEVICES IT IS NECESSARY TO GO TO:
      Settings -> Developer Options -> OEM unlocking
      AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.


      DOWNLOAD:

      Oreo/Pie:
      TWRP_3.2.3-1_sm-t380_4119

      TWRP_3.2.3-1_sm-t385_5119

      Nougat:
      TWRP_3.2.1-1_sm-t380_15118


      To Root:
      Download the latest Magisk release:
      https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

      To disable forced encryption and mount internal storage (/DATA):
      1. Boot to Twrp
      2. Format the Data partition (NOT WIPE) using the FORMAT DATA button under Wipe options.
      (Note: This will wipe the internal storage)
      3. Check /DATA is mountable.
      4. Install Magisk

      OREO/PIE ONLY:
      5. Flash the RMM bypass zip
      https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795

      6. Reboot




      Kernel source T380DXU2BRK3: : https://opensource.samsung.com/uploadSearch?searchValue=sm-t380

      TWRP recovery source: https://github.com/omnirom/android_bootable_recovery


      PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST


      DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU

      5
      @ashyx

      Kernel source for T380DXU2BRI6 has been released :)
      5
      @ashyx

      Kernel source for T380DXU2BRI6 has been released :)
      Finally, will be on it soon as I get chance.
      4
      That is great. I am new to all of this. Any sort of estimated timeline as to how long it takes to update TWRP once this is done. Got the tab for christmas and keen to get this thing properly rooted so I can strip all the stuff I do not need and run multiple versions of my game app.

      Not trying to say rush to any of the awesome dev team, just trying to get an idea.

      In the mean time, hap[y new year!
      Probably when new-year is out of the way.
      3
      ok, i feel like i am being ignored here, let me iterate this in another way..

      some of us are visual learners, and no matter how much we read it makes no sense because we don't understand the basis or have anything to compare this too..

      BUT..

      if you made a video on how to install this we would understand in one shot.

      can someone make a youtube video on this please?

      thank you.

      if you dislike youtube (and I understand and agree fully) I wiill even give you webspace to store it on, but i must warn you i move from host to host every three years and next year i move again, but it give us somewhere to start.

      I am working (or trying too anyways) with build # T380DXU1ARB3

      and btw, multiple post about rooting the same device and disagreeing abotu how it is done DO NOT help, nor does it help when someone who was helped by another makes one of those posts rather than the one who provided the solution.

      it has caused me major problems on my end learning to do this actually, and I am sure others feel the same, besides, it is a BS practice.

      so ashyx you have time to make a 15 minute video or something on installing this?
      if we can get you to do that, and the guy behind magisk to do the same we could make this alot easier.

      and also noting which builds it is for and which it fails on would be good too, look ay the posts by mingkee and shahmir_k, good example.

      Hey mate you'll have no issue flashing TWRP to your device just use the download link in OP to download the recovery as your REV001 so your device is compatible as your running the 7.1 nougat SDK, make sure OEM unlock is ON

      Download a copy of your stock firmware for your T380 from sammobile.com you'll need it, any country is flashable but MAKE SURE that the firmware numbers are ☆T380ABC "U1" ABC1 and not T380ABC "U2" ABC1 for example as the new REV002 is 8.1 OREO you dont want that,

      Once you have the recovery downloaded and also the stock firmware, make sure you have ODIN3 3.13.1 also as it supports oreo compression,

      Now first load the TWRP.img you downloaded from OP and place it into the AP tab in odin3 3.13.1 make sure it is the AP tab, now select options, Uncheck auto reboot, now press start, wait for it to say pass In green,

      Now you have to reboot the device but as soon as the screen goes black you must enter recovery without letting the system boot, on the T380 I have i use these buttons reboot the device,

      Hold all at the same time
      Home button,
      Volume down button
      Power button,

      Keep holding until the screen goes black,
      As soon as it does you have to be really quick and hold

      Home button
      Volume up button
      Power button

      You should now be in TWRP now just follow the steps as provided by the OP and you will be fine the hard part is now over,

      if it didnt boot TWRP and you get a triangle screen flash back the stock firmware you downloaded and start these steps again from the start, to flash stock there will be 4 files, BL AP CSC & HOME_CSC, place the BL file into the BL tab, place the AP file into the AP tab (this will take a while to load this one) and last insert the the CSC into the CSC tab, flash and your on stock again, now start from the start,

      ---------- Post added at 05:29 AM ---------- Previous post was at 04:57 AM ----------

      Never known a bootloader with the same revision to be refused. Maybe it's the region variant.
      In any case it doesn't need to be flashed, you already have a rev2 bootloader.


      Hey mate I got it all fixed I managed to get everything back to 1 and not -2 like it was, apart from (R2) this was 2 when I received it but it's not -2 like it was,

      Qualcomm secure boot and also warrantt void is not showing as 0×fffffffe thank #€£@ know what I'm doing just potentially averted a $200 loss lol, ah the Joy's of phone technician,

      What I found wouldnt flash from combination rom when tried after downloading this morning it wouldnt flash the aboot.mbn, sbl.mbn, adspo.mbn,

      what I did is disassemble the combination rom,

      Took the following and converted to .tar

      Persist.img
      System.img
      Userdata.img
      Recovery.img
      Sec.dat
      Msadp.img
      Keymaster.img
      cmnlib.img
      NON-HLOS.img
      Rpm.img
      tz.img

      Then finally very last the cache.img,

      Flash this last you will reboot get the spinning circle and it will reboot and everything will be back to normal for anyone else whom encounters this error, there is a fix to go back to 1 from -2 and have an operational system again :) enjoy guys I'll be waiting for TWRP oreo patiently and can tell my customer I didnt FUBAR they're tablet after all :)
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone