Develop Bugs

[Q] Need some help. What should I do next?

I've had my I9192 for about 2 months. I updated it right after receiving it, and rooted it using Kingo. Everything was working great until I received the software update. I installed the update a couple of days ago and lost root. I tried Kingo again, but I'm getting the Samsung Security (knox) message that it was blocking it. Even though I never installed Knox, it must be running in the background.
I've done some reading since on Kingo, Knox, and updating while rooting. I have now come to the realization that my warranty is probably void, my phone will no longer get official updates, and there is no Santa Claus.
In researching the problem, I found some reference to download mode. and the Knox Kernel lock. When I start my phone in download mode, this is what it shows:
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0 (I think this and the next one are good)
Knox Warranty Void: 0x0
CSB-Config-LSB: 0x30 (I don't know what this is)
Write Protection: Enabled
Can anyone confirm my assumptions? I just want to get back to my original state before updating a few days ago. Original FW with root capability. I'm ok with resetting the phone and reinstalling if necessary.
If I screwed the pooch on this one, then I guess it's time to go CFW route to get to root.
Thanks for any input.

Once you got a fw with Knox you can't go back.
And yes, 0x0 is good but if you flash a kernel for root you will get 0x1..
Sent from my GT-I9195 using xda app-developers app

mnezo said:
Once you got a fw with Knox you can't go back.
And yes, 0x0 is good but if you flash a kernel for root you will get 0x1..
Sent from my GT-I9195 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the input. Since, I am at 0x0, will I still get fw updates?
As I mentioned, I thought you had to be a 0x1 to be excluded from official updates. Or does the fact the System Status is now Custom, exclude me from those updates?

Snotick said:
Thanks for the input. Since, I am at 0x0, will I still get fw updates?
As I mentioned, I thought you had to be a 0x1 to be excluded from official updates. Or does the fact the System Status is now Custom, exclude me from those updates?
Click to expand...
Click to collapse
Yes. As your System Status is now set to Custom then you can not receive official updates by OTA.

GeoDum said:
Yes. As your System Status is now set to Custom then you can not receive official updates by OTA.
Click to expand...
Click to collapse
Thanks.
I'm still reading conflicting reports about how Samsung is handling all of this. You say I won't receive official updates OTA. Will I be able to side load them via Kies?
I'm also confused about the Knox security. It seems like it is more for people that want to use their phones for work. I don't, and am 99% certain that I never will. Should I even care what my Knox count is?

Snotick said:
Thanks.
I'm still reading conflicting reports about how Samsung is handling all of this. You say I won't receive official updates OTA. Will I be able to side load them via Kies?
I'm also confused about the Knox security. It seems like it is more for people that want to use their phones for work. I don't, and am 99% certain that I never will. Should I even care what my Knox count is?
Click to expand...
Click to collapse
In some countries Knox warranty 0x1 = Void warranty So yes sometimes u should care about Knox
Read more here

SilviuMik said:
In some countries Knox warranty 0x1 = Void warranty So yes sometimes u should care about Knox
Read more here
Click to expand...
Click to collapse
Sorry, I should have mentioned that I am in the U.S.
At this point, I would trade my warranty for a rooted phone running stock fw going forward. As it stands now, I can't root (at least not the with one click) and I won't be updating fw going forward. Seems like a double whammy.

Snotick said:
I've had my I9192 for about 2 months. I updated it right after receiving it, and rooted it using Kingo. Everything was working great until I received the software update. I installed the update a couple of days ago and lost root. I tried Kingo again, but I'm getting the Samsung Security (knox) message that it was blocking it. Even though I never installed Knox, it must be running in the background.
I've done some reading since on Kingo, Knox, and updating while rooting. I have now come to the realization that my warranty is probably void, my phone will no longer get official updates, and there is no Santa Claus.
In researching the problem, I found some reference to download mode. and the Knox Kernel lock. When I start my phone in download mode, this is what it shows:
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0 (I think this and the next one are good)
Knox Warranty Void: 0x0
CSB-Config-LSB: 0x30 (I don't know what this is)
Write Protection: Enabled
Can anyone confirm my assumptions? I just want to get back to my original state before updating a few days ago. Original FW with root capability. I'm ok with resetting the phone and reinstalling if necessary.
If I screwed the pooch on this one, then I guess it's time to go CFW route to get to root.
Thanks for any input.
Click to expand...
Click to collapse
Hi man many Questions but i think i can help you.
If made nearly the same like you the only differnce i flash the new upadte by my self via Odin.
So lets start step by Step:
1. You can go back to your old Firmeware with root is possible as befor! For that you must search your Firmeware via I-net and flash them via Odin like me. No changes on the Knox flag
2. That Custom stat: Yes you will be able to get OTA by me it Works. You can emulated the Offical state via Wanam Xposed and it will show you too as Offical in the Download mod.
3. Warranty is still in place
Look at my Post on a other Thread: littel Guide from me
There i explain what you must do to get back to your older Firmeware
Happy new Year for you all
Greets
Killer

[Q] Triangleaway? Can't unroot N7100 running Slimkat

Hi everyone, this is my first post on here, though I have read a lot of other threads on this site and just wanted to start by saying thank you to all the helpful people on here.
So, my issue is I have a Note 2 (N7100). I rooted it (using very useful guides from here) and installed the Slimkat custom ROM. I'm now selling the phone but the person interested in buying from me wants the original Samsung stock ROM (unrooted so that he can get the update currently rolling out).
I downloaded the correct official firmware (I'm in Thailand) from sammobile and I've tried using Odin just as instructed here and on many other sites. However it just won't work.
I select the md5 firmware file then and it does it's getting the PIT file and gets to the point where I just have to hit start. But when I do it says it failed and that I need an Odin supported file.
I suspect this is because of previous flashing. When I boot into download mode is says it has a binary count of 2 and that knox was tripped.
I read on here that I could use Triangleaway but that if I mess it up, it's goodbye phone. I know that you can't be held responsible etc etc but I would just like to know can I use Triangleaway on my phone (which is running SlimKat 4.4.2)? It says that you have to be using it with a compatible ROM.
If I use Triangleaway with my phone, following the instructions I've found on here... what are the chances that I'll end up totally permanently bricking my phone?
Provided that I don't do anything stupid and just follow step by step instructions, would it be ok? (yes, I know you can't be held responsible)
And would this solve the issue of Odin not being able to flash the file that seems to work for everyone else?

somewada
If you have better bootlader, than mj5, then tringleaway is not working. about knox. if knox varranty 1 the jor varranty is over
if bootlader mj5 then download original rom www.sammobile.com

Knox counter says warranty void 0x1 then forget about MJ5. You must have tripped with a bootloader above MJ5 therefore no downgrade.
You got to go for the newest firmware to get stock again, even (maybe) got to try indian 4.4.2 AND unrooted status will stay custom, so OTA won't work.
Seems that you pay the price for unconscious or careless flashing. Sad to state this...

Samsung Note 2 LTE (N7105) Stuck at Samsung logo after 4.3 to 4.1.1 downgrade

Hi guys,
I'm new to this forum and I am a beginner so I must apologise in advance for my ignorance.
I was looking to downgrade my Note 2 from 4.3 to 4.1.1 to unlock it, and I found this http://forum.xda-developers.com/showthread.php?t=2612485
I followed the instructions properly. I rooted my 4.3 with CF auto root, and then I tried to flash the 4.1.1 firmware onto my phone.
Now it is stuck at the boot screen, and I'm so shocked because I did everything correctly.
I can still get to "ODIN Mode" by holding volume down, home and power, and it says:
Current Binary: Custom
System Status: Custom
Knox warranty void: 1
What have I done wrong?
Thank you.

nigzy said:
Hi guys,
I'm new to this forum and I am a beginner so I must apologise in advance for my ignorance.
I was looking to downgrade my Note 2 from 4.3 to 4.1.1 to unlock it, and I found this http://forum.xda-developers.com/showthread.php?t=2612485
I followed the instructions properly. I rooted my 4.3 with CF auto root, and then I tried to flash the 4.1.1 firmware onto my phone.
Now it is stuck at the boot screen, and I'm so shocked because I did everything correctly.
I can still get to "ODIN Mode" by holding volume down, home and power, and it says:
Current Binary: Custom
System Status: Custom
Knox warranty void: 1
What have I done wrong?
Thank you.
Click to expand...
Click to collapse
On the first post that you've followed says that "It may or may not work for you" so you only have 50% chance. AFAIK 4.3 firmware has Knox already. Did you flash the 4.1.1 successfully? If yes, maybe Knox is restricting it from booting. If not successfull, maybe the files of your device have been messed up. So you have to flash again your previous rom using Odin. Why don't you try it. Since you already tripped your Knox to 1. Meaning you've already voided your warranty.

asin_punk said:
On the first post that you've followed says that "It may or may not work for you" so you only have 50% chance. AFAIK 4.3 firmware has Knox already. Did you flash the 4.1.1 successfully? If yes, maybe Knox is restricting it from booting. If not successfull, maybe the files of your device have been messed up. So you have to flash again your previous rom using Odin. Why don't you try it. Since you already tripped your Knox to 1. Meaning you've already voided your warranty.
Click to expand...
Click to collapse
Thank you for your reply I flashed the 4.1.1 successfully, but it just wouldn't boot. 4.3 does have Knox but I disabled it when I rooted it.
I flashed 4.3 again, and to my surprise it worked, I'm really grateful mate thanks a lot
What does it mean for me now that I've voided my warranty? I can't update it anymore with Kies?

nigzy said:
Thank you for your reply I flashed the 4.1.1 successfully, but it just wouldn't boot. 4.3 does have Knox but I disabled it when I rooted it.
I flashed 4.3 again, and to my surprise it worked, I'm really grateful mate thanks a lot
What does it mean for me now that I've voided my warranty? I can't update it anymore with Kies?
Click to expand...
Click to collapse
Great! AFAIK you can still update with kies. But you have to unroot your device first using supersu. There are a lot of rumors around there. Some said yes and some says no. Haven't tried it myself before actually. I always use odin. Since you got back to 4.3, what's your next plan? Hehehe.

asin_punk said:
Great! AFAIK you can still update with kies. But you have to unroot your device first using supersu. There are a lot of rumors around there. Some said yes and some says no. Haven't tried it myself before actually. I always use odin. Since you got back to 4.3, what's your next plan? Hehehe.
Click to expand...
Click to collapse
Ok got it, thanks man. I'll probably use Odin from now on too.
Is there currently no way to restore the Knox count? The phone doesn't have warranty anyway but if I can't use Knox enabled software in the future I guess it will be difficult
Since I'm back on 4.3 I'm looking to see if I can unlock my phone somehow, I'm looking to study abroad soon and I need it done, and I can't do it through the official carrier so I'm a bit desperate. What do you reckon I should do?
In the tutorial that I mentioned in my first post, he didn't say that I should factory reset the phone. Shall I try downgrading again and then do the factory reset? Will it help at all? Like it says here: http://www.droidviews.com/how-to-downgrade-firmware-on-samsung-galaxy-devices/2/
Cheers

nigzy said:
Ok got it, thanks man. I'll probably use Odin from now on too.
Is there currently no way to restore the Knox count? The phone doesn't have warranty anyway but if I can't use Knox enabled software in the future I guess it will be difficult
Since I'm back on 4.3 I'm looking to see if I can unlock my phone somehow, I'm looking to study abroad soon and I need it done, and I can't do it through the official carrier so I'm a bit desperate. What do you reckon I should do?
In the tutorial that I mentioned in my first post, he didn't say that I should factory reset the phone. Shall I try downgrading again and then do the factory reset? Will it help at all? Like it says here: http://www.droidviews.com/how-to-downgrade-firmware-on-samsung-galaxy-devices/2/
Cheers
Click to expand...
Click to collapse
Downgrading from Knox-enabled-bootloader to Non-Knoxed-Bootloader may brick your device. Your lucky that it didn't happen on your first try. From what carrier are you locked on? Since your on 4.3 Knox bootloader, maybe you can try other custom rom that depends on your current bootloader. Or try to upgrade to Official 4.4.2 from sammobile then install PhilzTouchRecovery 6.26.6 then root it, then find a custom rom that fits your device and can also unlock your device. Maybe you can ask Dr. Ketan if he has a rom like in this thread http://forum.xda-developers.com/showthread.php?t=2472270 for your device. And I think he can help you with all of your concerns. Cheers!

[Q] Rooting Questions

Hi guys,
I am new to the xda forums and I have been researching about rooting my note 10.1 2014 p600 (WIFI). I have three questions about rooting my device.
1. How would I update my tab with root? I heard you can't get OTA updates.
2. What is the best and safest way to root?
3. How do I get TWRP and is it good?
I haven't installed knox on it yet and I am a beginner to linux and have done research so I know what root is.

dudeian said:
Hi guys,
I am new to the xda forums and I have been researching about rooting my note 10.1 2014 p600 (WIFI). I have three questions about rooting my device.
1. How would I update my tab with root? I heard you can't get OTA updates.
2. What is the best and safest way to root?
3. How do I get TWRP and is it good?
I haven't installed knox on it yet and I am a beginner to linux and have done research so I know what root is.
Click to expand...
Click to collapse
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
1) Download this file https://dl.dropboxusercontent.com/u/11938873/CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip then unzip, you will see this file CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5.
2) Turn Off Tablet, Hold Volume Down + Power. Follow the instructions on the screen to get to download mode (Odin mode).
Rooting Instructions
1.Flash the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file with Odin v3.09 (put in AP slot, don't change any other settings, click start)
2.Let it do its trick! boot up then go to play store download and install supersu in order to update supersu to the latest binary.
3. Boot back into Odin mode and flash TWRP version 2.6.3.3 found here https://goo.im/devs/OpenRecovery/lt03wifiue/
That's all!

buhohitr said:
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
1) Download this file then unzip, you will see this file CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5.
2) Turn Off Tablet, Hold Volume Down + Power. Follow the instructions on the screen to get to download mode (Odin mode).
Rooting Instructions
1.Flash the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file with Odin v3.09 (put in AP slot, don't change any other settings, click start)
2.Let it do its trick! boot up then go to play store download and install supersu in order to update supersu to the latest binary.
3. Boot back into Odin mode and flash TWRP version 2.6.3.3 found here
That's all!
Click to expand...
Click to collapse
Thanks! This is great help.

buhohitr said:
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
Click to expand...
Click to collapse
Knox is just a shortcut to the install link, Does this mean it's not installed or is the shortcut just extras (I don't know how to post screenshots).

dudeian said:
Knox is just a shortcut to the install link, Does this mean it's not installed or is the shortcut just extras (I don't know how to post screenshots).
Click to expand...
Click to collapse
I don't understand what you are saying???
When I said tripped Knox void warranty is that your device detected that you installed unauthorized software which tripped the knox counter. You can see this by boot into download mode (Odin mode) and you should see a line like this:
Warranty bit: 1 (factory is 0x0)
I hope that what you're asking!

buhohitr said:
I don't understand what you are saying???
When I said tripped Knox void warranty is that your device detected that you installed unauthorized software which tripped the knox counter. You can see this by boot into download mode (Odin mode) and you should see a line like this:
Warranty bit: 1 (factory is 0x0)
I hope that what you're asking!
Click to expand...
Click to collapse
Yup.

ok, now i'm getting confused.
my p600 is still on 4.3 jellybean. but from what i read, as long as did not update to kitkat firmware, i can still unroot and reverse the warranty bit bcoz they don't have knox yet. but it'll be too late if i updated to kikat right? btw, i used cf-auto-root.
just weeks ago i rooted my p600 and flashed stock recovery, so now my p600 thinks its stock official firmware, even say so in about device.
i haven't tried unrooting it yet to confirm that i can get warrenty back by flashing back whole stock firmware bcoz i don't want to redo all settings again. but thats the impression i'm geting.
anyhow if i can't really reverse that warranty thing i don't really care anyways. i warranty my stuff better than they do it, and since i think i can still get updates, it bothers me even less if its unreversible. but in the case if i'm right, and i can reverse that warranty bit. maybe one day i'd like to update to kitkat. then what? i'll have to have knox in my system and i can't reverse warranty counter anymore?
is there a way i can update to a custom kikat firmware (one day) and not have knox so i'll still be able to get warranty back?
i kind of realized the dilemma i have here since if i own the device for more than a yr, my warranty wouldn't matter anymore. am i just thinking too much and worrying myself?

kazukiflame said:
ok, now i'm getting confused.
my p600 is still on 4.3 jellybean. but from what i read, as long as did not update to kitkat firmware, i can still unroot and reverse the warranty bit bcoz they don't have knox yet. but it'll be too late if i updated to kikat right? btw, i used cf-auto-root.
just weeks ago i rooted my p600 and flashed stock recovery, so now my p600 thinks its stock official firmware, even say so in about device.
i haven't tried unrooting it yet to confirm that i can get warrenty back by flashing back whole stock firmware bcoz i don't want to redo all settings again. but thats the impression i'm geting.
anyhow if i can't really reverse that warranty thing i don't really care anyways. i warranty my stuff better than they do it, and since i think i can still get updates, it bothers me even less if its unreversible. but in the case if i'm right, and i can reverse that warranty bit. maybe one day i'd like to update to kitkat. then what? i'll have to have knox in my system and i can't reverse warranty counter anymore?
is there a way i can update to a custom kikat firmware (one day) and not have knox so i'll still be able to get warranty back?
i kind of realized the dilemma i have here since if i own the device for more than a yr, my warranty wouldn't matter anymore. am i just thinking too much and worrying myself?
Click to expand...
Click to collapse
Yes you're confused!!. Knox has nothing to do with warranty bit, once this tripped, you can't undo doesn't matter you on 4.3 or 4.4.

I'm a little confused on a few other issues. I have read over 40 pages on another thread here about rooting etc and I couldn't find the answer to a few questions. I've just successfully rooted using the most recent instructions (P600 - CF Auto root) but in earlier instructions (about a year ago) you had to also install the stock recovery file using Odin. Is that a necessary step? Is it needed for OTA updates? Since I've read that OTA updates will unroot and possibly prevent you from rooting at all, is it best to just forget about OTAs and flash up to date files from this site? Is it also prudent to turn off auto updating in the settings.
If I'm not installing custom roms and backed up using Titanium Pro do I really need to install TWRP? Any other benefits other than nandroid? Thanks

jbarr3 said:
I'm a little confused on a few other issues. I have read over 40 pages on another thread here about rooting etc and I couldn't find the answer to a few questions. I've just successfully rooted using the most recent instructions (P600 - CF Auto root) but in earlier instructions (about a year ago) you had to also install the stock recovery file using Odin. Is that a necessary step? Is it needed for OTA updates? Since I've read that OTA updates will unroot and possibly prevent you from rooting at all, is it best to just forget about OTAs and flash up to date files from this site? Is it also prudent to turn off auto updating in the settings.
If I'm not installing custom roms and backed up using Titanium Pro do I really need to install TWRP? Any other benefits other than nandroid? Thanks
Click to expand...
Click to collapse
Once you rooted you can't use OTA update any more. So the easiest going forward is to flash TWRP and use it to flash pre-rooted rom from this site.

Thanks buhohitr
I guess I'm installing TWRP tonight. There are many versions up to 2.8 I think. Which one do you recommend for P600? I've tried searching for "installing TWRP" but there were no obvious hits like there were for rooting. Which is the key thread?
To my first question, I'm assuming that the later root methods automatically installs or leaves the stock recovery as earlier methods needed to load it. Am I right?

jbarr3 said:
I've tried searching for "installing TWRP" but there were no obvious hits like there were for rooting.
Click to expand...
Click to collapse
OK found the thread and I just read the last 55 pages (that took a while) and boy is it scary. So many problems. Touch not accurate, inverted screens, certain versions failing eg 2.7, can't access external SD card, continual looping, booting into the old recovery , OTG cables not working, time zones can't be set properly, some say turn off autoboot in odin and some say don't change default settings etc etc. the list goes on and on. I likened it to a bushfire or tornado. Some houses still stand and some don't and you want to know the silly thing here, I am an experienced computer teacher with a degree in computer science and I've upgraded firmware on over a hundred devices over the years and yet all this rooting and recovery stuff is another world. The rooting process, admittedly, was a piece of cake and the instructions for flashing TWRP seems easy too but after that there seems to be so many problems. So hit and miss.
All i want to do is load TWRP on a P600. I will only load custom ROMs when a new firmware version comes out. Can someone alleviate my fears who has successfully loaded TWRP recently on a P600 using ODIN without massive tweaking to get it going. What version TWRP did you use and did you turn off autoboot or not?
PS Have I posted this in the correct section?

Took the plunge and loaded the latest TWRP 2.8.1 and it worked perfectly except I could only back to the main SD storage and not my extSD. I ended up, as a work around, moving the backup files to the extSD drive and PC.
I think I was worried unnecessarily.

[Q&A] [Root][Port] Cf-Autoroot T700 [Tab S 8.4]

Q&A for [Root][Port] Cf-Autoroot T700 [Tab S 8.4]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

galaxy tab s stuck on battery screen after using the cf-Autoroot
I tried rooting my galaxy tab s 8.4 using the cf-Autoroot method however at the end it said failed. I attempted to restart tablet but it was stuck on download mode, finally after searching forums I found one that explained how to power it off, and it said if I did it I would be golden. Now I have 2 choices battery screen or off. Please help I have the stock firmware but no way to reinstall

Does this root method reset or wipe the device?

@lbert said:
Does this root method reset or wipe the device?
Click to expand...
Click to collapse
Nope just installs supersu and root. You will still have your apps.

cf autorootf
I was just going to say - towelroot won't trip KNOX - at least as it applies to the 705, AND, the tab pro version as well. So I curious why folks would still use CF, if they're concerned about the 0x1 flag.

hillg001 said:
I was just going to say - towelroot won't trip KNOX - at least as it applies to the 705, AND, the tab pro version as well. So I curious why folks would still use CF, if they're concerned about the 0x1 flag.
Click to expand...
Click to collapse
Well no one has tried downgrading to a kernel that towelroot could of worked with. Thought those builds were also old we do not know it if works. But people have claimed they got their tablet replaced(hardware deffect) even if they tripped knox so thats probaly why they use CF

CF Autoroot for Samsung Galaxy Tab S 8.4
Used this method;
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-t700-t2805366
Worked amazing, so easy to do and pleased that I'm rooted now! Now able to use Sixaxis and PS3 controller with all my specific profiles for various games as needed.
Build KOT49H.T700XXU1ANL2 (SM-T700 WiFi only)
WAY TO GO Beantown!!! Many thanks!!!

can not use screen mirroring after root ....
can not use screen mirroring after root .... can you fix this ?

Tripped Knox...?
I used this method and Knox Warranty went from Knox Warranty Void: 0 to Knox Warranty Void: 1. I have never had to deal with this, but is the warranty voided now? Does it mean anything that it is in gray and not red or something?
Maybe I miss read all the posts saying this will not trip Knox, but..... Why did this happen? I guess it isn't that big of a deal, as I just bought this last night, I can easily just exchange it for a new one, but if it will keep happening, there isn't much of a point.
Thanks.

Alyusha said:
I used this method and Knox Warranty went from Knox Warranty Void: 0 to Knox Warranty Void: 1. I have never had to deal with this, but is the warranty voided now? Does it mean anything that it is in gray and not red or something?
Maybe I miss read all the posts saying this will not trip Knox, but..... Why did this happen? I guess it isn't that big of a deal, as I just bought this last night, I can easily just exchange it for a new one, but if it will keep happening, there isn't much of a point.
Thanks.
Click to expand...
Click to collapse
Seriously? Directly from the post that you downloaded the root package from --
"Warning: I cannot be held responsible for anything you do to your phone, rooting is optional! This Does Trip The Knox Warranty Bit Built into the Bootloader of the Tab S 10.5"
In Big BOLD letters.

hawkxcore said:
Seriously? Directly from the post that you downloaded the root package from --
"Warning: I cannot be held responsible for anything you do to your phone, rooting is optional! This Does Trip The Knox Warranty Bit Built into the Bootloader of the Tab S 10.5"
In Big BOLD letters.
Click to expand...
Click to collapse
Seriously? Directly from the post that I download the root package from --
TITLE
"[Root][Port] Cf-Autoroot T700 [Tab S 8.4]"
I rooted the 8.4, not 10.5. Not sure what difference this would have since the hardware for the two are identical. In retrospect maybe I should have triple checked, but that exact warning you quoted would lead one to believe it would would trip Knox on the 10.5 and not 8.4.

Thanks

CF-Autoroot T700 [Tab S 8.4] lost after OTA
Hello, I had previously rooted my Tab S 8.4 with CF-Autoroot from Beanstown with no problem. However I received some OTA update from Samsung and now I have lost root access. I tried to root again as I previously had...and even though Odin says it was a success, I still don't have root. Has anyone else ran into this?

dhughes20 said:
Hello, I had previously rooted my Tab S 8.4 with CF-Autoroot from Beanstown with no problem. However I received some OTA update from Samsung and now I have lost root access. I tried to root again as I previously had...and even though Odin says it was a success, I still don't have root. Has anyone else ran into this?
Click to expand...
Click to collapse
Cfautoroot needs to be updated. Just install twrp recovery and flash supersu.zip (google it) with twrp and you should get root

DUHAsianSKILLZ said:
Cfautoroot needs to be updated. Just install twrp recovery and flash supersu.zip (google it) with twrp and you should get root
Click to expand...
Click to collapse
That did it! Thanks so much for the help! Very appreciated!

linux
I want to flash twrp in sm-t700 using heimdall and linux does it work there?

PreachyPreachyMachine said:
Used this method;
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-t700-t2805366
Worked amazing, so easy to do and pleased that I'm rooted now! Now able to use Sixaxis and PS3 controller with all my specific profiles for various games as needed.
Build KOT49H.T700XXU1ANL2 (SM-T700 WiFi only)
WAY TO GO Beantown!!! Many thanks!!!
Click to expand...
Click to collapse
I have same build (KOT49H.T700XXU1ANL2) but could not find chainfire autoroot to root my device (only chainfire build version available is KOT49H.T700XXU1ANF9). Did not want to first downgrade to that version for fear of bricking. Seems like this Beantown rooting worked for you....just wanted to reconfirm same build number before trying.
Thanks

Doesn't matter what build your running. Just flash the one for your model.

ashyx
Today, 07:43 PM |#18
Senior Member1,146 posts Thanks: 378
Doesn't matter what build your running. Just flash the one for your model.
According to the "autoroot.chainfire.eu" website, it is build specific:
"[*] Warning: The above tutorial is only for Android 4.4.2 with the built id KOT49H.T700XXU1ANF9.
[*] If your device isnt running on the same built id KOT49H.T700XXU1ANF9, then you need to download and flash the firmware based on the same build id then after try to root your device from the above method."
This is what is scaring me from trying.

tomkasan said:
ashyx
Today, 07:43 PM |#18
Senior Member1,146 posts Thanks: 378
Doesn't matter what build your running. Just flash the one for your model.
According to the "autoroot.chainfire.eu" website, it is build specific:
"
[*] Warning: The above tutorial is only for Android 4.4.2 with the built id KOT49H.T700XXU1ANF9.
[*] If your device isnt running on the same built id KOT49H.T700XXU1ANF9, then you need to download and flash the firmware based on the same build id then after try to root your device from the above method."
This is what is scaring me from trying.
Click to expand...
Click to collapse
Ok have it your way, cuz I don't know what I'm talking about. :banghead:
Better tell the rooted lollipop users they shouldn't have used it.
Maybe you should look at my Sig.