[Recovery] Official TWRP for the Galaxy Tab A 10.1 (2016) with S-Pen (gtanotexl) - Samsung Galaxy Tab A series ROMs, Kernels, Recover

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?

Related

[How to]Flash latest stock, twrp and root SM-G531F Galaxy Grand Prime VE

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

[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][ROOT] TWRP 3.1.1-1 Galaxy J7 Prime SM-G610F (2016)

Unofficial release -TWRP recovery for the Samsung Galaxy J7 Prime SM-G610F/DS - Exynos 7870 Octa. Should also work for the SM-G610M/Y
{
"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.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Current status: BETA.
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source (kernel AQC4)
system Image backup and flashing support
NTFS support
F2FS support >> To be added
Twrp app support
Micro SD card >> Not working.
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
IT'S ADVISABLE TO BACK UP ANY PERSONAL FILES.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
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 VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.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.
Download:
twrp_3.1.1-1_sm-g610f_5617
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
ashyx said:
Unofficial release -TWRP recovery for the Samsung Galaxy J7 Prime SM-G610F/DS - Exynos 7870 Octa. Should also work for the SM-G610M/Y
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Current status: ALPHA(Untested)
I don't own this device so this build is currently untested. It may boot, it may not. If there are issues I would appreciate proper details and if possible the recovery log which can be found under ADVANCED/SAVE LOG.
I always advise having the stock firmware to hand just in case.
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
system Image backup and flashing support
NTFS support
F2FS support >> To be added
Twrp app support
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
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 VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.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.
Download:
twrp_3.1.1-1_sm-g610f_5617
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
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
No meu j7 prime G610F twrp v3.1.1.1 não funcionou travou fiz tudo Serto mas mesmo assim não funcionou
Sent from my SM-G610F using XDA-Developers Legacy app
gean vilharva said:
No meu j7 prime G610F twrp v3.1.1.1 não funcionou travou fiz tudo Serto mas mesmo assim não funcionou
Sent from my SM-G610F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Please don't quote the entire OP.
I don't speask Portuguese, but from what I can make out you are saying TWRP doesn't boot?
Can I ask which firmware build your device is on? You should be on at least AQC4.
Can you try this version?
https://www.androidfilehost.com/?fid=673368273298961224
.
tried this touch is not working
Ephesis said:
tried this touch is not working
Click to expand...
Click to collapse
Can you tell me which version is working, the one in the OP or the one above. I will fix the touch.
Touch is not working
Can you tell me which version is working, the one in the OP or the one above. I will fix the touch.
Click to expand...
Click to collapse
both is working on me but the touch on both is not working.
Ephesis said:
both is working on me but the touch on both is not working.
Click to expand...
Click to collapse
Ah right so the guy in the first post was complaining about touch not that it didn't boot.
Can I ask your firmware version your device is running?
ashyx said:
Ah right so the guy in the first post was complaining about touch not that it didn't boot.
Can I ask your firmware version your device is running?
Click to expand...
Click to collapse
Google Translate TR> ENG
______________________
Hello there.
The touch does not work when I load TWRP with ODIN. TWRP stays on the first screen.
I can not assign a screen image because the message can not count. I sent the information with a private message that you did not want. I hope it helps.
Good luck with. Good work.
ah right so the guy in the first post was complaining about touch not that it didn't boot.
Can i ask your firmware version your device is running?
Click to expand...
Click to collapse
j7-g610f
g610fddu1api9
Ephesis said:
j7-g610f
g610fddu1api9
Click to expand...
Click to collapse
The kernel is based on AQC4, so I'm guessing this could be the issue?
Wonder if anyone using AQC4 firmware could confirm?
Ephesis said:
j7-g610f
g610fddu1api9
Click to expand...
Click to collapse
havananyx said:
Google Translate TR> ENG
______________________
Hello there.
The touch does not work when I load TWRP with ODIN. TWRP stays on the first screen.
I can not assign a screen image because the message can not count. I sent the information with a private message that you did not want. I hope it helps.
Good luck with. Good work.
Click to expand...
Click to collapse
Hopefully this fixes the touch issue: https://www.androidfilehost.com/?fid=961840155545571773
.
ashyx said:
Hopefully this fixes the touch issue: https://www.androidfilehost.com/?fid=961840155545571773
.
Click to expand...
Click to collapse
Touch is working bro thank you. awsome work
ashyx said:
Hopefully this fixes the touch issue: https://www.androidfilehost.com/?fid=961840155545571773
.
Click to expand...
Click to collapse
The Touch issue is fixed but the sd card mount bug is still there ..!
jagopk said:
The Touch issue is fixed but the sd card mount bug is still there ..!
Click to expand...
Click to collapse
I intend to fix that.
Can you do me a favour? Could you install DISKINFO from play store. Open the app then tap SDCARD. Could you post a screen shot making sure I can see PARTITION NAME and DEVICE.
Thanks.
ashyx said:
I intend to fix that.
Can you do me a favour? Could you install DISKINFO from play store. Open the app then tap SDCARD. Could you post a screen shot making sure I can see PARTITION NAME and DEVICE.
Thanks.
Click to expand...
Click to collapse
Sent from my SM-G610F using XDA Labs
@ashyx Thought I'm not rooted. But I can help u with this kind of things
Sent from my SM-G610F using XDA Labs
Elanza_48 said:
Sent from my SM-G610F using XDA Labs
Click to expand...
Click to collapse
Many thanks for that! Even though you are not using it you're the only one willing to assist.
Anyway based on your post I have made some changes. Could someone test this out and see if it fixes the SDcard mounting issue?
https://www.androidfilehost.com/?fid=961840155545572469
.
@ashyx Do one need to flash SuperSU if he flashes the dm variety and encryption disabled patched kernel ??
Sent from my SM-G610F using XDA Labs
Elanza_48 said:
@ashyx Do one need to flash SuperSU if he flashes the dm variety and encryption disabled patched kernel ??
Click to expand...
Click to collapse
No need to flash supersu unless you wish to root.
Which kernel are you referring to? There is no need to flash any kernel.

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note8 Exynos

{
"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"
}
Official TWRP 3.6.1-* For Galaxy Note8 Exynos​Only for exynos variants - N950F (Single SIM: Europe, Australia); N950FD (Global Dual SIM: Europe, LATAM, Brazil; Australia); N950N (South Korea)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery 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.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
https://twrp.me/samsung/samsunggalaxynote8.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
Device tree - https://github.com/TeamWin/android_device_samsung_greatlte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal8895/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
No Download. Img file?
corsicanu said:
TWRP
Click to expand...
Click to collapse
Well done mate
Benny100 said:
No Download. Img file?
Click to expand...
Click to collapse
Its directly in the github link
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Benny100 said:
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Click to expand...
Click to collapse
Did you tried taping on Assets?
Found and is working Thx!...
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
tabish84 said:
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
Click to expand...
Click to collapse
datafix is for oreo issues where twrp could not properly access internal storage.
format is if you come from stock rom and still have encrypted storage.
Very nice start of the Note 8 Exy journey Bro ?
It is a big pleasure to see U around N8 development!
I am really excited now for the nearest few months and Your 'crazy' ideas which always bring some goodies ?
Thx for Ur efforts and good luck! ?
Works great thank you.
Dev Base August
Sent from my SM-N950F using XDA Labs
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Pinan said:
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Click to expand...
Click to collapse
im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
bober10113 said:
1. im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
2. did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
Click to expand...
Click to collapse
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Pinan said:
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Click to expand...
Click to collapse
i could extract it but u can basically get it from unziping stock.(see link below)
since we are on the n950n, I'm almost sure repulsa rom didnt update it because mostly all roms that might include the BL will have mainly the F/DS bootloader, most dont even update it though.
latest BL would be U3. might be a good idea to update cp(modem) while you are at it too, so grab latest stock firmware and extract both from:
https://samsung-firmware.org/model/SM-N950N/
if download is slow, i can provide these 2 files in a few minutes because package is so big just to get them smaller files.
so only put bl and cp in odin and at least you will be on the latest stuff. dont know what is taking so long for BL U4 to arrive for our korean n950ns....
edit
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
bober10113 said:
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
Click to expand...
Click to collapse
Thank you very much. Most kind of you. :good:
Yes. I've used SamFirm before. Faster indeed.
@ bober10113.
All's well after new CP and BL. no more "Recovery is not seandroid enforcing".
Thanks again.
Good job mate :good:
Really glad we have this dev around. Will flash shortly

Categories

Resources