[TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 - Samsung Galaxy Tab A series ROMs, Kernels, Recover

Unofficial release -TWRP recovery for the Galaxy Tab A - T380/T385, Qualcomm MSM8917
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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

Here is a question
Should I do it in TWRP?
https://forum.xda-developers.com/showpost.php?p=75542737&postcount=35

mingkee said:
Here is a question
Should I do it in TWRP?
https://forum.xda-developers.com/showpost.php?p=75542737&postcount=35
Click to expand...
Click to collapse
Please do not quote the entire OP.
Please remove the quote.
I take it you are referring to the modifications?
It doesn't matter how you do it as long as you do it before reboot.

ashyx said:
Please do not quote the entire OP.
Please remove the quote.
I take it you are referring to the modifications?
It doesn't matter how you do it as long as you do it before reboot.
Click to expand...
Click to collapse
Sorry for that.
It's browser problem which doesn't let me post without quoting
Firefox for Android.

Thanks for your recovery.
Mine finally rooted.

help me
help please, I can not install the twrp, odin tells me that everything is ok, and when I run the recovery it appears no command, my tablet is sm t380

aquamoon1 said:
help please, I can not install the twrp, odin tells me that everything is ok, and when I run the recovery it appears no command, my tablet is sm t380
Click to expand...
Click to collapse
Did you see any error on the unit?
If it is a new machine, you have to wait 7 days for OEM Unlock in Developers Option shows up.

mingkee said:
Did you see any error on the unit?
If it is a new machine, you have to wait 7 days for OEM Unlock in Developers Option shows up.
Click to expand...
Click to collapse
No error and have 1 month with OEM unlocked

aquamoon1 said:
help please, I can not install the twrp, odin tells me that everything is ok, and when I run the recovery it appears no command, my tablet is sm t380
Click to expand...
Click to collapse
You didn't follow the instructions in the OP. You have booted to stock recovery.

There's a minor mistake to enter TWRP.
After flashing TWRP in Download mode, press and hold Volume Down and Power buttons, and as soon as the screen goes blank, press Volume Up + Power + Home buttons until you see "entering recovery"

TWRP intstalled OK and Data partition formatted as instructed. SuperSU and boot image patch zips installed, rebooted and after two auto reboots the tablet powers down and is unresponsive. Can still manually boot to TWRP. ?? Any hints??

Thanks for the guide, seems to have worked fine. Have TWRP, Root, Magisk on my Tab A T385 after following all the guides on this forum.

Impossible. ALL THE GUIDES? There are so many errors and omissions in THIS guide, it's impossible that you could have successfully completed root by following it. I, too, researched other posts on other guides. Perhaps I missed something. It would be good to clean up THIS guide so others don't have to do it.

NavyDave49 said:
Impossible. ALL THE GUIDES? There are so many errors and omissions in THIS guide, it's impossible that you could have successfully completed root by following it. I, too, researched other posts on other guides. Perhaps I missed something. It would be good to clean up THIS guide so others don't have to do it.
Click to expand...
Click to collapse
Maybe you shouldn't be attempting to root your device if you are incapable of following instructions that every one else seems to manage with just fine.
I suggest you try www.spoonfeeders.com.

Didn't work for me. Tab SM-T380. Using Odin3 v3.11. OEM unlock is checked and running Build RB3. USB debugging is check too if that matters in download mode.
Do I need to flash back to stock firmware first? I don't think I read that I need to flash stock first, just that you said I should download it in case of a soft brick. Or do you think it might be my Odin ver. Honestly I don't know, every time I've done this on previous devises it worked, so not sure where to go from here.
My Tab says "Only official released binaries are allowed to be flashed"
Odin says...
Code:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Chrisrobbins30 said:
Didn't work for me. Tab SM-T380. Using Odin3 v3.11. OEM unlock is checked and running Build RB3. USB debugging is check too if that matters in download mode.
Do I need to flash back to stock firmware first? I don't think I read that I need to flash stock first, just that you said I should download it in case of a soft brick. Or do you think it might be my Odin ver. Honestly I don't know, every time I've done this on previous devises it worked, so not sure where to go from here.
My Tab says "Only official released binaries are allowed to be flashed"
Odin says...
Click to expand...
Click to collapse
Check for RMM state in Odin mode.

ashyx said:
Check for RMM state in Odin mode.
Click to expand...
Click to collapse
As I was trying to find out what you where talking about. I discovered you where referring to a line of txt in download mode. So I went back to download mode to check. I didn't see the RMM line though. But I thought maybe I have to try to flash again to get that line. But oddly this time it passed. Crazy right? thx for the help tho...

It's amazing that even Samsung's tablets are getting TWRP, even if they might not be as glorious as their phones.
Speaking of which, will TWRP 3.2.0 ever be able to support the older (and weaker) model of this device called an SM-T350? I'm out to build Android Oreo for those old tablets from three years ago and 3.1.1 does not seem to know what an Oreo is.
Sent from my OnePlus 3T using XDA Labs

I'm in TWRP but when I try to boot to system I get suck in a boot loop. I think maybe I f**ked up. I forgot to put SU on my SD card and I wanted to do a backup before I booted to system. It wouldn't let me. So I tried wiping and it wouldn't let me do that. So I skipped a step and used the format option. That worked and then I made a backup, but it said something about reloading the data. Then I tried rebooting to system and got the boot loop. I can still get in TWRP but can't get boot system. Do I need to start over? Reflash stock and stuff or am I missing something?
Edit: False alarm again, damn what the hell eveything wants to take 2 tries first. I'm good to go now.

Newbs, if you're having trouble flashing TWRP to your Smasung Galaxy A T380 (2017) and you're having no luck following several different ROOT or TWRP tutorials on here, try a different button combination. I tried over 15 times with existing tutorial combinations (including this one) and they were not right for my device - which is a week old.
Note: after unlocking developer options in Settings, you will have to wait 7 days for OEM unlock to show up in your settings... so turn that and USB Debugging on. But if you boot to download mode in the meantime you may be able to do it anyway on the T380 (thanks to ashyx for pointing this out) - OEM lock was showing as "OFF" the day I got it - I just couldn't get the flash button combos right! If not, then wait the 7 days for the option to show up.
I used ODIN 3.12.5. Uncheck auto-boot (you will find it in the "Options" tab of Odin)
Load up the TWRP file provided in this tutorial in the AP slot.
To put your device into download mode, turn it of, then hold: Power + Volume Down + Home (not what is said in this tutorial)
Flash, then once you get your success message/"PASS" message - here's the important bit that's different from this tutorial and others I've seen. To get out of DL mode, hold Power + Volume Down + HOME (HOME is the additional step that has been missing)
As soon as the screen goes blank, switch to Power + Volume Up + HOME. You should boot straight to TWRP then... and follow the rest of ashyx tutorial for root & installing the encrypt patch.
I don't know why this was different from this tutorial, or others I've seen.... but it was. And I was killing myself using the other button combos with no success (either straight back to ordinary boot following this tutorial steps, or hitting error following suggested Power + Volume Down to ext DL, then Power + Volume Up + Home to boot to recovery in a root tutorial or two).
TL;DR version if hitting problems - use the HOME BUTTON AS WELL on BOTH the suggested steps in the OP's tutorial after flashing.

Related

[Recovery][T580] Official TWRP for Galaxy Tab A 10.1 WiFi 2016 (gtaxlwifi)

Team Win Recovery Project 3.0.2-0
This is for the Exynos WiFi SM-T580 model only!
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your retailer to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxytaba101wifi2016.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR OBTAINING ROOT
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for gtaxlwifi.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Initial build on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/jcadduono/android_device_samsung_gtaxlwifi (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_exynos7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
Thanks for this work!
I managed to flash and boot into TWRP recovery but i have partition problem :
"failed to mount data"
"internal storage is listed as 0MB"
http://imgur.com/a/Ut3S7
http://imgur.com/qDCs9iS
EDIT2: As mentionned by @jcadduono , there is a simpler method than mine :
BTW you can just flash TWRP and use the [Format Data] button on wipe page which will do the same thing, making data available (but completely wiped, including internal storage!!!)
Click to expand...
Click to collapse
EDIT3: use@ashyx' patch to remove encryption:
BOOT IMAGE PATCHER
Boot image patcher to remove DM-verity and Forced encryption.
Flash the zip below with TWRP.
This was built by jcadduono not me, so props to him, I just modified it to work for this device and to remove the SEANDROID ENFORCING message.
NOTE: IF YOU INTEND TO ROOT THEN FLASH THIS AFTER SUPERSU.
no-verity-no-encrypt_ashyx
.
Click to expand...
Click to collapse
bws78 said:
Thanks for this work!
I managed to flash and boot into TWRP recovery but i have partition problem :
"failed to mount data"
"internal storage is listed as 0MB"
http://imgur.com/a/Ut3S7
http://imgur.com/qDCs9iS
EDIT: I found out a solution to solve my problem, at least to root my device.
-Flash back stock recovery using odin
-Boot in stock recovery and Wipe data/factory reset
-Boot DIRECTLY in download mode (DO NOT NORMAL BOOT)
-Flash TWRP recovery using odin
-Boot DIRECTLY in TWRP recovery (DO NOT NORMAL BOOT)
(/data partition should be visible)
-For root flash Supersu.zip (or what you want)
-reboot system (device is now rooted)
Each time my device boot on android I lose /data partition in TWRP, maybe due to partition encryption
Click to expand...
Click to collapse
yes Exynos 7870 devices currently have a bug where Samsung is using their own crypto daemon and telling vold to force encryption regardless of fstab flags, I reported it to Samsung security team but not sure if they are looking into it. So far haven't found a way to prevent encryption from happening. (I removed all references to encryption in ramdisk & system.prop and it still encrypts, wow!)
BTW you can just flash TWRP and use the [Format Data] button on wipe page which will do the same thing, making data available (but completely wiped, including internal storage!!!)
Could it possibly work for SM-T585? Would it be possible to use your repos and compile a build for my tab?
Alexander_the_B0ss said:
Could it possibly work for SM-T585? Would it be possible to use your repos and compile a build for my tab?
Click to expand...
Click to collapse
I've been hoping someone would show up with the T585 in the #twrp channel on freenode so we could work on it, it would only take minimal changes (basically just take the dtb from stock T585 rom I guess, kernels should be exactly the same)
You could try flashing T580 TWRP and let me know if it works though, then I can just combine them if so.
jcadduono said:
I've been hoping someone would show up with the T585 in the #twrp channel on freenode so we could work on it, it would only take minimal changes (basically just take the dtb from stock T585 rom I guess, kernels should be exactly the same)
You could try flashing T580 TWRP and let me know if it works though, then I can just combine them if so.
Click to expand...
Click to collapse
I am too tired right now and not in the mood. Very sick, having some tooth issues and maybe we can sort this out somehow. But not today, I am really sorry. May be tomorrow. Add 13 hours to your time and you'll know if I am on-line or not. It's about 7 am here, been up all night and need some sleep. Just PM me whenever you can and I'll hop on Freenode.
I'm having problems booting from Download mode (after flashing recovery via Odin) directly into Restore mode... Is there a trick I'm missing? I can't seem to find a way to get the battery out so right now all I can do is reboot in Download_mode>cancel>volume up and I'm in TWRP but same partition/data issue as above. Thanks for any help
8BitAirwaves said:
I'm having problems booting from Download mode (after flashing recovery via Odin) directly into Restore mode... Is there a trick I'm missing? I can't seem to find a way to get the battery out so right now all I can do is reboot in Download_mode>cancel>volume up and I'm in TWRP but same partition/data issue as above. Thanks for any help
Click to expand...
Click to collapse
In download mode press [power + vol down + home], when the screen turn off press [power + vol up+ home].
But you should try format data in twrp (on wipe page) as mentioned by jcadduono. It's a easier way to remove partition encryption (wipe everything on /data)
bws78 said:
But you should try format data in twrp (on wipe page) as mentioned by jcadduono. It's a easier way to remove partition encryption (wipe everything on /data)
Click to expand...
Click to collapse
First off thank you so much for the fast reply, I should have thought of that- well the button swap I never would have come up with the quoted I'm rather new/in middle of a dedicated but gradual move from iOS Dev to Android! Loving it and this community, thanks again
root sm-t580
@bws78
Hello,
Sorry for my bad english, first!
To Boot DIRECTLY in download mode from stock recovery correctly once i wipe data/factory reset, do i have to power off and then use buttons power + (volume -) + home?Is that correct?
Same thing when i finish to Flash TWRP recovery using odin to boot DIRECTLY in TWRP recovery, buttons : power + (volume +) + home ?
Thanks fo your response
yetibiker said:
@bws78
Hello,
Sorry for my bad english, first!
To Boot DIRECTLY in download mode from stock recovery correctly once i wipe data/factory reset, do i have to power off and then use buttons power + (volume -) + home?Is that correct?
Same thing when i finish to Flash TWRP recovery using odin to boot DIRECTLY in TWRP recovery, buttons : power + (volume +) + home ?
Thanks fo your response
Click to expand...
Click to collapse
To boot in download mode from stock recovery, go to power off or reboot system and when the screen turn off press
[power + vol down + home].
To boot in recovery mode from download mode, long press [power + vol down + home], when the screen turn off press [power + vol up+ home].
But this method it's tedious. Try @jcadduono method to wipe /data encryption from TWRP:
BTW you can just flash TWRP and use the [Format Data] button on wipe page which will do the same thing, making data available (but completely wiped, including internal storage!!!)
Click to expand...
Click to collapse
recovery t580
Hello,
I flash the TWRP in download mode whithout doing data/factory reset before in stock recovery but when i try to reboot in TWRP, because odin say success, i'm finally in stock recovery!
How many times i've to wait the bar stop in download mode? Because the bar wasn't totally full when i reboot, miss just a very little bit, but after few(too long) minutes i try to reboot to go on TWRP but not here, just stock recovery. I missed up something? I can't remove battery, is that for?
Thanks for your time
So this replaces the regular recovery image? If so the first thing I'd want to do is make a backup I guess right?
I know this looks to be early days, but anyone looking into cm on this device(just got it today) also any luck with xposed?
---------- Post added at 04:22 PM ---------- Previous post was at 04:19 PM ----------
UntouchedWagons said:
So this replaces the regular recovery image? If so the first thing I'd want to do is make a backup I guess right?
Click to expand...
Click to collapse
Samsung is really good about having odin flashable packages available so if there is issues you can always restore via download mode (never heard of a permanent soft brick in years for a Samsung device)
jaykoerner said:
Samsung is really good about having odin flashable packages available so if there is issues you can always restore via download mode (never heard of a permanent soft brick in years for a Samsung device)
Click to expand...
Click to collapse
Do you know where I'd get one of these packages just in case?
I've used the first site not the second, sammobile is trustworthy. The other is for redundancy.
http://www.sammobile.com/firmwares/database/SM-T580/
http://samsung-updates.com/device/?id=SM-T580
Also recovery and stock firmware is on xda, somewhere it's just hard to find since this device doesn't have a forum.
jaykoerner said:
I've used the first site not the second, sammobile is trustworthy. The other is for redundancy.
http://www.sammobile.com/firmwares/database/SM-T580/
http://samsung-updates.com/device/?id=SM-T580
Also recovery and stock firmware is on xda, somewhere it's just hard to find since this device doesn't have a forum.
Click to expand...
Click to collapse
What's with all the countries? What would I choose for North America?
UntouchedWagons said:
What's with all the countries? What would I choose for North America?
Click to expand...
Click to collapse
Yes, but the only real reason is so the device has the correct language settings. They should all be compatible but if you choose your region you don't have to worry.
Step 8 says to download the tar file in the AP slot, but the download page for TWRP is an img file, do I just tar the image using 7zip?
UntouchedWagons said:
Step 8 says to download the tar file in the AP slot, but the download page for TWRP is an img file, do I just tar the image using 7zip?
Click to expand...
Click to collapse
You'll find the link for the tar file in the OP (Temporary Download).

[RECOVERY][ROOT][TWRP 3.0.2-1] Samsung Galaxy Tab A6 LTE SM-T285

Attached in this thread is TWRP repackaged for the SM-T285 built by @ashyx with the UI lag fixed and a new custom kernel that I built.
TWRP-3.1.1-0 for the SM-T285 is now available, you should hop on to this thread for more information.
Update 01/17/2017
==============
TWRP with F2FS support here. Use only if you plan to use the F2FS enabled CM13 builds for the SM-T285.
Update 11/24/2016
==============
* MTP should now be fixed
Installation Instructions
This installation instruction is only for the LTE enabled version of the Samsug galaxy tab A 7" 2016 (SM-T285). If you have a wifi-only version (SM-T280) go to this thread instead.
Disclaimer: I am not responsible for bricked devices and provide no warranty, make sure you made the proper backups and contingencies before you do this procedure. Make sure you have a stock firmware available as a contingency plan
Before going through this make sure your tablet is OEM Unlocked. Make sure you have developer settings enable and there should be a setting there that says OEM unlock. That should be enabled, otherwise your SM-T285 will not accept firmware changes. Also make sure your tablet has sufficient charge and is not about to die.
1. Put your tablet in download mode (Turn off. holding POWER + HOME + VOL DOWN until download mode appears. There will be a warning that about custom firmware blah- blah-blah just hit volume up to proceed). Connect your tablet to your computer using the provided micro usb cable.
2. Flash with ODIN 3.10.7 in the AP slot. Uncheck Auto reboot. (If you are on Linux you can use Heimdall
3. Load the respective attached file (TWRP_3.0.2-1_SM-T285_20161124.zip) in this thread below into the AP slot and hit start.
4. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Root and SuperSU
==============
1. Download the latest available SuperSu Zip from chainfire. Install Zip using TWRP. Reboot phone.
2.Your phone might reboot a couple of times, however at the end of the process you should be rooted.
enjoy!
jedld said:
Attached in this thread is TWRP repackaged for the SM-T285 built by @ashyx with the UI lag fixed and a new custom kernel that I built.
For the installation instructions, should be the same with the SM-T280 in this thread http://forum.xda-developers.com/galaxy-tab-a/development/recovery-samsung-galaxy-tab-a6-sm-t280-t3475381
enjoy!
Click to expand...
Click to collapse
Thanks! The lag is completely gone, making the recovery a joy to use. However, MTP is still not working.
Thanks
I rooted my device (Glaxy Tab a 7" T285)by your method and files.
Next day i saw my device was off ,i pressed power but it could not boot and show this:
Code:
custom binary blocked by frp lock
Afterward i tried to go recovery by pressing Home+Power+volum up but it could not go recovery and show me:
Code:
custom binary blocked by frp lock
Recovery is not Seandroid Enforcing
Therefor my device had been useless.
so I go to download by odin and install a stock ROM.
I search and saw 2 advises:
1)this problem occur if androd version is 5.1.1
2) this problem occur if in developer menu OEM Unlock Option is disabled.
IS THIS ADVISES TRUE? OR THAT PROBLEM HAS OTHER REASON?
I went dev menu and enabled OEM and afterward i did ROOT again.
I have some questions:
1) Is it important Factory reset after install new ROM ? Also after ROOT? Also after unroot?
2) How do i unroot my device?
I have some questions:
1) Is it important Factory reset after install new ROM ? Also after ROOT? Also after unroot?
Click to expand...
Click to collapse
If you install a new rom, then yes you have to factory reset. If it is just to install TWRP I don't think you need to do that.
2) How do i unroot my device?
Click to expand...
Click to collapse
Easiest way is to just flash stock again
Many thanks @jedld, root works perfectly in Galaxy Tab A6 (2016) SM-T285.
Flash twrp.tar by odin, then flash @Chainfire SuperSU SR 2.78 and get rooted !
acornkenya said:
Thanks! The lag is completely gone, making the recovery a joy to use. However, MTP is still not working.
Click to expand...
Click to collapse
MTP should now be fixed with the latest release.
jedld said:
MTP should now be fixed with the latest release.
Click to expand...
Click to collapse
MTP is now working like a charm; thank you
Adam Hui said:
Many thanks @jedld, root works perfectly in Galaxy Tab A6 (2016) SM-T285.
Flash twrp.tar by odin, then flash @Chainfire SuperSU SR 2.78 and get rooted !
Click to expand...
Click to collapse
Pls help subinary files not installed superSU v2.78.SR1
siukbah112 said:
Pls help subinary files not installed superSU v2.78.SR1
Click to expand...
Click to collapse
Just download & flash latest SR5 superSU.zip
@jedld
So just flash the TWRP file with Odin or follow the long steps provided in that thread about the T280?
The links seem to get outdated very quickly so a step by step guide would be really appreciated to avoid mistakes :good:
From beginning to end until I have SuperU :good:
Thanks in advance if I don't reply m8
Shook1 said:
@jedld
So just flash the TWRP file with Odin or follow the long steps provided in that thread about the T280?
The links seem to get outdated very quickly so a step by step guide would be really appreciated to avoid mistakes :good:
From beginning to end until I have SuperU :good:
Thanks in advance if I don't reply m8
Click to expand...
Click to collapse
ok, I've updated the instructions.
finally, I've managed to flash the recovery img to my Stock 285. I have compiled the heimdall from source (github), using Debian 8 Jessie. I also managed to download the stock firmware from sammobile using wget + cookies trick so it can be resumed without requiring a premium account. Thanks for the TWRP
BTW, after installing the SuperSU the SELinux is gone? do I need to flash your custom kernel too?
What do you mean? Was SELinux set to permissive? From what I know the stock kernel has SELinux configured to always enforce and can't be disabled that easily.
SCREENSHOT SELF DESTRUCT AFTER 24 HRS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before I flashed TWRP nad ROOT (SR5-SuperSU-Chainfire) the SELinux can be seen Set to 'Enforcing' then it is now gone? THe SUperSU asked that 'Samsung KNOX has been detected, try to disable KNox?' I clicked 'Yes'. I have not used yet your kernel img, i am still using the 'stock' kernel, i've only flashed recovery img using heimdall 1.4.1
$ sudo heimdall flash --RECOVERY recovery.img
----
This may not be related but. The screen lock password prompt does not popup the keyboard (samsung or any other). I've also tried 'Pi Locker' the PIN code option and the keyboard still won't appear so there s no way to type the code/pin/password. I am trying to set the screen lock to pattern lock but it is greyed out it security settings because I used device encryption. Is there a adb/shell command to enable Pattern Lock method? Thanks
screen shots:
#1 Stock android lock screen
#2 Pi Locker (F-Droid)
gian20 said:
SCREENSHOT SELF DESTRUCT AFTER 24 HRS
Before I flashed TWRP nad ROOT (SR5-SuperSU-Chainfire) the SELinux can be seen Set to 'Enforcing' then it is now gone? THe SUperSU asked that 'Samsung KNOX has been detected, try to disable KNox?' I clicked 'Yes'. I have not used yet your kernel img, i am still using the 'stock' kernel, i've only flashed recovery img using heimdall 1.4.1
$ sudo heimdall flash --RECOVERY recovery.img
----
This may not be related but. The screen lock password prompt does not popup the keyboard (samsung or any other). I've also tried 'Pi Locker' the PIN code option and the keyboard still won't appear so there s no way to type the code/pin/password. I am trying to set the screen lock to pattern lock but it is greyed out it security settings because I used device encryption. Is there a adb/shell command to enable Pattern Lock method? Thanks
screen shots:
#1 Stock android lock screen
#2 Pi Locker (F-Droid)
Click to expand...
Click to collapse
Interesting, I haven't encountered that on my device, then again I'm not using encryption. In that case it could be related to something SuperSU is doing. Unfortunately I have no clue as to what that is, it does touch the sepolicy files in order to allow for root as far as I know.
jedld said:
Interesting, I haven't encountered that on my device, then again I'm not using encryption. In that case it could be related to something SuperSU is doing. Unfortunately I have no clue as to what that is, it does touch the sepolicy files in order to allow for root as far as I know.
Click to expand...
Click to collapse
I don't know if that issue (missing keyboard) was patched with the new stock firmware update on Dec 13, 2016 or if it may block installation of custom firmwares... I ended up not using a password on the lock screen, I deleted the passowrd.key and modified the android settings database to disable password lock, but seperating the necrpytion password using an app.
Unroot without rebloating?
I've rooted using this method (smooth as anything, by the way) in order to remove the various bits of bloatware. What I'm wondering is, is it possible to unroot, take the recovery back to stock and not end up with the bloatware back on?
Reason I'm asking is, my 6 year old loves playing Pokemon Go (honest!), but any of the custom ROMs I've tried meant I couldn't play the game anymore.
Failing that, is there a workaround?
DJThunderGod said:
I've rooted using this method (smooth as anything, by the way) in order to remove the various bits of bloatware. What I'm wondering is, is it possible to unroot, take the recovery back to stock and not end up with the bloatware back on?
Reason I'm asking is, my 6 year old loves playing Pokemon Go (honest!), but any of the custom ROMs I've tried meant I couldn't play the game anymore.
Failing that, is there a workaround?
Click to expand...
Click to collapse
If you have removed the bloatware it should stay like that unless you reflash the stock rom.
My device software info
Baseband version: T285XXU0APH4
Kernel version: 3.10.65-8968674
[email protected] #2
Wed Dec 28 11:00:16 KST 2016
Build Number:
LMY47V.T285XXU0APL7
I had software update few days back so wondering if the TWRP method to root would still work?
I could not select TWRP_3.0.2-1_SM-T285_20161124.zip file in AP slot so I selected TWRP_3.0.2-1_SM-T285_20161124.tar.md5 I hope this correct.
After seeing PASS on odin I could not go into recovery mode directly.
I did press power + vol down and home button but the device rebooted.
And when I did
adb reboot recovery there is not TWRP but stock recovery.
What am I doing wrong? can I still use TWRP method for with latest samsung software?
Is there a easy method to get into recovery mode after running odin?
thank you.
kannaiah said:
My device software info
Baseband version: T285XXU0APH4
Kernel version: 3.10.65-8968674
[email protected] #2
Wed Dec 28 11:00:16 KST 2016
Build Number:
LMY47V.T285XXU0APL7
I had software update few days back so wondering if the TWRP method to root would still work?
I could not select TWRP_3.0.2-1_SM-T285_20161124.zip file in AP slot so I selected TWRP_3.0.2-1_SM-T285_20161124.tar.md5 I hope this correct.
After seeing PASS on odin I could not go into recovery mode directly.
I did press power + vol down and home button but the device rebooted.
And when I did
adb reboot recovery there is not TWRP but stock recovery.
What am I doing wrong? can I still use TWRP method for with latest samsung software?
Is there a easy method to get into recovery mode after running odin?
thank you.
Click to expand...
Click to collapse
It's possible the stock rom overwrites the recovery since you rebooted straight to stock after flashing. Try to flash again but this time when the device reboots, try to press and hold power + home + vol up immediately to attempt to load TWRP recovery.

[RECOVERY][OFFICIAL] TWRP 3.6.0_9-0 [N5100 N5110 N5120]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Odin
- Odin3 v3.10.5
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Note 8.0
How to flash TWRP with Odin
1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down and Home simultaneously. When the warning screen appears, release all buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP".
3. Disable auto reboot in Odin and press start.
4. You can then boot directly into TWRP by pressing the Power, Home and Volume Up simultaneously. Release all buttons as soon as you see the boot screen ("Samsung Galaxy Note 8.0").
How to flash TWRP within a previous version of TWRP
1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all buttons when the boot screen appears ("Samsung Galaxy Note 8.0").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Bugs
- You tell me!
Credits
TWRP Team and all people who worked / are working on the exynos 4 devices.
Sources
- n5100 repository
- n5110 repository
- n5120 repository
- TWRP repository
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my spare time and every donation keeps me motivated.
donate
XDA: DevDB Information
TWRP 3.6.0_9-X, ROM for the Samsung Galaxy Note 8.0
Contributors
@html6405
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-03-14
Created 2021-02-21
Last Updated 2021-10-12
is the file corrupted? it's only 7KB instead of 7MB
begucu said:
is the file corrupted? it's only 7KB instead of 7MB
Click to expand...
Click to collapse
Hi, which file did you try?
They are all about 7.2MB, if you downloaded it with your device, check if it didn't downloaded the html page instead (I've seen this many times)
html6405 said:
Hi, which file did you try?
They are all about 7.2MB, if you downloaded it with your device, check if it didn't downloaded the html page instead (I've seen this many times)
Click to expand...
Click to collapse
I tried to download
Code:
https://dl.twrp.me/n5100/twrp-3.5.0_9-0-n5100.img
And as you said, I only got the html file
I'm using Google Chrome with Internet Download Manager.
It took a couple times to download the 7MB file
TWRP 3.5.1_9-0 is now ready to download , if you should find any bugs, let me know.​
Does anyone know anyone who wants to sell his GT-N5120? Thanks
TWRP 3.5.2_9-0 builds are up, I've readded some file systems.
Can anyone access an encrypted data partition from TWRP?
I tested TWRP 3.3.1, 3.5.0_9, 3.5.1_9, 3.5.2_9-0 and 3.5.2_9-1 on my n5110, and no version asks me for the password, and the mounting process fails.
I encrypted the device shortly after @html6405 added support for it in his LineageOS 16 ROM. I selected "resize partition" in TWRP for the data partition, then the encryption succeeded in LineageOS. Since then, TWRP fails to access the data partition.
I attach recovery.log. This is from TWRP 3.5.2_9-1.
The most interesting line is probably
Code:
E:Unexpected value for crypto key location
Is my data partition messed up (although Lineage functions correctly), or has TWRP a problem with encryption, which @html6405 might be able to solve?
Mynacol said:
Is my data partition messed up (although Lineage functions correctly), or has TWRP a problem with encryption, which @html6405 might be able to solve?
Click to expand...
Click to collapse
Hi,
the encryption in TWRP was never supported for these devices, but I will take a look at it and try to find a solution.
Update 16.06.2021:
Brought support for GSI flash & reused old HIDDEN partition as vendor.
Brought support for encrypted /data partition.
Can i use this recovery img for my device gt-n5100 with build number KOT49H instead of KONA3G which is the only one available at twrp website?
sparks2012 said:
KOT49H
Click to expand...
Click to collapse
This code is only software related from samsung's side.
You can use the recovery.
html6405 said:
This code is only software related from samsung's side.
You can use the recovery.
Click to expand...
Click to collapse
Thanks
Hi,
After trying to revert my device to stock I lost twrp as well as the system..
Now my device is only showing start screen with samsung logo.
I want to reinstall TWRP so I followed procedure and with the device in download mode, from Linux I do:
Code:
heimdall flash --RECOVERY twrp-3.5.2_9-1-n5110.img
It seems to work (see logs below)
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
but when I restart the device and try to enter TWRP I get nothing but the same screen with Samsung logo.
I retried flashing several times but always same result.
Do you have an idea what could be wrong and how to solve it?
Thanks,
mutonic said:
Hi,
After trying to revert my device to stock I lost twrp as well as the system..
Now my device is only showing start screen with samsung logo.
I want to reinstall TWRP so I followed procedure and with the device in download mode, from Linux I do:
Code:
heimdall flash --RECOVERY twrp-3.5.2_9-1-n5110.img
It seems to work (see logs below)
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
but when I restart the device and try to enter TWRP I get nothing but the same screen with Samsung logo.
I retried flashing several times but always same result.
Do you have an idea what could be wrong and how to solve it?
Thanks,
Click to expand...
Click to collapse
If your device won't enter TWRP or the stock ROM (if you've flashe a full Firmware),
it could be that your eMMC is locked and need to get replaced.
html6405 said:
If your device won't enter TWRP or the stock ROM (if you've flashe a full Firmware),
it could be that your eMMC is locked and need to get replaced.
Click to expand...
Click to collapse
locked eMMC?? never heard of that before... what is it?
My device is in this state since I tried to flash the stock back ...
Could't it be related?
Edit:
Also I was surprised when I flashed the stock rom back to see the customized boot logo (with your nickname + xda developer) still displayed.
So it seems something went wrong or wasn't completely restored as I should see the original Samsung logo..
mutonic said:
locked eMMC?? never heard of that before... what is it?
Click to expand...
Click to collapse
The eMMC firmware lock's the storage if there are no blocks left.
Than it's read only.
mutonic said:
Also I was surprised when I flashed the stock rom back to see the customized boot logo (with your nickname + xda developer) still displayed.
So it seems something went wrong or wasn't completely restored as I should see the original Samsung logo..
Click to expand...
Click to collapse
This would be gone if the eMMC would store the flashed data.
html6405 said:
The eMMC firmware lock's the storage if there are no blocks left.
Than it's read only.
This would be gone if the eMMC would store the flashed data.
Click to expand...
Click to collapse
Very strange.. can it be fixed?
I wonder how something like this can happen.. I don't think I did anything wrong while flashing.
mutonic said:
Very strange.. can it be fixed?
Click to expand...
Click to collapse
Yes, your eMMC need to get replaced.
mutonic said:
I wonder how something like this can happen.. I don't think I did anything wrong while flashing.
Click to expand...
Click to collapse
Also a storage has it's physical end, the blocks are limited.
html6405 said:
Also a storage has it's physical end, the blocks are limited.
Click to expand...
Click to collapse
Thanks for precisions.
So this means it would be wearing issue? which would make sense given age of this device...
html6405 said:
Yes, your eMMC need to get replaced.
Click to expand...
Click to collapse
You mean hardware, how can it be?
Originally I wanted to restore device back to stock to benefit from trade in bonus offer from samsung.
I guess I'd rather getting it traded as it is than trying to repair it...

[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)

Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release was Android 10-based). I have attempted to make this install as painless as possible. Please read the notes below carefully. WARNING: you are responsible for your own actions, so please be careful. If you brick something, that's on you.
Update to latest stock ROM as of 3/24/2022 (T500XXU3BVB3).
Unlock bootloader using steps described in this thread. Make sure that after your device wipes and reboots after the bootloader is unlocked that you go through the setup wizard again and back into Developer Settings and enable OEM Unlocking. I think you need to connect to wifi for this option to appear, so if you don't see it try that.
Boot to download mode, then install VBMeta Disabler via Odin.
Reboot to download mode, then install TWRP via Odin.
Reboot to download mode again, then install LineageOS via Odin.
Boot to TWRP, push "fix_brightness.sh" to the device and run it, then format data.
That should be all that is necessary. If you get stuck in a loop with TWRP where you can't boot to system (seems to happen regularly to me) I included a script in TWRP that should get you out. From the TWRP cli run the command "exit_twrp". It will say "out of space" when finished (instantly). Then reboot to system. If for some reason that still doesn't work and you boot back to TWRP, repeat.
Known Issues:
OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
TWRP touchscreen seems to be unresponsive for several seconds upon first booting into TWRP. Just patiently wait a few seconds and try again.
You'll see errors in TWRP about /keyrefuge, etc. Ignore that. I believe it's related to the inability to decrypt internal storage using FBE.
Installing Gapps (Nik and Flame) doesn't work, but no worry because the ROM includes Gapps
Security: by default this ROM has root access and USB debugging (adb) is enabled unsecured. Anyone can plug into it and have full root access. So disable USB debugging if you don't want that! TWRP is the same way, though data is encrypted. Someone could install malware into your system partition though. In short, this is for hobbyists, not someone with security concerns.
Sources:
Device tree for TWRP from my Github; branch TWRP-11 specifically: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Kernel sources from Samsung: https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#
Files:
LineageOS 19.1 Beta2
TWRP 3.6.1 Beta 5
VB Meta Disabler
Brightness Fix
Updates:
You can update this ROM yourself by installing a new GSI to the system partition.
Download new GSI from here onto Micro SD card: https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
Boot into TWRP
Run command: blockdev --setrw /dev/block/mapper/system
Run command: dd if=/external_sd/<your_downloaded_gsi.img> of=/dev/block/mapper/system bs=1M
Wait for dd command to finish, then reboot into system. Don't forget to use "exit_twrp" command if you keep booting into TWRP.
Thanx! I must flash gsi via Odin over AP?
torekiki said:
Thanx! I must flash gsi via Odin over AP?
Click to expand...
Click to collapse
If by GSI you mean the Lineage .tar file I linked to, then yes. That particular file is more than a GSI, it is a super partition including the GSI, vendor, product, and odm partitions. Flash this via Odin to AP and in the future you can install standalone GSIs of Lineage using TWRP with the instructions at the bottom of the post.
After formatting data, tablet just keeps booting to TWRP. Won't boot to system.
lewmur said:
After formatting data, tablet just keeps booting to TWRP. Won't boot to system.
Click to expand...
Click to collapse
Read the op. I specifically address this.
Hi thanks for all your work. Question , I do step 3 successfully and it boots to OS, but step 4 when I try to install TWRP it fails and when trying to boot I get error "Only official released binaries are allowed to be flashed(vbmeta)" and I need to reinstall stock OS for it to boot again. Any Suggestions what I may be missing or doing wrong?
hakkers420 said:
Hi thanks for all your work. Question , I do step 3 successfully and it boots to OS, but step 4 when I try to install TWRP it fails and when trying to boot I get error "Only official released binaries are allowed to be flashed(vbmeta)" and I need to reinstall stock OS for it to boot again. Any Suggestions what I may be missing or doing wrong?
Click to expand...
Click to collapse
When you do step 3 and boot to the os make sure you verify that bootloader unlock is still enabled in Developer Options. If it is, I suggest reinstalling stock and then starting over.
agreenbhm said:
When you do step 3 and boot to the os make sure you verify that bootloader unlock is still enabled in Developer Options. If it is, I suggest reinstalling stock and then starting over.
Click to expand...
Click to collapse
When I check OEM Unlock it's selected to ON its 'greyed out' bootloader is already unlocked.
hakkers420 said:
When I check OEM Unlock it's selected to ON its 'greyed out' bootloader is already unlocked.
Click to expand...
Click to collapse
Good, that's what it should be. Try reflashing the vbmeta disabler again and then flashing TWRP.
agreenbhm said:
Good, that's what it should be. Try reflashing the vbmeta disabler again and then flashing TWRP.
Click to expand...
Click to collapse
So I tried that but it fails in Odin.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 0 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> vbmeta.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hakkers420 said:
So I tried that but it fails in Odin.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 0 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> vbmeta.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I know I ran into this once the past few days but am having difficulty remembering exactly how I resolved it. I think your best bet is to start from scratch, reinstalling stock and doing a factory reset.
agreenbhm said:
I know I ran into this once the past few days but am having difficulty remembering exactly how I resolved it. I think your best bet is to start from scratch, reinstalling stock and doing a factory reset.
Click to expand...
Click to collapse
Thanks will give it another shot see what happens.
On the page for unlocking bootloader that you provided are you supposed to do all 7 steps or can I just do up to step 3 and not worry about 4-7?
hakkers420 said:
On the page for unlocking bootloader that you provided are you supposed to do all 7 steps or can I just do up to step 3 and not worry about 4-7?
Click to expand...
Click to collapse
Correct, you can stop after 3.
Figured it out, before step 4 boot to OS and reenable developer options and USB Debugging.
agreenbhm said:
Correct, you can stop after 3.
Click to expand...
Click to collapse
Now step 6 when trying to boot to TWRP it boots to the stock recovery for some reason. I think I may have to take a break for a bit.
edit: after a break and a reinstall of twrp all seems to be good now
agreenbhm said:
If by GSI you mean the Lineage .tar file I linked to, then yes. That particular file is more than a GSI, it is a super partition including the GSI, vendor, product, and odm partitions. Flash this via Odin to AP and in the future you can install standalone GSIs of Lineage using TWRP with the instructions at the bottom of the post.
Click to expand...
Click to collapse
I am a huge fan of GSI but doesnt realy understand what it is and how to use it ( this isnt my first account just forget my pw XD) so it would be a pleasure for me if you would write a few words about it thanks in advantage :_)
agreenbhm said:
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release was Android 10-based). I have attempted to make this install as painless as possible. Please read the notes below carefully. WARNING: you are responsible for your own actions, so please be careful. If you brick something, that's on you.
Update to latest stock ROM as of 3/24/2022 (T500XXU3BVB3).
Unlock bootloader using steps described in this thread. Make sure that after your device wipes and reboots after the bootloader is unlocked that you go through the setup wizard again and back into Developer Settings and enable OEM Unlocking. I think you need to connect to wifi for this option to appear, so if you don't see it try that.
Boot to download mode, then install VBMeta Disabler via Odin.
Reboot to download mode, then install TWRP via Odin.
Reboot to download mode again, then install LineageOS via Odin.
Boot to TWRP, push "fix_brightness.sh" to the device and run it, then format data.
That should be all that is necessary. If you get stuck in a loop with TWRP where you can't boot to system (seems to happen regularly to me) I included a script in TWRP that should get you out. From the TWRP cli run the command "exit_twrp". It will say "out of space" when finished (instantly). Then reboot to system. If for some reason that still doesn't work and you boot back to TWRP, repeat.
Known Issues:
OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
TWRP touchscreen seems to be unresponsive for several seconds upon first booting into TWRP. Just patiently wait a few seconds and try again.
You'll see errors in TWRP about /keyrefuge, etc. Ignore that. I believe it's related to the inability to decrypt internal storage using FBE.
Installing Gapps (Nik and Flame) doesn't work, but no worry because the ROM includes Gapps
Security: by default this ROM has root access and USB debugging (adb) is enabled unsecured. Anyone can plug into it and have full root access. So disable USB debugging if you don't want that! TWRP is the same way, though data is encrypted. Someone could install malware into your system partition though. In short, this is for hobbyists, not someone with security concerns.
Sources:
Device tree for TWRP from my Github; branch TWRP-11 specifically: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Kernel sources from Samsung: https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#
Files:
LineageOS 19.1 Beta2
TWRP 3.6.1 Beta 5
VB Meta Disabler
Brightness Fix
Updates:
You can update this ROM yourself by installing a new GSI to the system partition.
Download new GSI from here onto Micro SD card: https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
Boot into TWRP
Run command: blockdev --setrw /dev/block/mapper/system
Run command: dd if=/external_sd/<your_downloaded_gsi.img> of=/dev/block/mapper/system bs=1M
Wait for dd command to finish, then reboot into system. Don't forget to use "exit_twrp" command if you keep booting into TWRP.
Click to expand...
Click to collapse
thank you you did a amazing work
Noskilldode said:
I am a huge fan of GSI but doesnt realy understand what it is and how to use it ( this isnt my first account just forget my pw XD) so it would be a pleasure for me if you would write a few words about it thanks in advantage :_)
Click to expand...
Click to collapse
In short, a GSI is a special type of system image that is made to work across multiple devices. It stands for generic system image. The ROM that I included in the op is a super image which contains not only the system partition but also the vendor partition, which includes device specific drivers and things like that, plus a couple other partitions.
What is the syntax to push the fix_brightness file? I have it on the extternal SD card. Can I just copy to a directory on the internal SD?

How To Guide How to Root S23 (S91*B/N/0)

How to Root Samsung S23 (SM-S91*B/N/0)
WARNING!
Before you root your device you must be aware that
This will void warranty.
As of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
There are many features stop working when you unlock bootloader other than S pay/Pass like Samsung Health, Secure Folder, Galaxy Watch pairing issue, Issue connecting old gear watch (S3 or earlier), Google Pay etc but some ROMs are patched for all these mentioned features, you can use custom ROM or patch it yourself for stock ROM. Still you may trouble using some bank apps and these may fixed by adding these apps to Magisk Hide
There may be some knox features there which you may not able to use but I can't list those as I never used. Just Google It
Patched featurs are working today when writing this, No idea if it may stop working next moment/tomorrow or later
Also to note, once you root, you can't go back to "pre-rooted" state completely. It is one way!
OTA won't work once you root device.
ROOT with caution.
You can unroot & Relock bootloader after flashing stock firmware, but still your warranty flag remain 0x1 and most of countries it still voids warranty. Also after unrooting & relocking bootloader, some knox features never work again.
How to Unlock Bootloader
Follow below four steps to ulock the bootloader
1.Enable Developer Option
Open the Settings app on your Galaxy device.
Choose About > Software Information.
Now tap on Build Number 7 times to enable the developer option.
You’ll get a message “You’re now a developer.”
Now Developer option has been enabled.
2: Enable OEM Unlock
Go to the Settings app again on your device.
Navigate to the Developer option.
Enable the toggle next to OEM Unlocking.
Tap YES to turn on the confirmation dialog box.
3: Boot Your device to Download Mode
While device is booted → Connect device to PC → Select to Restart → As soon as device screen turns off, Press and hold Volume Up + Volume Down simultaneously OR In case device is powered off Press and hold Volume Up + Volume Down simultaneously and connect your device to the PC via a USB Cable.
You can see the warning message on your device and release the pressed keys.
Finally, press the Volume Up key once, and you will be booted into Download Mode.
4: Unlock Bootloader
Once device booted into Download Mode, you will see option to long press Volume up to unlock bootloader,Now, press and hold the Volume Up key for a few seconds., Here, you’ll get a confirmation whether you are sure to proceed.
Use the Volume Up button to reply to the confirmation.
This will erase all the data on your device and unlock the bootloader.
Once completed, your device will automatically boot up to the OS.
Now you have successfully unlocked the bootloader
How to root S23
Instructions for stock non rooted ROM​
Use either samfirm.js, Frija, or Samloader to download the latest firmware zip of your device directly from Samsung servers.
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Download and Install latest Magisk apk (Get Latest Magisk apk from here)
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the AP tar file
When done, copy patched file to PC
Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.
Your device should reboot automatically once Odin finished flashing. Agree to do a factory reset if asked.
Install the Magisk app you’ve already downloaded above and launch the app. It should show a dialog asking for additional setup.
Let the app do its job and automatically reboot the device. Voila!
Upgrading the OS​Once you have rooted your Samsung device, you can no longer upgrade your Android OS through OTA. To upgrade your device’s OS, you have to manually download the new firmware zip file and go through the same AP patching process written in the previous section. The only difference here is in the Odin flashing step: do NOT use the CSC tar, but instead use the HOME_CSC tar as we are performing an upgrade, not the initial install.
Important Notes​
Never, ever try to restore either boot, recovery, or vbmeta partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.
To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always patch AP in the Magisk app and use that instead.
Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading.
PS : It is strongly recommended to make EFS backup once you root device and save to safer place like on cloud or PC
For TWRP : Read here
Credit : topjohnwu Guide part taken from Origin guide here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Will try this now. Should the other slots BL/CP/CSC be filled with the firmware files when flashing this AP?
zzattack said:
Will try this now. Should the other slots BL/CP/CSC be filled with the firmware files when flashing this AP?
Click to expand...
Click to collapse
No needs, Flash requied file with AP slot onl
I flashed the AP file. I could not enter recovery mode to do factory reset. Device went into boot-loop mode, but after some failed attempts launched recovery by itself. Then I was able to do factory reset, and device boots properly.
Magisk (25.2 from apk in your zip file) still indicates: not installed. Ramdisk yes. Zygisk no (obviously).
zzattack said:
I flashed the AP file. I could not enter recovery mode to do factory reset. Device went into boot-loop mode, but after some failed attempts launched recovery by itself. Then I was able to do factory reset, and device boots properly.
Magisk (25.2 from apk in your zip file) still indicates: not installed. Ramdisk yes. Zygisk no (obviously).
Click to expand...
Click to collapse
You flashed AP file I have provide or one with patched with magisk yourself?
Earlier today I used Magisk alpha to patch the AP from WA6 firmware.
Some minutes ago I flashed AP file from you on top. It only wrote boot and vbmeta.
Any debug info/logging I can provide?
zzattack said:
Earlier today I used Magisk alpha to patch the AP from WA6 firmware.
Some minutes ago I flashed AP file from you on top. It only wrote boot and vbmeta.
Any debug info/logging I can provide?
Click to expand...
Click to collapse
Odin was passed successful?
Kernel I have provided is surely Patched., May be needs to contact Jhon with log. Kindly post in Magisk thread
Yes, no problems from ODIN. I will try to find the magisk thread and useful logging infos.
Magisk log added
zzattack said:
Magisk log added
Click to expand...
Click to collapse
If you can save log from Magisk App - Logs - Save and attach here
Also show me screenshtot of magisk app
Nice!!!
zzattack said:
Magisk log added
Click to expand...
Click to collapse
I have updated link (with debug version), Can you flash again and Install included Magisk? After this take log so I can send to Jhon with debug version. Also take screenshot of magisk app
Logs + magisk screenshot attached with debug image and apk.
zzattack said:
Logs + magisk screenshot attached with debug image and apk.
Click to expand...
Click to collapse
Do you have telegram? If yes inbox me. We can do some test with easy communication
@zzattack or any other user
I have updated link(v3), If anyone available to test new version.
.
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
zzattack said:
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
Click to expand...
Click to collapse
Great,
That's awesome news!
Thank you very much for testing.
Any other user available to test then let me know, Next test will be for Root with Magisk Stable (25.2)
Debug version already reported working (reported by @zzattack )
.
I'm waiting for my s23 ultra next week and then I'll be able to test.
I'm aware I'll lost Samsung Pay and pass. I really don't care... Don't use it... But, will I have troubles with Google pay and secure folder if rooted?
zzattack said:
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
Click to expand...
Click to collapse
does zygisk work?

Categories

Resources