Hi,
today i soft bricked my Note 3 because i tried to install CWM Recovery with Reactivation Lock on.
Now it shows a yellow triangle and says "Custom binary blocked by Reactivation Lock" and under that: "Secure Fail: Recovery"
I read that i can go back flashing the original stock firmware but i dont have any idea what my product code/csc is.
On the package it says ART code: SM-N9005ZWENEE
The Booklets in the package are printed in Swedish/Finish
Is there any help or do i have to send it back to Samsung?
Thanks in advance
Chris
hexacetat said:
Hi,
today i soft bricked my Note 3 because i tried to install CWM Recovery with Reactivation Lock on.
Now it shows a yellow triangle and says "Custom binary blocked by Reactivation Lock" and under that: "Secure Fail: Recovery"
I read that i can go back flashing the original stock firmware but i dont have any idea what my product code/csc is.
On the package it says ART code: SM-N9005ZWENEE
The Booklets in the package are printed in Swedish/Finish
Is there any help or do i have to send it back to Samsung?
Thanks in advance
Chris
Click to expand...
Click to collapse
No better way on Earth to welcome you on XDA than a soft brick.
Long story short:
0. I hope you've learned your lesson. READ, READ, THEN WHEN YOU'RE SURE THAT YOU'LL MANAGE, READ SOME MORE.
1. You need your cable and a PC, on the PC you need the latest Samsung USB drivers. You can obtain them most easily by downloading Samsung Kies, it will install the drivers for you.
2. Download, for example, this: https://mega.co.nz/#!Ld03nbgB!N5xbTBnOKrwKmsalRrmLdBY-RF8-01YbNk2QpQEcj1k + Odin (for example, from here http://www74.zippyshare.com/v/18196321/file.html )
3. Unzip the file somewhere easily accessible.
4. Turn the phone off and put it in download mode (hold simultaneously Vol Down + Home Button + Power button), until you see that big yellow triangle and some Samsung nonsense about custom OS harming your phone. Press Vol Up to confirm you want to do it.
5. Unzip Odin somewhere, then start Odin 3.07.
6. Plug the phone to the PC with the cable.
7. Odin should put out a message "Added !!"
8. Click on AP and find the .tar.md5 file you extracted in step 3, and click Open.
9. Odin will process the file and when it puts out the message "Leave CS..." see if only F. Reset Time and Auto Reboot are checked. NOTHING else. And THEN click Start.
10. After the operation finishes and your phone reboots, perform a Factory reset.
11. Go on with rooting and CWM, but check the Reactivation lock.
Good luck.
7.
sirobelec said:
No better way on Earth to welcome you on XDA than a soft brick.
Long story short:
0. I hope you've learned your lesson. READ, READ, THEN WHEN YOU'RE SURE THAT YOU'LL MANAGE, READ SOME MORE.
1. You need your cable and a PC, on the PC you need the latest Samsung USB drivers. You can obtain them most easily by downloading Samsung Kies, it will install the drivers for you.
2. Download, for example, this:XXX + Odin (for example, from here XXXX )
3. Unzip the file somewhere easily accessible.
4. Turn the phone off and put it in download mode (hold simultaneously Vol Down + Home Button + Power button), until you see that big yellow triangle and some Samsung nonsense about custom OS harming your phone. Press Vol Up to confirm you want to do it.
5. Unzip Odin somewhere, then start Odin 3.07.
6. Plug the phone to the PC with the cable.
7. Odin should put out a message "Added !!"
8. Click on AP and find the .tar.md5 file you extracted in step 3, and click Open.
9. Odin will process the file and when it puts out the message "Leave CS..." see if only F. Reset Time and Auto Reboot are checked. NOTHING else. And THEN click Start.
10. After the operation finishes and your phone reboots, perform a Factory reset.
11. Go on with rooting and CWM, but check the Reactivation lock.
Good luck.
7.
Click to expand...
Click to collapse
Thank you verry much.
I had a galaxy s and a note 2 rooted and with custom rom but still this didnt prepare me for this knox **** :/
Still you are right, i was way to carelessle for such an expensive phone.
The Android Version you supplied is UK branded, shure this will work on my phone?
I know i have 4.4.2 on the phone, the version that came out before the latests big patch.
Sorry but i dont want to flash the wrong things even further.
Regards
Chris
OMG,
Flashed it and everything is working perfectly again. BIG Thx mate, supply me with your paypal id and ill invite you for some beers!
THANKS
hexacetat said:
OMG,
Flashed it and everything is working perfectly again. BIG Thx mate, supply me with your paypal id and ill invite you for some beers!
THANKS
Click to expand...
Click to collapse
Support the devs that make unbricking, flashing, etc. possible.
And have fun with the Nope 3, the ugliest phone on Earth, but still I wouldn't change it for anything but (probably) a Note 4 with Exynos 5433.
Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.
Thanks man, had the same issue. I figured it might be something to do with booting int OS. Sure enough with 6.0.1 EPK2 rom you MUST load into boot recovery right after flashing TWRP as you stated.
Something went wrong with my OTA update of EPK2 and it started to bootloop( 2 vibrates upon restart and then random amount of bootloops, and then random, soon-coming freeze upon loading in OS and continuing boot-looping) sometime after the update. I erased most of the old stuff via TWRP reinstalled EPK2 bootloader separately and then flashed EPK2 rom and it seems to be OK so far (knock on wood). We'll see hopefully it's not hardware issues like many people were reporting with bootlooping.
Can't you just uncheck the Odin option to reboot instead of the frantic battery pull?
Just wondering, as I'm going to do this later- thanks!
Steven.RN
Followup: Yep. Slip over to the options tab in Odin and uncheck "auto reboot". After Odin flashes TWRP, (the bar is all the way across the download screen, and the Odin Log says "succcess") go ahead, disconnect the phone from USB. Do your battery pull, replace battery. Close up the phone, then hit Volume up, home, and power at the same time- Bang! TWRP screen.
Further note: first time I did this flash, it didn't work, it just stopped in it's tracks. Then I realized I had to enable "developer mode" by clicking on the build number in the "About phone" sections in settings 5 times, going into Developer mode (the new option will present itself in the menu on settings), then: enable OEM unlock and USB debugging. Odin will flash TWRP just fine after that. (Duh on me!)
planetjeff said:
Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.
Click to expand...
Click to collapse
thanks for the info, might give it a shot tonight. you have a link to the software update so i can load it with odin?
Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?
Charlie Rock said:
Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?
Click to expand...
Click to collapse
sammobile.com
Sent from my SM-N910T using Tapatalk
Hi.
New to all this and haven't a clue due to recent circumstances.
My lad, for some unknown reason to me, decided to install team win recovery as a way of trying to clean up his galaxy s 8 phone. He's wiped the OS!! Twr starts but when pressing recovery, it says no os.
I'd never heard of it before and haven't a clue how to use it.
So, after some googling, found out the basics and as I say, when pressing recovery or install or restart, it says no os so I presume he's wiped it.
Spoke to Samsung. They say they can reinstall the is if the rom is ok? I presume it is.
Think they can fix it? I haven't a clue and looking at threads on here about installing ROMs, still gobbledegook to me!
Thanks
smiffie71 said:
Hi.
New to all this and haven't a clue due to recent circumstances.
My lad, for some unknown reason to me, decided to install team win recovery as a way of trying to clean up his galaxy s 8 phone. He's wiped the OS!! Twr starts but when pressing recovery, it says no os.
I'd never heard of it before and haven't a clue how to use it.
So, after some googling, found out the basics and as I say, when pressing recovery or install or restart, it says no os so I presume he's wiped it.
Spoke to Samsung. They say they can reinstall the is if the rom is ok? I presume it is.
Think they can fix it? I haven't a clue and looking at threads on here about installing ROMs, still gobbledegook to me!
Thanks
Click to expand...
Click to collapse
It seems that you're not that familiar with TWRP, and i think you wipe off your system without any idea.
Try to do these steps;
MAKE SURE TO INSTALL these drivers first to your PC or latop before proceeding.
Samsung Drivers
1. download your stock firmware using SamFirm. If you're unsure of your model, look at the back of your phone. Mine is SM-G950FD. its important that you will download your correct firmware to avoid any issues with your network bands
2. download the latest ODIN app
3. extract the downloaded stock firmware. you should be able to get the following files: BL, AP, CP, CSC
4. Extract Odin and open it (or run as admin).
5. Locate each files with corresponding file name BL, AP, CP, CSC on their respective locations. BL = BL, AP = AP, and so on. MAKE sure that you select the correct files.
6. if your phone is on boot loop (power cycling or stuck at samsung logo), force close it by pressing volume down + power button for 10 seconds. If it is not on boot loop, go to the next step
7. go to download mode by pressing volume down + bixby button + power button. you should be able to see a blue screen with text like this.
8. plug in your cable from your PC to your phone, and wait for the ID:COM to turn blue. that means you are ready.
9. press start and wait for the process to complete.
10. once your device gets booted, your're good to go with your fresh phone.
Note: Reboot may take a while. try to force close it (step 6) and reboot again.
Thanks for the advice.
I've installed and run SamFirm.
Put the model in which is smg950f. Region UK.
In 'Phone' I've put Samsung galaxy S8, I've tried Samsung, S8, Samsung S8, galaxy S8 but I get the same error: please specify PDA, CSC and phone version or use auto method.
Any help appreciated. Thanks
There are lots of root and recovery guides here, so why am I posting this? Well, because I tried them, and they either didn't work or were outdated. Also, the install instructions on Lineage OS's site flat out wouldn't work. So here's how I did it!
These instructions are for Windows users, and uses Odin not Heimdall. I'm using Windows 10 Pro. I can't guarantee that it will work on other versions, but I can't see why it wouldn't. YMMV on other versions. I tried Heimdall and no matter what I did, I could not get it to flash anything to my tablet. After much google-fu, I found several people saying Heimdall is broken. I don't know if it is, but it wouldn't work for my on Windows or on Debian linux. So this install uses Odin, which was super easy and I wished I'd have done it in the first place and saved a ton of time and frustration messing around.
For those of you that know what you're doing already, here's the short version:
Enable OEM Unlock in the Developer settings of your stock Samsung OS.
Download TWRP recovery image (the .img.tar version, not the .img version), Lineage OS zip, Lineage Add-on SU zip, Gapps, and Odin (latest versions of all - links are below in the more detailed instructions)
Make sure your stock OS tablet can be seen by your PC - you can copy files back and forth between them. Copy over the Lineage OS, Add-on SU, and Gapps files to your tablet's SD card.
Boot your tablet into Download Mode (Home + Power + Volume Down), tap Vol Up to accept the warning message.
Open Odin on your PC, then plug in your tablet to the PC, note the green COM port number.
Open the Options tab of Odin and make sure the ONLY option checked is the F. Reset Time option. (You don't want it to auto-reboot, and you definitely do NOT want it to re-partition anything).
Click the AP button in Odin and select your TWRP image file. Then click Start in Odin to flash it.
When it's done flashing, disconnect the USB cable from the tablet and exit Download Mode (hold Power + Home + Vol Down), but release them as soon as the screen goes blank and switch to Power + Home + Volume Up so that it boots into recovery. If you miss it, booting into the stock OS will wipe out the TWRP recovery and you'll have to flash it again with Odin.
Once in TWRP recovery, flash the lineage OS file, the add-on-su file, and the gapps file. If asked about encryption, go ahead and tell it to wipe everything out. It's going to wipe your data partition anyway, and if you don't it will screw things up and you'll end up locking TWRP out of the data partition. This can be resolved by rebooting into Recovery and using TWRP to wipe the data partition and then flashing the lineage OS, add-on, and gapps files again.
Once you've flashed lineage OS, add-on-su, and gapps, go ahead and use the on-screen option to wipe the cache and davlik partitions, then reboot into the system.
The first boot will take some time, so go get a beer/coffee/soda and relax. Once it is booted up, it will take you through the Lineage OS setup.
After you complete the setup, you can enable Root on this device by going into Developer Options (under Settings > System > Advanced > Developer Options) and tapping Root Access and selecting from Disabled, Apps Only, ADB Only, Apps and ADB options.
Notes (lessons learned):
Don't flash any of Chainfire's SuperSU packages. They won't work with Lineage OS and will goober up the add-on-su package install. I had to wipe my device and reinstall Lineage from scratch (with the add-on-su and not Chainfire's SuperSU) before mine would work.
Also, I ran into trouble with the encryption of the Data partition. I can't remember the exact sequence of events, but there was a selection when I was installing Lineage for the first time about the encryption of the partition, and apparently I chose wrong. The OS didn't install, it didn't boot right, and TWRP refused to mount the Data partition. I had to reboot into recovery (from recovery) and use TWRP to wipe the Data partition, then reflash lineage OS, add-on-su, and gapps. Then it worked fine.
The LONG Version (more detailed instructions):
Step 1) Gather the files you'll need:
Go to lineage's site and grab the latest OS version. Currently that's v16.0 (Android v9.0 Pie)
https://download.lineageos.org/gts28vewifi
Go to lineage's site and grab the add-on-SU package. Get the arm64 one (second from the top) named addonsu-16.0-arm64-signed.zip
https://download.lineageos.org/extras
Go to Team Win's site and download the twrp package for the Samsung Galaxy Tab S2 8.0 (known as "gts28vewifi" on most of these sites). Be sure to grab the .img.tar version of the file, NOT the .img version.
https://dl.twrp.me/gts28vewifi/
Go to the Odin website and download the latest version of Odin. (At the time of this writing, it is v3.13.1) Note there are links there for multiple versions. I used v3.12.3, but v3.13.1 will work too.
https://odindownload.com/
Go to the OpenGapps.org site and grab the nano version of Gapps. Be sure to select ARM64 for the platform, v9.0 for the Android version, and nano for the variant. (You can choose any variant you like. I used nano. If you know what you're choosing, go for it.)
https://opengapps.org/
Step 2) Enable OEM Unlock on your tablet
On your tablet, go into the Developer settings and enable OEM Unlock. (If you don't have Developer settings in your Settings menu, go to About Tablet and tap the Build Number several times in a row. (As you tap it, it will countdown the number of taps until Developer mode is turned on. Once you've tapped it seven or so times, you can go back to the Settings menu and there will be a new entry there Developer settings. The OEM Unlock is in there, enable it.
Also, back up your tablet contents, because this will wipe your tablet's internal storage (not your SD card though). How you backup is up to you and beyond the scope of this post.
Step 3) Get a good quality/reliable USB-to-micro-USB cable (one came with your tablet).
Using a cheap cable will cause you headaches, and you don't won't to be flashing your recovery partition using a lousy cable.
Step4) Copy the needed files to your tablet's SD card.
In my case, those files were:
lineage-16.0-20190523-nightly-gts28vewifi-signed.zip (517MB)
addonsu-15.1-arm64-signed.zip (1MB)
open_gapps-arm64-9.0-nano-20190529.zip (175MB)
Do not copy it to the tablet's internal storage, as that's gonna get wiped out. You can make a new folder on the SD card or just put it in the root of the card. The simplest way to do this is to have your tablet powered up under the original factory OS and just plug it into your PC with the USB-to-micro-USB cable. It will appear in Windows as a device with two "folders" in it - one for internal storage and one for the SD card. Just drag and drop the files over.
Step 5) Let's flash that recovery! (this is the tricky part):
Make sure your tablet has at least 75% charge before you begin this step. If it doesn't charge it until it does.
Disconnect your tablet from your PC. (unplug the USB cable)
Unzip Odin to a folder - it doesn't really matter where, I put mine on my Desktop. It is handy if you copy the twrp .img.tar file into the Odin folder, but not necessary. When I started Odin, I right-clicked on it and clicked Run As Administrator, then clicked Yes to the windows pop-up. I probably did NOT need to do this, but I didn't want anything getting in the way when it came time to flash the recovery partition of my tablet.
With Odin open, you'll notice that all the blocks across the top are greyed out and blank. That's good because we haven't done anything yet. Notice the left-most small grey block has ID:COM written above it. When you plug in your tablet, it will show what COM port your tablet is on.
Before you plug in your tablet, you need to boot it into Download Mode. To do so, power off the tablet. Then hold the Home button, the Volume Down button, and the Power button at the same time. Within a few seconds, it will boot into a light blue screen that warns you about the dangers you are about to embark upon. Let go of the three buttons you're holding and tap the Volume Up button to let it know that you've got this and you're gonna make this tablet submit to your will! Once you press the Volume Up button, it will go to another light blue screen that says Download and has a message about not turning off the device.
Once you're at that light blue Download screen, you can plug your tablet into your PC with the USB cable. Almost immediately, the ID:COM box should turn green and show a com port number, such as COM4. If you don't get anything give it a minute. If nothing happens, then you may need to install drivers for your tablet. The easy way to do that is to install Samsung's official PC application. It used to be Kies, but now it is called Smart Switch. You can download it here:
https://www.samsung.com/us/support/owners/app/smart-switch
If you need to install Smart Switch, close Odin and unplug the USB from your tablet. Take the tablet out of Download Mode while you take care of business installing Smart Switch. To get the tablet out of Download Mode hold the Home, Volume Down, and Power buttons at the same time for about 10 seconds. When the light blue screen goes away release the buttons or you'll end up back in Download Mode.
After installing Smart Switch, plug in your tablet via USB (make sure it is booted up in the stock OS, not in Download Mode) and make sure your PC detects the tablet and that you can copy files to/from the tablet. When it does, you're ready to disconnect the USB to the tablet and boot the tablet into Download Mode again. Then start Odin, then plug in the USB to the tablet and see if you get a nice green com port showing.
Now that you've got Odin running, the tablet connected, and the com port showing green, you're ready to flash TWRP. Click the AP button in Odin, which will open a standard Windows open-a-file window. Navigate to where you saved the twrp .img.tar file (in my case it was named twrp-3.3.1-0-gts28vewifi.img.tar). Select that file and click OK. Now the Odin window will show the location/filename of your twrp file next to the AP button.
On the left side of the Odin window, click on the Options tab. By default the Auto Reboot and F. Reset Time options will be checked. Uncheck the Auto Reboot option and MAKE SURE THE F. RESET TIME OPTION IS THE ONLY OPTION CHECKED!
Now you're ready to click the Start button which is what flashes the TWRP recovery to your tablet. Go ahead and click Start. The flash will take about 20 seconds or so, and when it is done, the grey blocks above the ID:COM block will be green and will say PASS and have a time under it. (It might have said OK instead of PASS, I can't remember now...) Anyway, you'll know it was OK because its green. If the flash did not work, it will be red and say FAIL! If it fails, make sure you specified the twrp .img.tar file with the AP button and NOT a twrp .img file. (common mistake - .img.tar files are for Odin and .img files are for Heimdall) You can also try rebooting your tablet back into Download Mode, and make sure it is seen by Odin (Odin shows the com port in green).
Assuming that Odin is green and OK, you're ready to unplug the tablet from the PC.
The next step is a little tricky so get your head right before you do it. You're going to reboot the tablet out of Download Mode and directly into Recovery. It is important that you do NOT allow the tablet to boot as normal into the OS. (That's because the stock OS will see that your recovery partition has been changed and it will change it back to the stock recovery and you'd have to start over and flash twrp again.). To make this happen correctly you have to hold the Home + Power +Volume Down at the same time, BUT as soon as the light blue screen goes away, let all three go, then hold Home + Power + Volume Up! So you're basically switching one finger from Volume Down to Volume Up. It may sound tricky, but it really isn't. Just be sure to switch as soon as the light blue screen goes away. Worst case, you miss it and it boots back into the factory OS and you have to do this whole step over again.
Step 6) Time to flash the OS and other goodies!
Once you completed the above step and successfully booted into TWRP recovery, you've completed the tricky parts. The rest is rather simple and done entirely on the tablet.
In TWRP Recovery tap the Install button. Tap the Select Storage button at the bottom. Select MicroSD from the list and tap OK. Now use the folder structure on-screen to navigate to where you saved the lineage OS, add-on-su, and gapps files. If you're smart, you saved them to the root of the SD card and they're already listed on the screen. Tap the Lineage OS file first (in my case it was the lineage-16.0-20190523-nightly-gts28vewifi-signed.zip file). The screen will change and have an Add More Zips button, tap it. Tap the add-on-su file (addonsu-15.1-arm64-signed.zip) and tap Add More Zips, and tap the Gapps file (open_gapps-arm64-9.0-nano-20190529.zip). Now you're ready to flash, so swipe the bar at the bottom to the right. It will start the flash and this will take a few minutes.
Now, I apologize for this next part, I didn't write down exactly what happened... but the gist of it is: the Data partition of my tablet was encrypted (according to TWRP, I hadn't encrypted it via the stock OS), and that messed up the flash. TWRP asked me about the encryption but I was unclear what option to pick. Obviously I picked wrong, because the result was that the flash didn't work, and the Data partition of my tablet was unwritable/unmountable for TWRP and the process blew a bunch of errors. The good part is that the fix was simple. I rebooted from TWRP back into TWRP (tap Reboot then tap Recovery). After rebooting back into TWRP, I tapped Wipe, then Advanced Wipe, checked the Data partition and swiped right. It wiped the encrypted Data partition, and I flashed the lineago OS, add-on-su, and gapps files again. That time it went perfectly. So, if you're reading this now, you may just want to save yourself a little bit of time and before you try to flash the first time, wipe the Data partition. Warning: there's no going back from this, your Data partition will be blank, so be sure to have backed it up before you started down this road, or be ready to proceed with flashing Lineage OS and don't look back.
When the flash process is complete (and error free), go ahead and tap the option to wipe your cache and davlik partitions, then reboot. Both options are on the screen that shows right after the flash process.
Step 7) Let it boot into Lineage OS and enable Root (or not)!
The first boot will take some time, so go get a drink and be patient. It didn't take a whole 10 minutes, but it seemed like it. Once it boots, it will take you through the Lineage/Android setup process. Go ahead through that, then if you want Root, go to Settings > About Tablet and tap the build number seven times, it will do a countdown as you tap to turn on Developer Mode. Hit the back button, tap System > Advanced > Developer Options and scroll down until you find Root Access. Tap it and select from the options: Disabled, Apps Only, ADB Only, Apps and ADB. I suggest Apps Only, as I don't need ADB. YMMV. You now have a rooted Samsung Galaxt Tab S2 with Lineage OS and TWRP. Congrats!
I seem to have painted myself into a corner. After the flashing step apparently I encountered the encryption problem, too. However, no matter what I try I cannot wipe the data partition. I just fails every time. I can get into TWRP. But if I let it try to boot normally I get an error that it needs a factory reset. Even letting it do that doesn't seem to help. Not sure what my next step should be.
EDIT:
Oh wait, I think I got it. What I did in this state was power off (using power button) and choose power off from the menu that pops up. Then I rebooted back into TWRP. Before I tried anything else I chose to format data then wipe data (probably redundant but I don't care). Then I reflashed the 3 packages. That seems to work now...
EDIT 2:
So yeah it did work. Thanks so much! I haven't had a rooted Android device in years. Nice to have that ability back. Wish I could do that to my phone (Verizon S10+).
Will this work for Tab S2 9.7 T813 too? What is the device name of it? gts210vewifi is that correct? So I just have to download the TWRP for gts210vewifi and follow the same guide? What is different to your guide compared to the Lineage OS guide https://wiki.lineageos.org/devices/gts210vewifi/install ?
First of all, thank you very much for this detailed post. Worked like a charm on my client's T713.
The only thing I cannot do is enable encryption, it just reboots the phone. I've tried everything and am running into brick walls. My guy needs to get on work VPN, so encryption is a must. If anyone has an idea, please chime in, I'd be indebted to you.
I keep getting an error 255 and then I read you need to flash a 64 bit rom with an unofficial 64 bit twrp, which I can't find. Anyone know where I can find it or a link? Thanks.
To those having Error 7 while flashing, Open the updater-script file and add TZ.BF.3.0.3-00021 (If you android 6.0) or delete the assert lines altogether.
Man, I followed your instruction word in word and I didn't a single problem upgrading my Tab S2 713 from 7.0 stock to Lineage 16.0. I really appreciate the detailed instruction on how to do this.
Hey there. Found this guide as I recently got a tab s2 and it's very well written, but one step is really hard and it's the whole "boot into recovery from download mode". Whatever I try I can't get it to work.
I assume when you say to hold the Download mode combo (pwr+home+volDown) you mean while the screen is blue with the message "Downloading....". I do this and as soon as the screen turns off I switch to recovery combo (pwr+home+volUp) but I always land at the "Samsung Galaxy Tab S2" screen and it just stays there.
Is there a way to completely turn OFF the tablet from Download mode so I can start into recovery easier? I don't know why it's not working for me tbh. I've tried timing it, tried being a second earlier, later, whatever. Always the same thing. I fear I might be doing something wrong tbh.
(A note: I don't have the "enable unlock OEM" option in my developer options but apparently that means I don't need to enable it. Odin works just fine and I get a pass after 3 seconds. Oh, and my KNOX WARRANTY VOID: went from 0 to 1 so I assume it worked).
EDIT: I want to add my TabS2 is model SM-T815, in case that matters.
One must not click "install TWRP" or it will boot loop into recovery after loading the OS. This is very frustrating, make sure you do not load the TWRP app when installing!
Hope this saves someone time.
Thanks for this post! SUPER helpful.
any guide on how to enable encryption ?
I already format data using twrp 3.2.3.
I did that and now cannot get out of it. UGH
---------- Post added at 06:46 AM ---------- Previous post was at 06:18 AM ----------
avongil911 said:
One must not click "install TWRP" or it will boot loop into recovery after loading the OS. This is very frustrating, make sure you do not load the TWRP app when installing!
Hope this saves someone time.
Click to expand...
Click to collapse
Any way to fix this? I screwed up and installed it.
Hi
Very detailed guide.
I am writing to ask for your help:
I managed to boot into TWRP after ODIN, but it seems i am unable to access micro sd card. There is the option micro sd but i can't select it. As a result, i can't flash lineage.
I click install - select storage -
Internal storage (0mb)
MicroSd (0mb)
USB OTG (0mb)
Do you have any ideas?
I have the lineageos files,gapps to sd card.
Should i proceed with TWRP--> Wipe, then Advanced Wipe-> Data partition -- swipe right, then should i able to access the sd card?
Edit: just tried wipe - advanced wipe - data - and i get Wipe complete: FAILED
could not mount/data and unable to find crypto footer.
Failed to mounf /data (invalid argument)
unable to recreate /data/media folder
Unable to mount storage
Hello. Does the fingerprint scanner work with lineage os ? Thanks in advance!
Edit: yes it does, found it
---------- Post added at 02:48 PM ---------- Previous post was at 01:50 PM ----------
First time i got the failed to mount /data error.
I fixed it like this
Press back at recovery.
=> Wipe
=>advance wipe
=>check data
=>repair or change file system
=>ext2
swipe right
now go back, change file system again to ext4.
Now just install as per OPs instructions and all will be great.
morfeas-dsl- said:
Hello. Does the fingerprint scanner work with lineage os ? Thanks in advance!
Edit: yes it does, found it
---------- Post added at 02:48 PM ---------- Previous post was at 01:50 PM ----------
Mine always fails with too many tries, so I just use a PIN.
Click to expand...
Click to collapse
lloydsw said:
morfeas-dsl- said:
Hello. Does the fingerprint scanner work with lineage os ? Thanks in advance!
Edit: yes it does, found it
---------- Post added at 02:48 PM ---------- Previous post was at 01:50 PM ----------
Mine always fails with too many tries, so I just use a PIN.
Click to expand...
Click to collapse
Try registering your fingerprint from different angles and sideways.
Click to expand...
Click to collapse
So I have one issue, my father was given one by an older gentleman from his work its a brand new looking 713 it has been registered. however, the man does not remember what account nor the perspective password for this tablet, will this work without enabling OEM unlock? if not it goes back to being a fancy paperweight once again.
Sadly, it seem the OEM Unlock is blocked out for me on my S2 with July 2018 as the last update for it, Tried the change date back and auto off steps and such several times but it just does not appear, guess Samsung for even more greedy and blocked that method, so nice of them to make a $600 tablet a paper weight with a 3 year old OS stuck on it..Last time i buy a Samsung device.
morfeas-dsl- said:
lloydsw said:
Try registering your fingerprint from different angles and sideways.
Click to expand...
Click to collapse
Worked! Thanks you!
Click to expand...
Click to collapse
Hello! Could I flash only TWRP and Magisk following this guide? I have Android 7.
I'd like also to know if the tablet would get formatted during these operations thank you in advance!