Develop Bugs

[Q] Installation of Wicked 7 Fails

I have had wicked installed on my phone for a while, but when i install wicked 7 it fails.
What happens is the installation goes fine, however, after I reboot, the system attempts to boot up, but never leaves the first screen, which says Samsung. After a 30seconds or so on that screen it restarts, and automatically goes into Recovery Mod. There when I hit Reboot, I get the warning
"Root access Possibly lost" and it gives me the option to Fix it, or not, I have tried both options, and neither have worked to resolve the issue. I have returned to an older version of Wicked, and it is working fine.
Can someone please help me?

re: Wicket rom issue
this.user said:
I have had wicked installed on my phone for a while, but when i install wicked 7 it fails.
What happens is the installation goes fine, however, after I reboot, the system attempts to boot up, but never leaves the first screen, which says Samsung. After a 30seconds or so on that screen it restarts, and automatically goes into Recovery Mod. There when I hit Reboot, I get the warning
"Root access Possibly lost" and it gives me the option to Fix it, or not, I have tried both options, and neither have worked to resolve the issue. I have returned to an older version of Wicked, and it is working fine.
Can someone please help me?
Click to expand...
Click to collapse
I am almost sure that if you would ODIN flash TWRP v2.5.0.2
and CF-AUTO-ROOT it would solve the issues with your phone.
This method will NOT delete your games, apps or anything else on
your internal or external sdcard if you don't wipe or reset the phone.
Here is what needs to be done as well as the download links you might need:
This is for the T-Mobile Galaxy S4 SGH-M919 Only!
If your phone is NOT a Tmobile Samsung Galaxy S4 M919 then please ignore this post.
If you need official usb drivers to connect your phone to your computer, you can download here.
This is official Samsung USB_Driver_for_Mobile_Phones_v1.5.14.0
The TWRP recovery & the CF-AUTO-ROOT below are specifically designed for the M919 Tmobile S4.
1 - Download the TWRP 2.5.0.2 tar file. Do not extract the files. (This is a Odin compatible TAR file do not extract)
2 - Download Odin 3.07 and extract the files (unless you already have it)
3 - Download CF-Auto-Root and extract the .tar file (unless you already have it)
(This is a Odin compatible TAR file do not extract)
4 - Double click the Odin3 v3.07 file to start Odin. Auto Reboot should be selected by default.
If not, select it and only select Auto Reboot. Make sure re-partition is not selected.
Good luck!

Rooting and flashing ROMS with T-Mobile Note 3 with KitKat

Ok. I have seen several people asking about rooting their T-Mobile Note 3. I am sure there have been posts on how to accomplish this feat. I am going to put out the steps that I took and mention a few other options and my thoughts on those. I hope to make this an all inclusive post for newbies. This method works whether you are on 4.3 or 4.4 BUT you will need to make sure the recovery and ROM you download is for the correct version of android you are using. To make this easier I am going to assume you are already on 4.4 Not everything will be clear but should be able to be easily understood. If there is something you don't understand ask and I am sure people will try to help. That or you can do a google search and probably find the answer a whole lot faster. If you did have a problem and found the solution please post it so others can use your information. I don't have the time at the moment to provide all the links but I will try to update this thread as much as I can.
I am NOT responsible for bricked devices, voided warranties or downloaded virus to your computer.
That being said rooting should be a relatively simple and easy process.
1. Download Odin 3.07 or 3.09 .zip file and install on your computer. (I have found no real difference in between the two when attempting root.) (No link provided just google it.)
2. Download the custom recovery of you choice. (I use and prefer twrp, but some people have had problems flashing ROMs and have had better luck with philz recovery) Below is the link for TWRP. If using 4.4 make sure to download the img.tar file for 2.7. There are other files but you want the one ending in img.tar! http://teamw.in/project/twrp2
3. Open Odin and connect your phone. You need to put your phone into download mode before connecting. Shut your phone off and then turn back on while holding volume down, power and home key. You will see a special screen pop up and a warning. Acknowledge the warning and the connect to the computer. If you don't get a blue bar on the left side of Odin after connecting your phone then you need to update your driver's (google search).
4. Place the .tar file that you downloaded into the PDA(3.07) or AP(3.09) section. Make sure the ONLY boxes on the left are Auto Reboot and F. Reset Time are checked (that should be the default settings)!!
5. Hit the start button. Be advised that Flashing a custom recovery WILL trip Knox.
6. You should the blue bar turn green and say "pass." You know have a custom recovery on your phone and you can disconnect your phone.
At this point you do not have root access, you just have a custom recovery. You now have a choice to make. Do you want your phone rooted or do you want to flash a custom ROM. If you want to flash a custom ROM jump to #8. If you just want root and plan on staying on stock go to #7.
7. Download the latest version of SuperSU file from http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash from your custom recovery. when you restart your phone make sure you can open the SuperSU app. If you cannot go to the play store and reinstall it from there. Congrats!!
8. If you want a custom ROM you need to download the .zip file of that ROM. I would recommend placing it on your EXTERNAL sd card.
9. Go to your custom recovery. There are some things you are going to need to back up prior to Flashing the ROM.
a. Backup your stock ROM, This could save you from some major problems. Back up-system, data and boot-to your EXTERNAL sd card.
b. Backup you EFS files (this can be done via twrp, other wise you will need to do it another way-Google search)
10. Wipe the phone. You want to wipe Data, Cache and Dalvik
11. Flash you custom ROM. Almost every custom ROM comes rooted. You just need to read the info on that ROM
12. Your phone should reboot and you are done!!
Below is some Q&A and helpful tips.
If I upgrade to 4.4 from 4.3 to get a diffent ROM can I switch back? NO
What is "Bricked"? It is a phone that will not boot and only stays on a black screen. Soft Brick is where your phone constantly reboots without opening your ROM.
What is Knox? Google it
Will tripping Knox void my warranty? Probably
How do I get into the recovery? Shut your phone off and then restart while holding the volume up, power and home key. You have to let go as soon as you see the blue letters "Recovery Booting"
There are not that many ROMS for T-mobile can I use an international ROM? Yes! I currently run an international ROM but on most of them you do loose your wifi calling feature. You also need to download a custom T-Mobile Kernel and the Wifi/BT fix.
Should I use CF Auto root or Klingo? I personally don't like the idea of Klingo. Some of the things I have seen they appear to be a little fishy and with them rooting your phone they initially have access to EVERYTHING. CF auto root does not place a custom recovery. You CANNOT flash a custom ROM without a custom recovery. I did it my way because I wanted a custom ROM and just not root.
What about the De La Vega Method? I have no idea and it seemed more work that it was worth. I did not care about tripping Knox
Tips:
Some ROMS will delete your internal memory when flashing as will wiping your phone. That is why I strongly suggest placing the backups and ROMS on your external sd card.
Some ROMS come with an Auroma set up. You will automatically be directed into it when you flash from recovery.
If you are flashing an international ROM make sure that you flash the ROM, T-mobile Kernel and Wifi Fix before choosing the reboot option. If you don't have the t-mobile kernel prior to reboot you will go into a bootloop.
I hope this helps and I will add more and clarify this post in the next few days. I just hope this can help some of you new guys out a little bit and if you found it useful especially if you obtained root please hit the thanks meter.

OK, I deleted all the information here about all the errors I made so that this won't confuse anyone. To summarize my error, I thought I had purchased Android 4.4.2 and flashed the wrong versions. After flashing the correct version, 4.3, everything worked.
The SD-card is not visible in stock recovery and the ADB method won't work without first having root, so that leaves the Odin method.
The Odin method flashes TWRP recovery successfully and when I exited it asked me if I wanted to root the device. I chose 'yes' and it worked for a while then booted into the Android OS. In Android it booted normally, then after I did something which I did not think about and don't recall, a dialog advised me that the GUI portion of the root process still needed to be applied. I allowed it to proceed and now I am rooted with TWRP. I verified the root through ADB by creating a file in the root directory.
Frank

I will try to break this down for you.
1. You need to reflash twrp via Odin to make sure it works correctly since doing auto root.
2. That screen you saw is exactly what you wanted to see. As stated in the OP when you see that screen let go of the buttons and wait, twrp will open shortly. I get the same screen so don't worry. Once you get into twrp and if you need a tutorial on twrp I would suggest looking it up on YouTube.
3. If you reflash the stock ROM via Odin it should fix everything. I am not sure about the partition problem. I will get back if I get some more info.
I would not worry about trying to reflash stock. I would just reflash twrp, boot into recovery and then proceed as listed in the OP.

Frank Westlake said:
**************************************************************************
I found my problem. I think the box, or something, was mislabeled because "About" tells me I have Android 4.3, not 4.4.2. So I flashed the 4.3 version of TWRP and booted right into it. After another reboot to make sure it's stable I'll try rooting again.
Frank
Click to expand...
Click to collapse
Great. Yes, it did not work because 2.7 is written for the new bootloader in 4.4. Are you planning on staying stock jb or planning on flashing a ROM?
sm-n900t: Powered by X-Note V13

FFTony said:
Are you planning on staying stock jb or planning on flashing a ROM?
Click to expand...
Click to collapse
Stock. With root I'm able to customize everything right on the device about as much as the ROM builders. But there are things I cannot do on the device so I'll be keeping an eye on the ROMs to see if anything is attractive.
After I finished this update I refreshed this page and saw that you had been commenting. The screen you saw should be there was also there when I flashed the correct TWRP, and it did move on to TWRP as you said. I'm adding the following paragraph separately so that it's easier for people to find if they need it:
After I had flashed the wrong version of TWRP (4.4 instead of 4.3) it boot-looped to the "SEANDROID NOT ENFORCING" display. To get out of that boot-loop I held the Download Mode keys (HOME-POWER-VOLDOWN) until it rebooted into the first download mode screen, the warning which says you can press VOL-DOWN to boot normally. At that point press VOL-DOWN and it will boot normally. If you press VOL-UP and continue into Download Mode then you will still be in the boot-loop when you reset the device and you will need to reboot again into the Download Mode warning screen and press VOL-DOWN to boot normally.
Thank you very much for your help with this.
Frank

FFTony said:
What about the De La Vega Method? I have no idea and it seemed more work that it was worth.
Click to expand...
Click to collapse
Samsung explains about Root De La Vega here: Samsungknox.com/en/blog/about-root-de-la-vega

Downgrade Note 2 from 4.3 to 4.1.2

Downgrade from 4.3 to 4.1.2. I have done this with 100% Success
If you are having any problem in 4.3 like back and menu buttons ( capacitive buttons) not working or any other issues.
BACKUP everything. (Important)
Turn ON USB Debugging mode and Unknown sources.
First ROOT your phone.
(FOR N7100 Note 2 use CF-Auto root, here is the link.
http://download.chainfire.eu/264/CF-Root/CF-Auto-Root/CF-Auto-Root-t03g-t03gxx-gtn7100.zip
NOTE: Knox and Binary Counters will get Triggered and your Warranty will be VOID.
Donwload CF-Auto root to your computer. Then boot your phone into Download mode. Open Odin. Connect your phone to computer. Click PDA and load CF-Auto root and click Start button. Let the process finish and your phone will reboot. You will see SuperSU icon on your phone).
Open Playstore and Update SuperSU. Open SuperSU and it will give a message to disable KNOX. Click YES/Ok.
Then install Titanium backup root from Playstore. Open it, go to backup/restore tab.
Find,
1.com.sec.enterprise.knox.attestation
2.com.sec.knox.eventsmanager
3.KLMS Agent
4.KNOX
5.Knox Notification Manager
6.KNOX Store
Go to each one of it and Uninstall them.
Next restart your phone.
*VERY IMPORTANT* Now Backup your efs folder by using EFS Professional on you computer. OR any other efs backup App on phone and copy efs backup files to an External sdcard or pc.
(Link: http://d-h.st/Gfo ). Because your imei number will be changed after downgrading. You can easily restore it later.
Now install Mobile Odin Pro from Playstore on your phone. Here is the link.
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
*IMPORTANT* DO NOT flash firmware for downgrading with Computer Odin as it will NOT work and it will FAIL. *ONLY Mobile Odin Pro from Playstore will work.
Copy your 4.1.2 firmware to your phone. Next Open Mobile Odin Pro on your phone and let it download some necessary files from internet.
When done, click on Open file and select the firmware. After loading the firmware scroll down and UNCHECK EverRoot (because it cause problems). Then click on FLASH Firmware.
*IMPORTANT* If your phone get stuck on samsung logo. Go into recovery mode by pressing Home+Power+Volume UP keys together for 15 seconds. Click Factory wipe/data and then Wipe Cache. Then Reboot.
Now check your imei by *#06#. If imei is changed then restore it from EFS Professional.

Thanks!, really helpful.
For those trying to flash firmware you can't use a .zip has to be a .tar.md5

Many thanks! Worked for me on Note 2 LTE N7105. Cheers!

Thanks very good my friend +++

"Click PDA and load CF-Auto root and click Start button. Let the process finish and your phone will reboot."
This part does not work on my GT-N7100.
Followed step by step and it when clicking Start it instantly states Succeeded 0/0 Failed 0/0. After this Play Store said SuperSU was installed on the device, but the application was not installed on the device. I had to try to manually install it from Play Store which worked but obviously it can't do anything because KNOX or something is still blocking it. Yes I was definitely in Download mode.
I've disabled KNOX and removed everything as a device admin except for Samsung Kies. All I want is to go through the supposed simply step by step Cyanogen install and I'm hitting roadblocks at almost every turn. For some reason I can't update to the latest policy when prompted during the installation because either it can't connect to the server or because I am already on the latest policy. Attempted clearing all this and resetting it but to no avail.
EDIT: Weirdly this seems to be working now. Waiting on Get PIT for mapping... Will see how this goes.

This actually worked unbelievably well!
I've got a N7105 on 4.4.2, I downgraded to 4.3 via odin then went on to try downgrading to 4.1.2 via odin which results in errors everytime.
Following these instructions I successfully downgraded to 4.1.2 with no problems and my phone is once again running great, great batt life and error free 4.1.2 roms.
Many Thanks @ Baller231!

Loco007 said:
This actually worked unbelievably well!
I've got a N7105 on 4.4.2, I downgraded to 4.3 via odin then went on to try downgrading to 4.1.2 via odin which results in errors everytime.
Following these instructions I successfully downgraded to 4.1.2 with no problems and my phone is once again running great, great batt life and error free 4.1.2 roms.
Many Thanks @ Baller231!
Click to expand...
Click to collapse
which stock 4.1.2 firmware u are using for gettig great battery life

[Q] Baseband and IMEI unknown after attempted unlock using fast gsm

I bought an AT&T locked stock SGH-i747 - it runs 4.4.2 with baseband I747UCUFNJ1
I tried to unlock it using FastGSM using their USB-tethered method. Their instructions (after some unrelated glitches) were this:
Unfortunately it's not possible to unlock the phone by USB with your current baseband.
It's possible to change the baseband to a supported one and then unlock the phone following these steps:
Code:
1. Install these drivers - http ... files.complexgsm.com ... SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.42.0.exe
2. Power off your phone and reinsert battery
3. Press and hold the volume down button and power button
4. Release them when the download disclaimer shows up
5. Confirm the download mode by using the volume up button
6. Connect the phone to the USB cable
7. Wait until all drivers are installed
8. Download and unzip http ... files.complexgsm.com ... Odin3_Lite_v3.07.zip
9. Start the Odin software
10. Download and unzip http ... files.complexgsm.com ... S3/i747-usa-att/MODEM_I747UCDLK3.zip
11. Click the ‘One Package’ button
12. Select the file you previously downloaded and unpacked MODEM file
13. Press start
14. Wait until the file is uploaded to your phone
15. Disconnect the phone from the USB cable
16. Now you can start the unlocking process by USB
I followed these steps and now have an unknown Baseban and my IMEI is null/null.
When I went back to the original instruction for unblocking by USB and connect the SAMSUNG client, I am stuck at
Code:
READING FIRMWAREWARE VERSION : [FAIL]
FastGSM has stopped talking to me so I can't get help from them to restore my original baseband let alone unlock the phone. Is this a hopeless case? Any suggestions on how to restore the baseband and IMEI?

Are you running a stock ROM and stock recovery?

audit13 said:
Are you running a stock ROM and stock recovery?
Click to expand...
Click to collapse
I'm afraid so. I bought this device on swappa and it appear factory reset, unrooted and AT&T locked. So I presumed it was stock ROM and recovery. Do I need to get another one on there?

You will probably need to flash a custom recovery in order to reflash stock 4.4.2. AT&T never relased a full 4.4.2 firmware, only as an OTA update to a phone's existing firmware.
I suggest loading the Samsung Info App to determine the bootloader on your phone. If the bootloader is the NE4, this may help: http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654

PLEASE post if below works with existing I747UCUFNJ1
I747UCUFNJ1 was just rolled out November 2014 !!!!!!!!!!!!
Try this solution to get you back up and running:
1) Download debrick256.img web address: androidfilehost.com/?fid=23501681358551786
2) Use Win32DiskImager program to flash a sdcard (card can be 16GB or 32GB), then insert sdcard into phone
IF you have a ROM already installed, boot phone an skip to step 5
IF you have a CUSTOM RECOVERY INSTALLED skip to step 5
3) Boot into download mode ( I am sure you are now a VERY VERY HAPPY PERSON NOW )
4) ODIN/flash a custom recovery
5) Download d2att_I747UCUFNE4_bootloader_modem_4.4.2_7-29-14.zip web address: androidfilehost.com/?fid=23578570567720263
6) Transfer d2att_I747UCUFNE4_bootloader_modem_4.4.2_7-29-14.zip to phone (use ADB or if phone boots just use PC)
7) Reboot into RECOVERY
8) Flash d2att_I747UCUFNE4_bootloader_modem_4.4.2_7-29-14.zip
9) Install CM11 / 4.4.4 or higher ROM
Remove sdcard. Enjoy....... your phone is back to normal

audit13 said:
You will probably need to flash a custom recovery in order to reflash stock 4.4.2. AT&T never relased a full 4.4.2 firmware, only as an OTA update to a phone's existing firmware.
I suggest loading the Samsung Info App to determine the bootloader on your phone. If the bootloader is the NE4, this may help: http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
Click to expand...
Click to collapse
Edit: I struggle to follow this advice: I don't have wifi anymore - so connecting to the PlayStore for the installation of apps doesn't work. Would I have to try and download an APK for Samsung Info App and then somehow install that onto my phone?
I have found an APK of the Phone Info App and the bootloader version is given as UCUFNJ1.
Also your above comment seems to state that AT&T never released the 4.4.2 firmware. Does that mean I need to first get to an earlier (released) firmware from where I'll be able to use the OTA update? Sorry - but I'm new to this game, so, still learning. I get the sense that with UCUFNJ1 I can't apply most of the methods for firmware up- and downgrades?

Easiest way to fix the issue would be to flash a custom recovery such as Philz Touch for the d2lte and flash a compatible modem.
This may help: http://forum.xda-developers.com/showpost.php?p=57233161&postcount=135

audit13 said:
Easiest way to fix the issue would be to flash a custom recovery such as Philz Touch for the d2lte and ...
Click to expand...
Click to collapse
I seem to be stumbling at this first step. Odin 3.09 eventually (after 2:05 min) reports PASS when I flash a variety of Philz custom recoveries (I tried philz_touch_6.48.4-d2lte.tar.md5, philz_touch_6.09.something-d2att.tar.md5 and some more). However, I don't seem to be able to get rid of the stock recovery. After rebooting and starting into recovery mode (volup+home+pwr) I always get the
Android system recover <3e>
KOT49H.I747UCUFNJ1
And I can't do anything with that beyond: reboot / apply update from adb/ apply update from ext storage / wipe data&fact reset / wipe cache / apply update from cache.
How can this be so locked down? What am I doing wrong?

I have never used Odin 3.09, only 3.07.
Try this:
open Odin and uncheck everything except f reset time;
attach the phone and flash Philz;
after you see Reset in the status window, remove the USB cable from the phone and remove the battery;
replace the battery and boot into recovery.

Samsung Galaxy Tab S (10.5 Wifi) - "Semi-Rooted" Device Crashes on Reboot

Recently tried to root my Samsung Galaxy Tab S (I am not allowed to post links yet so I'll just say the site is techbeasts)
I believe I went through these instructions and followed them all precisely.
This method also installs SuperSU on my device..
However, I tried checking the root status with Root Checker, and it says "verification failed"
I then checked SuperSU, and it said something along the lines of "binary needs updating". I tried the "normal" method for doing this twice, but it didn't seem to work. There is an option presented in SuperSU to do this through TWRM or CWM, so I tried that option. ( NOTE I do NOT have TWRM or CWM installed)
**Then when I started the tablet, a whole bunch of messages came up saying "unfortunately, ____ stopped" [/B]and a whole bunch of these are there. I'm sure this is a crash.... **
I managed to get the tablet back to semi-working state by using the factory reset from the recovery partition (it's the stock recovery partition). However, the crash-on-reboot problem still persists.
Any help on getting back to working state? I can use the tablet but I cannot restart it as it will crash again (have had to do the factory reset from recovery twice now...)
I should mention that i am trying to:
1) have a rooted tablet
2) Not have these crash-on-reboot issues...
Bharat

Best would be to flash your firmware again with Odin. You can download your firmware on sammobile (see link below).
You will need Odin for this, the correct drivers on your pc and to have USB Debugging on (under Developer options in Settings).
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
Download supersu.zip as well (see link below, you can download 2.46 or 2.49 beta) and put it on the tablet or external sd card.
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
http://www.sammobile.com/firmwares/database/SM-T800/
http://forum.xda-developers.com/showthread.php?t=1538053
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Good luck!

Wow, how to massively over complicate something.
Just install the stock firmware, then look for my build of cf_autoroot in the dev section, flash in ODIN. Done.
If you want to upgrade twrp to the latest version you will find it in the dev section too. This version fixes some of the issues with the official version and has more options.

Hi guys,
TThanks so much for your replies! Complicated or not, anything helps...
I had previously used Odin to flash the rooted firmware to the tablet, so I amn faniline with the software.
Alta1r: looked at the links and it looks like sprue stock firmware. A couple of questions about this procedure:
1) Is it normal that the stock firmware file (as downloaded) is larger than firmware images used to root the tablet?
2) Would using TWRP to flash Supersu onto the tablet root the tablet, even if the stock firmware is installed?
Thanks again guys!!

Not sure what you mean with firmware images to root the tablet. Do you mean a custom rom? Those should be smaller in size yes, as the are usually de bloated.
Maybe you flashed a wrong version if a custom rom for your tablet before, that would give you problems when flashed.
Both my or ashyx's method can be applied on a stock rom. I'm running just stock with root.
@Asynx: I flashed the latest firmware on my T800 this week and twrp didn't stick after the first boot. Tried many versions, also the one you mention in the dev section, but to no avail. Even replaced the recovery in the samsung's tar file and flashed it like that: twrp screen showed up right after the flash, but on next boit it was stock again. Only way to make it stick was to reboot into recovery right after flashing it.
Never had that problem before though on the Tab S (did have it already once on Galaxy S6).
Edit: forgot to mention I hadn't seen there was cf-auto root available for our current firmware. If I knew it would have saved me some time. Could have flashed the recovery with Flashify afterwards.

Apologies I am still getting used to the lingo with this stuff
Have done some stuff with Linux and some tweaking in Windows as well, so figured this shouldn't be too bad...
@Alta1r: so the process you describe is what you said, flashing the stock ROM and then root it afterwards...
Will try this process and report results here
(aside: I think the tablet was working fine after flashing with CF autoroot ROM -- is that the right word? -- what I think ruined it was when I told Supersu to try updating its binary through TWRP or CWM....which isn't yet on my tablet)

Alta1r said:
Only way to make it stick was to reboot into recovery right after flashing it.
Click to expand...
Click to collapse
It seems since lollipop this has to be done if flashing over stock recovery or it will be replaced at boot with stock.
Twrp will patch the recovery install script at first boot.

Sooooo...
First off, thanks for the "luck wishing"
I decided to try the method of @Alta1r.
@ashyx - I tried the CF-autoroot thing before (this was first attempt at getting a rooted tablet), and this didn't work for me. So I wanted something a bit more "hands on".
This is procedure I followed and worked for me (as of this post):
1) Before I began, I accidentally went into recovery mode instead of download mode. So I had to restart the tablet *gulp*
....yet I was able to restart just fine (no crashed as mentioned in my first post). I think this ~might~ have something to do with the fact that I downgraded the version of supersu that was "updated" through Google Play, but I'm not really sure...
2) Downloaded all relevant files.
3) Flashed firmware for tablet as instructed:
Alta1r said:
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Click to expand...
Click to collapse
Result was that tablet booted just fine!
Made sure that a few apps worked OK, and also rebooted the tablet a few times to make sure it was stable
(this is a linux based system, not Windows, but I still like reboot tests for stability checking...)
4) Next I did the TWRP flash through Odin:
Alta1r said:
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Click to expand...
Click to collapse
TWRP flashed fine. But then....
5) Tried to boot into TWRP recovery:
Alta1r said:
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Click to expand...
Click to collapse
As predicted, Alta1r, the TWRP didn't flash properly. I got an error on the stock recovery saying:
"Error message is "E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)"
So I tried your odin + reboot trick as above, and this booted into TWRP recovery.
6) Then I flashed supersu.zip (had kept on microSD card that is in tablet).
Andddddd.....
Root checkers says all good
Thanks so much for the help guys. I wrote the procedure above for anyone else who attempt this method!

bsquared938 said:
Root checkers says all good
Thanks so much for the help guys. I wrote the procedure above for anyone else who attempt this method!
Click to expand...
Click to collapse
Glad to hear all went well, and by the looks of it had fun doing it.

Although computer/device problems can get me agitated, I still have fun in the end
Not sure if I can ask this here, but two other slight issues after the rooting:
1) Upon rebooting the tablet, I always get the message "android is upgrading", even if I didn't touch any apps through Titanium Backup or other root-only apps that are meant to remove pre-installed applications.
Is this an issue? And if so, is there a way to get rid of this?
2) I am able to uninstall/remove apps with Titanium Backup (freezing them isn't possible without the paid version of the app), but I am not able to restore them. I made a full backup before I started to uninstall stuff. I put on USB debugging mode in developer options, but still I cannot put apps back. Any thoughts on this?
Thanks again!
Bharat

I wouldn't worry about the upgrading message, most get that.
AFAIK TB requires a kernel that can be set permissive to fully function.
If you want the ability to remove and restore apps use system app remover (root)

ashyx said:
I wouldn't worry about the upgrading message, most get that.
Click to expand...
Click to collapse
Okay thanks, I will not worry about that upgrading message for now...
ashyx said:
AFAIK TB requires a kernel that can be set permissive to fully function.
If you want the ability to remove and restore apps use system app remover (root)
Click to expand...
Click to collapse
Is there a way to set this up? Even System App Remover does not let me reinstall stuff...
(I don't plan to ever use any of the apps I am removing, but I would like this feature for "sanity" purposes...)

bsquared938 said:
Okay thanks, I will not worry about that upgrading message for now...
Is there a way to set this up? Even System App Remover does not let me reinstall stuff...
(I don't plan to ever use any of the apps I am removing, but I would like this feature for "sanity" purposes...)
Click to expand...
Click to collapse
Are you sure you have full root?

ashyx said:
Are you sure you have full root?
Click to expand...
Click to collapse
Yes I am sure I have full root.
I used root checker to check if I have full root access and it comes back green (to say root access is good).
(Just checked again now before posting this...)
Using either Titanium Backup and Root App Deleter, I am unable to restore deleted apps...
I have enabled USB debugging in the developer tools, as instructed to by Titanium Backup....
I read something about the "mount namespace separation" in supersu, I might try to toggle that option to see if it helps this situation.

Root app deleter? Is that system app remover?
Also what is the error when you try to restore with it?

ashyx said:
Root app deleter? Is that system app remover?
Also what is the error when you try to restore with it?
Click to expand...
Click to collapse
App is called System App Remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
It tries to restore the app, and after about half a second it just says "try again if it fails" with a "yes" button to be selected...

bsquared938 said:
App is called System App Remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
It tries to restore the app, and after about half a second it just says "try again if it fails" with a "yes" button to be selected...
Click to expand...
Click to collapse
That doesn't mean it doesnt restore. It says that every time iirc. Check in system apps to see if it restores.

ashyx said:
That doesn't mean it doesnt restore. It says that every time iirc. Check in system apps to see if it restores.
Click to expand...
Click to collapse
Okay I'm just going to say exact issue...
I deleted calendar storage, thinking that it's part of Samsung's calendar app (when in fact it is used by all calendar apps).
So now Google Calendar doesn't show me my calendar....and I'm trying to restore calendar storage, but it's not restoring
(had previously deleted through System App Remover, but now can't get it back)
Edit: I uninstalled and reinstalled Google Calendar, and that seemed to bring back my calendar.....
Sorry to cause you this trouble, I guess I panicked too early...
But will still be careful of what I remove...

Alta1r said:
Best would be to flash your firmware again with Odin. You can download your firmware on sammobile (see link below).
You will need Odin for this, the correct drivers on your pc and to have USB Debugging on (under Developer options in Settings).
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
Download supersu.zip as well (see link below, you can download 2.46 or 2.49 beta) and put it on the tablet or external sd card.
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
http://www.sammobile.com/firmwares/database/SM-T800/
http://forum.xda-developers.com/showthread.php?t=1538053
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Good luck!
Click to expand...
Click to collapse
worked for me thx :good: