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.
Related
I do not own the device anymore. So I can't support the thread anymore, if anyone wants to carry on just pm me. But as far as I know there are newer threads about this topic. Thank you
Hey there,
I decided to write a how-to on gaining root for the g531f Galaxy grand prime ve.
This should work for all grand prime devices based on marvel soc.
About this method:
Knox counter was not tripped for my device using this method.
The main steps, flashing latest stock and twrp, are perfomed by Odin. To gain root chainfire's supersu is flashed with twrp. If you are unsure about any step there are enough guides found on xda refering odin, twrp and supersu.
So let's get started.
I`M NOT RESPONSIBLE FOR ANY DAMAGE OR WARANTY LOST ON YOUR PHONE.
1. Make sure your device drivers is installed properly
2. Get Odin v3.09 for example here:
http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
3. Get your latest firmware and extract it once
http://www.sammobile.com/firmwares/database/SM-G531F/
4. Get twrp
https://dl.twrp.me/grandprimevelte/twrp-2.8.7.1-grandprimevelte.img.tar.html
5. Get supersu by chainfire
Latest beta
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or confirmed working version 5.52 beta, if the latest doesn't work thanks to @XelSam:
https://download.chainfire.eu/743/Su...erSU-v2.52.zip
6. Backup all things you need and copy supersu to external sd card
7. Boot to stock recovery and perform a factory reset and wipe internal memory.
(power off device and keep holding volume up, home and power button)
8. Reboot to download Mode, then start odin and connect your device
(holding volume down, home and power button to get into download Mode)
9. Flash your firmware with Odin by using the AP button and hit start. Make sure repartition is NOT selected and untick auto reboot. This step takes some time
10. Boot to download Mode again. And flash twrp as mentioned above. Using AP and the same selection.
--if twrp doesn't boot you have to use another firmware (step 9) post #20-- thanks to @bluepower
11. Boot into twrp recovery. Hit install and select the supersu zip file then clean cache and dalvic.
(holding volume up, home and power button)
12. Reboot your phone and see if everything is working.
13. Go to dev settings and tick "manufacturer unlock" to prevent fap lock.
(unlock dev settings: Settings - about phone - tap build number 7 times). If that doesn't work check post #4 and #6 and say thx to @hck5
14. Make a nandroid in twrp recovery to have a clean rooted rom to return to if anything gets messed up with further modding (eg. xposed framework etc.)
10.1 100%Working firmware
If you can't find a version that allows to flash twrp (carrier lock) use this unbranded one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
Check gps. If it doesn't lock install this app and configure your region.
https://play.google.com/store/apps/details?id=by.zatta.agps
CREDITS and CUDOS
chainfire
Twrp team
Odin team
Samsung
If you are interested in xposed check wanams xposed thread.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
The x86 version is working fine for me
For audio enhancement I'm using dolby atmos cause Viper didn't do the trick for me.
http://forum.xda-developers.com/android/apps-games/mod-dolby-atmos-t3109446
So have fun with your unchained device and hit thanks button.
Great job!
Hey there i have the same model and i'm happy that last night i've found your post
i used the pre-rooted firmware and i had the system ui rebooting problem after i uninstalled any of the apps
also i've seen guys who had that security tab problem from settings (didn't happened to me)
I am extracting the stock rom now i prepared everything
i also wanted so badly the viper fx cause the sound is pretty low
i searched for alternative but here you are with dolby atmos
i greatly thank you for the effort for posting this tuto
i will be back after i do the job!
Thanks!!!
---------- Post added at 12:46 PM ---------- Previous post was at 12:25 PM ----------
Root and twrp on stock rom it's working great!!
i just flashed the wanam xposed thu twrp everything done
the only bad part is the "recovery is not seandroid" but this is just a red small message above when i enter twrp and it has no bad effect! only visual
i am clearing dalvik and cache after every flash so i keep it smooth and nice i can't wait to test modules on this phone i will post screenshots as proofs
hck5 said:
Root and twrp on stock rom it's working great!!
i just flashed the wanam xposed thu twrp everything done
the only bad part is the "recovery is not seandroid" but this is just a red small message above when i enter twrp and it has no bad effect! only visual
i am clearing dalvik and cache after every flash so i keep it smooth and nice i can't wait to test modules on this phone i will post screenshots as proofs
Click to expand...
Click to collapse
Thx for your feedback and confirmation that it is working.
So have fun with your device.
BTW don't forget to make a nandroid backup before you mess around with xposed modules to get back to your rooted rom. I destroyed my system twice with xposed.... And I had to go through this procedure again (thanks touchwiz).
okay
ok. thanks for the advice i was just messing with the modules and i have no backup xD
there is a pic with all i have so far
{
"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"
}
---------- Post added at 02:25 PM ---------- Previous post was at 02:08 PM ----------
custom binary locked by fap lock.... shiet... this is the google account thingie
do you know any way to bypass it? it means i can't add my google account
i just tried to reboot in recovery and it's showing up and can't boot my phone so far...
ok flashing stock fixes it
and this is the ultimate fix
"i faced the same !steps you need to follow settings>search>reactivation lock>log in into Samsung account and disable" thanks to bhavstech xda member
hck5 said:
custom binary locked by fap lock.... shiet... this is the google account thingie
do you know any way to bypass it? it means i can't add my google account
i just tried to reboot in recovery and it's showing up and can't boot my phone so far...
ok flashing stock fixes it
Click to expand...
Click to collapse
Try to unlock via dev settings. Manufacturer unlock.
http://forum.xda-developers.com/attachment.php?attachmentid=3495074&d=1443947143
If that doesn't work you have to delete your Google account as far as I know.
For me it is working with Google account, but I can't remember if I ticked the dev setting option before or after adding my Google account.
for me has been this one
klausel said:
5. Get supersu by chainfire
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Probably a stupid question but why can't we just install SuperSU from Play Store?
Edit: Okay, I've noticed that the version in the xda thread is newer. Anyway why not install it the usual way (sideloading)?
eau4x6 said:
Probably a stupid question but why can't we just install SuperSU from Play Store?
Edit: Okay, I've noticed that the version in the xda thread is newer. Anyway why not install it the usual way (sideloading)?
Click to expand...
Click to collapse
I don't know exactly what you mean with sideloading app.
But as far as I know root is needed to install supersu via Google play store. Of course you can sideload the app via adb shell when booted to twrp. But I wanted to keep the tutorial simple without setting up adb etc.
Hope your question is answered.
Thank's for recovery
I thing a new nice rom will coming soon for 531F
klausel said:
Of course you can sideload the app via adb shell when booted to twrp.
Click to expand...
Click to collapse
Transfering APK to internal storage/sd card and installing from there (by opening it in file manager) is what I had in mind.
I don't think is that easy.. You must set system read and write and I guess twrp helps it installing supers in a better way than your file manager does
---------- Post added at 12:49 PM ---------- Previous post was at 12:45 PM ----------
We just need a hell of a rom
finally thank you very much! ?
Hello i have a new SM-G531F and i'm trying to install TWRP but don't result.
Version: G531FXXUAOI4
Compilation: LMY48B.G531FXXUAOI4
Lollipop 5.1.1
I have samsung drivers installed. Odin 3.10.7.
I install via ODIN the tar file of TWRP with sucess, but when i try to enter goes to stock recovery.
With volume up + home + power before enter the stock recovery i can see this message "recovery is not seandroid enforcing"
bluepower said:
Hello i have a new SM-G531F and i'm trying to install TWRP but don't result.
Version: G531FXXUAOI4
Compilation: LMY48B.G531FXXUAOI4
Lollipop 5.1.1
I have samsung drivers installed. Odin 3.10.7.
I install via ODIN the tar file of TWRP with sucess, but when i try to enter goes to stock recovery.
With volume up + home + power before enter the stock recovery i can see this message "recovery is not seandroid enforcing"
Click to expand...
Click to collapse
The same strange problem is @XelSam facing, too.
I don't know why it is booting to stock recovery instead of twrp. What is written on top when you boot to dl mode? Could you post a picture, please.
Maybe it is the odin version or the recovery partition is locked.
So here is what you might try
Make sure your device is not fap locked
1. Get the odin version from op
2. Flash firmware with reboot unticked
3. Power down device and boot directly to dl mode again (do not boot the system) and flash twrp with reboot unticked.
4. Power down the device and boot try to boot to twrp
Good luck
klausel said:
The same strange problem is @XelSam facing, too.
I don't know why it is booting to stock recovery instead of twrp. What is written on top when you boot to dl mode? Could you post a picture, please.
Maybe it is the odin version or the recovery partition is locked.
So here is what you might try
Make sure your device is not fap locked
1. Get the odin version from op
2. Flash firmware with reboot unticked
3. Power down device and boot directly to dl mode again (do not boot the system) and flash twrp with reboot unticked.
4. Power down the device and boot try to boot to twrp
Good luck
Click to expand...
Click to collapse
DL mode is written:
ODIN MODE(MULTI CORE DOWNLOAD)
PRODUCT NAME: SM-G531F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0x0
SECURE DOWNLOAD: ENABLED
RP SWREV: S1, L1, M1
Ok. I'm going to try again.
Thanks
bluepower said:
DL mode is written:
ODIN MODE(MULTI CORE DOWNLOAD)
PRODUCT NAME: SM-G531F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0x0
SECURE DOWNLOAD: ENABLED
RP SWREV: S1, L1, M1
Ok. I'm going to try again.
Thanks
Click to expand...
Click to collapse
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
klausel said:
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
Click to expand...
Click to collapse
The phone is brand new. I'm from Portugal, carrier MEO
I think the firmware is not avaiable.
bluepower said:
The phone is brand new. I'm from Portugal, carrier MEO
I think the firmware is not avaiable.
Click to expand...
Click to collapse
I see, looks like your rom is carrier specific. I just checked for your firmwares, I even could not find your version.
To unbrand your device you can try to flash another version.
I used this one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
I DON'T KNOW IF THIS WILL WORK, CAUSE MY DEVICE IS UNLOCKED. SO THERE IS A SMALL POSSIBILITY THAT THIS WILL BRICK YOUR DEVICE. BUT THERE ARE SO MANY PEOPLE THAT FLASH THE PREROOTED ONE AND NOBODY REPORTED THAT, YOU CAN TRY THIS.
BE CAREFUL, THIS could RESULT IN WARRANTY LOSS. SO IF YOU HAVE TO SEND IN DEVICE FLASH BACK A CARRIER SPECIFIC ROM BACK.
So it is on you if you are willing to try it.
klausel said:
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
Click to expand...
Click to collapse
klausel said:
I see, looks like your rom is carrier specific. I just checked for your firmwares, I even could not find your version.
To unbrand your device you can try to flash another version.
I used this one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
I DON'T KNOW IF THIS WILL WORK, CAUSE MY DEVICE IS UNLOCKED. SO THERE IS A SMALL POSSIBILITY THAT THIS WILL BRICK YOUR DEVICE. BUT THERE ARE SO MANY PEOPLE THAT FLASH THE PREROOTED ONE AND NOBODY REPORTED THAT, YOU CAN TRY THIS.
BE CAREFUL, THIS could RESULT IN WARRANTY LOSS. SO IF YOU HAVE TO SEND IN DEVICE FLASH BACK A CARRIER SPECIFIC ROM BACK.
So it is on you if you are willing to try it.
Click to expand...
Click to collapse
I'm back. Thanks. I'm going to try now.
Edit: Ok, done.
I installed de G531FXXU1AOI4_G531FOXX1AOI3_TPH for Portugal.
Then get the software update to the J2.
Great job, thanks a lot.
bluepower said:
I installed de G531FXXU1AOI4_G531FOXX1AOI3_TPH for Portugal.
Then get the software update to the J2.
Great job, thanks a lot.
Click to expand...
Click to collapse
Glad to know you got it and thanks for your feedback.
To rule out all misunderstandings and help other people with the same problem.
1. You flashed a rom from another carrier for your region and 2. updated it to the latest version via ota.
3. You installed twrp and 4. supersu
Is that the way you proceeded.?
Did the line for fap lock appear in dl mode?
Thanks in advance
Team Win Recovery Project 3.0.2-0
This is for the SM-P580 (gtanotexlwifi) and SM-P585, SM-P585N0, SM-P585M, SM-P585Y (gtanotexllte) Exynos models only! Do not flash on other models!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy Tab A 10.1 (2016) stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
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:
WiFi version: http://teamw.in/devices/samsunggalaxytaba101wifi2016spen.html
LTE version: http://teamw.in/devices/samsunggalaxytaba101lte2016spen.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://build.nethunter.com.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
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.
Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore.
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 gtanotexlwifi (WiFi) or gtanotexllte (LTE).
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] + [Power] 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 and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
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.
--- or (not both) ---
If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* 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 - Official release 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.0 (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 (WiFi): https://github.com/TeamWin/android_device_samsung_gtanotexlwifi (android-6.0)
Device tree (LTE): https://github.com/TeamWin/android_device_samsung_gtanotexllte (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_universal7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
It's possible to use this metod with T585 ?
Working very well on my tab A 10.1 P585Y.. bug.. cant read internal storage but it can use sd card..
I already root my tab a 10.1 p585y using this twrp.. thanks for making this recovery for our p585y.. now we need custom rom such as resurrection remix..
Worked well
Followed the instructions carefully and I'm now rooted! The swipe bar in TWRP seemed to have a little problem. When I first swiped it didn't stick and floated back over to the left side. I tried with my finger several times and then with the spen. It finally registered. It did the same swiping to install SuperSU. Not sure if it just was slow in registering the swipe or something with my system. I was a little nervous when I rebooted but all seems to be well. Thanks for the guide!
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
loraxnope said:
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Click to expand...
Click to collapse
I haven't found a good stock ROM yet (proper US version). No way I'm rooting my tablet before that.
My current tablet is untouched (in terms of custom recovery and ROMs). Is there a way of pulling out a stock ROM from it?
loraxnope said:
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Click to expand...
Click to collapse
Im using p585y version.. same here i didnt find any firmware on internet.. so my solution is using kies.. just install kies and recover it.. work for me.. right now sammobile also doesnt have the firmware yet..
Hope im helping.. press thanks if im help..
---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------
focus-pocus said:
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
Click to expand...
Click to collapse
Will try it bro.. right now im using s7 mod on p585y but doesnt show on settings>storage but it seem working background..
focus-pocus said:
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
Click to expand...
Click to collapse
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
cliemonster said:
Followed the instructions carefully and I'm now rooted! The swipe bar in TWRP seemed to have a little problem. When I first swiped it didn't stick and floated back over to the left side. I tried with my finger several times and then with the spen. It finally registered. It did the same swiping to install SuperSU. Not sure if it just was slow in registering the swipe or something with my system. I was a little nervous when I rebooted but all seems to be well. Thanks for the guide!
Click to expand...
Click to collapse
It is not your system - I had the same issue with the swipe bar. Like you, I tried several times and it finally accepted the swipe (even the pen had a few non-registering swipes).
Hi, can you plz update the links. Cuz idlekernel.com is currently not reachable nor the page of your source code for kernels :-/
And I remain highly unclear if I need a kernel for this dm-verity thing or not. I don't understand the issue reg. system boot partion. What is this? Android is already installed on the TabA - so what should I change there? Or is it for root apps?
If you want to root your tab and install TWRP you need the Kernal to turn off dm-verify and encryption. Do it in the exact order in the OP and don't let your tab try to boot rooted without turning off dm-verify.
BohArie said:
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
Click to expand...
Click to collapse
I think you'll find it does. Works on pretty much any Samsung device running Marshmallow.
BohArie said:
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
Click to expand...
Click to collapse
Yeah, that's what I expected. But this mod also replaces sm binary, so I suspect that this should enable converting to adoptable storage through adb shell (so-called S7 trick). Have you tried that?
focus-pocus said:
Yeah, that's what I expected. But this mod also replaces sm binary, so I suspect that this should enable converting to adoptable storage through adb shell (so-called S7 trick). Have you tried that?
Click to expand...
Click to collapse
ive done that.. still not working.. by the way.. i already root my devices when i delete some apps, fb, skypes and any apps that need account force close.. why is that??
BohArie said:
ive done that.. still not working.. by the way.. i already root my devices when i delete some apps, fb, skypes and any apps that need account force close.. why is that??
Click to expand...
Click to collapse
Restore your stock boot image. Apply the patch. Format your SD card as portable storage, reboot.
Look out in status bar for an SD card notification.
If you don't see it go to settings>storage. Tap the SD card choose format then internal.
thanks.. working well but it say that i already use 91% of my storage.. now i just need to install app.. im using enable adoptable storage zip then i put command using adb..
BohArie said:
thanks.. working well but it say that i already use 91% of my storage.. now i just need to install app.. im using enable adoptable storage zip then i put command using adb..
Click to expand...
Click to collapse
Take that with a pinch of salt. Make sure you migrate your data to the sdcard.
focus-pocus said:
I haven't found a good stock ROM yet (proper US version). No way I'm rooting my tablet before that.
My current tablet is untouched (in terms of custom recovery and ROMs). Is there a way of pulling out a stock ROM from it?
Click to expand...
Click to collapse
Could you tell me what your baseband version / build number is? I might try flashing one of the other region's ROMs since there's a few from Hong Kong, Turkey, etc out on Updato
soft bricked device,
i soft bricked my device trying to do the TWRP recovery and it kept saying unable to mount data so i factory reset and it still didnt work so then i wiped a bunch of stuff and now it's soft bricked.
im going to download the Korean Firmware for this device, but is there anyway i can avoid that? any tips?
{
"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 custom recovery for the Tab A SM-T280/T285. Latest build is 3.2.1-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 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.
UPDATE 08/01/2018 - TWRP updated to version 3.2.1-1
UPDATE 21/11/2017 - Magisk updated to v14
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. 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.
DOWNLOAD:
TWRP_3.0.2-1_SM-T280_261016
twrp_3.2.1-1_sm-t280_080118
twrp_3.2.1-1_sm-t285_080118
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this. (FIXED)
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
This step only required for the SM-T280
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v14:
1. Download Magisk v14 to your device
Magisk v14
2. Install the Magisk v14 zip with TWRP
This step only required for the T280
3. Flash the patched boot image below with TWRP.
magiskv14_boot_aqd1
4. Reboot
5. Install Magisk manager
Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
Help me root my phone
Sent from my SM-G903W using XDA Free mobile app
ashyx said:
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
Click to expand...
Click to collapse
interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
jedld said:
interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
Click to expand...
Click to collapse
Hi Jed, after trying various different configs in twrp and even modifying the graphics source code it made no difference.
Using the the touch debugger in twrp it was apparent that the touch was responding fine.
So I turned my attention to the kernel.
After several builds of modifying the cpu config making no difference, it turns out TWRP only supports double buffering, but the kernel was forcing triple buffering.
It seems this was causing an extra frame to be displayed causing what seemed like lag and explains why when pressing the screen a second time would cause the frame to update.
The page that was in ram had changed when tapping a button, but the wrong frame in the buffer was displayed until the next touch which then updated the display.
Disabling triple buffering in the kernel fixed the issue.
jaritico said:
PRE-ROOTED boot image can be used on 285? (needed for Systemless Root ) same at magisk patched boot
Click to expand...
Click to collapse
You don't need it for the T285.
Worked perfectly, first time.
Installed supersu via trwp and then img via boot in twrp also.
Thank you for the clear tutorial.
Excellent
just about to root mine now are there any custom roms that can go on it?
ashyx said:
TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 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.
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. 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.
TWRP_3.0.2-1_SM-T280_261016
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v7:
1. Download Magisk v7 to your device
Magisk v7
2. Install the Magisk v7 zip with TWRP
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280
4. Reboot
To Install Magisk v7 with SuperSu:
1. Follow the instructions above to install SuperSu
2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280
4. Reboot
5. Install Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
I don't know how this is working for others, but installing SuperSu uninstalled android.
Ethan-56 said:
I don't know how this is working for others, but installing SuperSu uninstalled android.
Click to expand...
Click to collapse
It does what? [emoji55]
Also please don't quote the entire OP.
ashyx said:
It does what? [emoji55]
Also please don't quote the entire OP.
Click to expand...
Click to collapse
OK, I'm new to XDA. I installed TWRP and supersu, but when switching to Odin to install that other supersu thing, It wouldn't boot properly I tried deleting supersu, but I uninstalled android entirely. I got the splash screen, but TWRP warned that there was no OS installed. Does XDA Developers have a tutorial on reinstalling Android? I also can't locate the stock firmware and I forgot to back up my system.
Download the stock firmware from sammobile or UPDATO and flash with odin.
T280 comes in on Tuesday, will try this method and report back. Seems fairly easy, thanks for allowing us to have TWRP and root, it will help in debloating this 8gb version i picked up.
Any suggestion how to install Magisk v9?
Root done in five minutes, I can't believe!
Thanks ashyx!
What Gives???
magiskv7_boot_sm-t280 in first post Failed to download, registered in Microsoft Security as a Trojan! Also download page in Android file host has the developer name as "ashyt6" and not "ashyx."
Anyone else noticed this, or did I miss something???
gello924 said:
magiskv7_boot_sm-t280 in first post Failed to download, registered in Microsoft Security as a Trojan! Also download page in Android file host has the developer name as "ashyt6" and not "ashyx."
Anyone else noticed this, or did I miss something???
Click to expand...
Click to collapse
Ffs have you never heard of false positives? [emoji55] What do you expect you're installing files that compromise an operating system.
Also what relevance is it that my AFH user name is different?
ashyx said:
TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 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.
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. 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.
TWRP_3.0.2-1_SM-T280_261016
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v7:
1. Download Magisk v7 to your device
Magisk v7
2. Install the Magisk v7 zip with TWRP
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280
4. Reboot
To Install Magisk v7 with SuperSu:
1. Follow the instructions above to install SuperSu
2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280
4. Reboot
5. Install Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
followed your instruction & it works, many thanks..much appreciated:good::good::good:
Hi ashyx
To start sorry for my English, I am French and a bad student.
I want to thank you for this guide and all of your contribution on the Android scene :good:
I followed your instructions successfully but I have some questions
Can I install Busybox? If so, is it useful? If yes, how?
I have to do update Magisk v7 to v9?
To finish what is the best solution to extend the internal memory? Actually I used Link2Sd but I'm not satisfied
Thanks again for your work, a little boy will be in the angels when he will receive his gift of Christmas
Error - Security check (boot)
While odin is telling me everything it's correct and shows PASS message on my tablet Sm-t280 shows Security check fail - (boot) and when i restart i can't see any changes,
Oem unlocked and usb debug activated i tried flash with twrp image file and with supersu img file.
I hope your help thanks
{
"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"
}
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this low-cost tablet. My thanks to @mehanik6 for blazing this trail on 4PDA.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
twrp-3.7.0_11-0-T290XXU3CVG3-20221120.tar.md5
twrp-3.7.0_11-0-T290XXU3CVG3-20221120.img
Build Archives:
Android File Host
Change Log:
v3.7.0_11-0: (2022-11-20)
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
Updated to T290XXU3CVG3 OEM stock kernel.
v3.6.1_11-0: (2022-03-27)
Updated to TWRP 3.6.1 release built from AOSP-11 branch.
Updated to T290XXU3CUK4 OEM stock kernel.
Using FFS MTP so that custom kernel builds are no longer necessary.
v3.6.0_11-1: (2022-02-20)
Added wipeingui for ext4 partitions.
v3.6.0_11-0: (2022-01-23)
Updated to TWRP 3.6.0 release built from AOSP-11 branch.
v3.5.2_9-0: (2021-10-17)
Updated to T290XXU3CUG4 posted kernel source.
v3.5.2_9-0: (2021-05-16)
Updated to T290XXU3BUC1 posted kernel source.
Updated to TWRP 3.5.2 release built from android-9.0 branch.
v3.5.1_9-0: (2021-03-30)
Updated to T290XXU3BUB2 posted kernel source.
Updated to TWRP 3.5.1 release built from android-9.0 branch.
v3.5.0_9-0: (2021-01-02)
Updated to T290XXU3BTI2 posted kernel source.
Updated to TWRP 3.5.0 release built from android-9.0 branch.
v3.4.0-1: (2000-12-09)
New custom T290XXS3ATC1 kernel that actually fixes MTP support.
v3.4.0-0: (2000-12-04)
Included legacy aboot and vaultkeeper in tarball to allow Odin flash on Android 10 OEM firmware.
v3.4.0-0:
Initial release based on @mehanik6's device tree and T290UES3ATC1 kernel.
Fixed MTP
Default language is now English
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler that preserves encryption from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to system
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.
Source:
android_device_samsung_gtowifi
Donations:
Your support is always appreciated! Just click here.
are there any custom roms for sm-t290?
Tralien said:
are there any custom roms for sm-t290?
Click to expand...
Click to collapse
I'll have a release of my Nexus Stock custom ROM shortly. It's basically the same as what I've been releasing for the 10.1" version of this tablet over the past year. I'm basically just waiting for Samsung to post the latest kernel source.
Update for TWRP v3.5.0 release...
Downloads:
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.tar.md5
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.img
Change Log:
v3.5.0_9-0:
Updated to T290XXU3BTI2 posted kernel source.
Updated to TWRP 3.5.0 release built from android-9.0 branch.
I have tried installing via Odin your twrp custom recovery for my t290 device.
The process with Odin seem to go well and after installation my device restarts however, when I press the + volume button, android recovery shows up and not TWRP.
Any idea why?
dark_friend said:
I have tried installing via Odin your twrp custom recovery for my t290 device.
The process with Odin seem to go well and after installation my device restarts however, when I press the + volume button, android recovery shows up and not TWRP.
Any idea why?
Click to expand...
Click to collapse
There are two issues here:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.
Magendanz said:
There are two issues here:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.
Click to expand...
Click to collapse
Got it! thank you very much!
Magendanz said:
There are two issues here:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.
Click to expand...
Click to collapse
Presumably, if you miss the first time, you reflash and try again? (and as many times as needed?)
Heeni said:
Presumably, if you miss the first time, you reflash and try again? (and as many times as needed?)
Click to expand...
Click to collapse
If you miss, hold Power + Vol Down for 7 seconds during the boot animation to do a hard reset and try again. Alternatively, you can wait for it to finish booting and then restart, but then you risk Samsung's VaultKeeper "feature" putting the bootloader into a stealth locked state. You can prevent that by connecting to the Internet, enabling Developer Options, and then confirming the OEM Unlocking state as soon as you finish setup. (You don't need to log into Google or Samsung services for Vaultkeeper to maintain the bootloader unlock, but you've got to have Internet access and reenable Developer Options right away.)
Thanks for pointing out some of the potential potholes along the way. I'm not a stranger to modding, but have experience only with fastboot, so the Samsung method is a whole new ballgame for me. Maybe I just need to take a deep breath and jump in. And backup everything before starting.
Heeni said:
Thanks for pointing out some of the potential potholes along the way. I'm not a stranger to modding, but have experience only with fastboot, so the Samsung method is a whole new ballgame for me. Maybe I just need to take a deep breath and jump in. And backup everything before starting.
Click to expand...
Click to collapse
Yeah, it never ceases to amaze me how Samsung believes it's adding value with Knox security features like Vaultkeeper and its special Download mode that only works with Odin. My main phone is a Pixel 4a, and I've never felt that Google has taken any flak for making bootloader unlocking and firmware flashing painless. Why does Samsung feel the need to reinvent the wheel?
Somewhat to my surprise, I was able to get TWRP installed and boot into it on the first try. In fact, the biggest difficulty by far was getting Samsung drivers to work in my Windows 10 vm. The vm is still having problems, so hopefully, now that TWRP is installed, I won't need to use Odin for a while.
Tried patching TWRP with Magisk. No bootloops or other drama, but wifi doesn't work. I notice on the Magisk Github site that a number of people are running into this. Fortunately, restoring the unpatched TWRP also restored wifi.
I think I can live without root much more easily than without wifi!
Heeni said:
Tried patching TWRP with Magisk. No bootloops or other drama, but wifi doesn't work. I notice on the Magisk Github site that a number of people are running into this. Fortunately, restoring the unpatched TWRP also restored wifi.
I think I can live without root much more easily than without wifi!
Click to expand...
Click to collapse
I have root and wifi, but didn't use the TWRP install method
Further to this post about the inability to set a password, PIN or pattern:
I reflashed the stock ROM and I can verify the following:-
Stock ROM with (or without) bootloader unlocked will allow me to set up a PIN (I didn't try the other options but would expect that they'd work.
As soon as I install TWRP, the stock ROM will no longer allow me to set up a PIN. I can have "swipe" or "nothing" to unlock, and that's it.
I've tried installing LineageOS 17 GSI, LineageOS 18 GSI and Magendanz's Nexus stock ROM. None of these will accept a PIN, password or pattern.
Therefore, I think that the issue has to do with TWRP, or possibly with something in the multidisabler script.
Googling has come up with nothing other than the instruction to remove /data/system/locksettings.db and related files. I've tried this numerous times without success. I've even tried comparing permissions and ownership with the (working) equivalent on my Moto phones, with no luck.
I'm happy to do any tests, provide logs etc if it would help. The only other alternative seems to be to revert to stock if I need to travel.
I'm going to be using the table in an install that does not allow easy access to be able to use the physical buttons, if I lock the boot loader back after all this will it keep root?
I need root so that I can modify the files necessary to make the tablet turn on automatically whenever power is connected.
New release posted...
Downloads:
twrp-3.5.1_9-0-T290XXU3BUB2-20210330.tar.md5
twrp-3.5.1_9-0-T290XXU3BUB2-20210330.img
Change Log:
v3.5.1_9-0: (2021-03-30)
Updated to T290XXU3BUB2 posted kernel source.
Updated to TWRP 3.5.1 release built from android-9.0 branch.
Do we need to update the underlying stock ROM first if TWRP is already installed? Or is it sufficient to flash TWRP from the existing TWRP?
Heeni said:
Do we need to update the underlying stock ROM first if TWRP is already installed? Or is it sufficient to flash TWRP from the existing TWRP?
Click to expand...
Click to collapse
You can just flash the new .img file from an existing TWRP install. The version of the kernel is only important if you're using Magisk (which boots through the recovery partition).
Thanks. That was easy. As far as I can tell at this point, it all works.
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 OSOnce 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?