yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S General] M.Yoda7:
Hi, just got a brand new T705M turned on only once to check fw, it came with 5.0.2 fw T705MUBU1BOF2 , 3 questions especially for [MENTION=1422202]stefan.pilsu[/MENTION] and [MENTION=4899305]ashyx[/MENTION]

I know there are newer FWs which are BOH1 and BPB1, what would you do?

It is uninstalling or freezing Knox related apps mandatory? What do I loose going KNOXless?

Thx in advance,

y
[Galaxy Tab S General] molitar:
Ok after many attempts got this to work on SM-T800 build BOL1. The problem I have now is the Super-Sume is crap! Foldermount will not work with it so I try to install SuperSU but it keeps saying binary needs to be updated. What SU software are you all using?
[Galaxy Tab S General] jsdecker10:
Just based on your post that I'm replying to, it sounds to me like you're most definitely not doing something correctly. After you have *successfully* rooted your Tab S with KingRoot, THEN you should go ahead and proceed with installing Super-Sume. After Super-Sume is installed, the very next thing you should do is run the Super-Sume app. Now I can't remember if just opening up Super-Sume will automatically trigger a root request or if root is only requested after pressing the big blue button in the app...you'll figure it out.. but either way, grant Super-Sume's root access request(Like I just stated, it'll either request root upon opening the app itself, or after the big blue button is pressed first. At this stage though, KingRoot should still be installed and it should be actively prompting you to authorize other apps' root requests. In this particular situation, Super-Sume is requesting root access and KingRoot should be prompting you to authorize Super-Sume's root request, which you absolutely MUST APPROVE its request for this all to work properly.). After Super-Sume has root access, it'll do its thing, and if everything worked out the way it's supposed to, KingRoot will be uninstalled and replaced with Chainfire's SuperSU.

Doing this whole process, you shouldn't have to manually install SuperSU yourself at all. The whole point of this Super-Sume method is that it automates the whole KingRoot uninstallation and safely replaces it with SuperSU for you...automatically, with the only user intervention being that you must approve a root request and press on a huge, blue button to get the process started. And yes, this method does work...I followed this method as well(Tab S 8.4, T-700), and it worked flawlessly. The only extra step I took myself was deleting a couple of leftover remnants of KingRoot. Besides that, this method is a piece of cake!
[Galaxy Tab S General] molitar:
Thanks SuperSU Me was what I needed. Did not see mention of it in the first post but sure enough that was able to update the SU Binary and now it's fully rooted.
[Galaxy Tab S General] ashyx:
If you have root then you may aswell just use flashfire to upgrade.

Firstly you could make a backup. Not only that it's actually easier than messing with odin as no PC needed.

The only thing I use Odin for now is flashing bootloaders.
[Galaxy Tab S General] louiscar:
Well not yet. I downgraded to anf7 but haven't rooted it yet.

So I guess you are saying that I should root as per your orginal thread and flashfire.

I was just curious if I could have installed my original ANL1 then used Kingroot as per this thread unless this method only works for Lollipop in which case I won't bother to try.
[Galaxy Tab S General] ashyx:
Well you may as well try v4.5 now seeing as you have already downgraded. At least you could then confirm if it works or not.
[Galaxy Tab S General] louiscar:
Would it not be better to go back to my original stock ROM ANL1 and try it then ?

I not then if I were successful on ANF7 I'd have to flashfire ANL1 to keep root presumably.
[Galaxy Tab S General] stefan.pilsu:
[MENTION=644996]louiscar[/MENTION]

Why don't try first to root the original rom, that you intend to use(keep).

It's the shortest way, of course if works.

At the time when [MENTION=4899305]ashyx[/MENTION] recommends to downgrade to a earlier rom, kingroot was not able to root the last released upgrades.
[Galaxy Tab S General] ashyx:
If you already have anf7 installed then you may as well try rooting that. If it works just update to lollipop with flashfire.

You are going to have to flash again either way. If you flash to lollipop first and it doesn't work then you will need to downgrade again.

I don't understand your trepidation, if it works it works.
[Galaxy Tab S General] c4td0g:
Not sure what I could be doing wrong. Galaxy Tab 10.5 here. Gets to about 22%, kicks me out of the app and says the process failed. I'm using the 4.5 beta.
[Galaxy Tab S General] ashyx:
Look again in the kingroot thread ;)
[Galaxy Tab S General] c4td0g:
Found it :)

Unfortunately it's not working on my T800. Is T800 supported?
[Galaxy Tab S General] louiscar:
A little nervous due to being new to Samsung devices and first use of Odin. That will get better :)

You misunderstand though, I am happy about going to Lollipop with this method however, as I will want to used Xposed framework I've decided to stay with Kitkat ANL1 and that is why I asked if Kingroot 4.5 was going to work for Kitkat or was it just working for Lollipop.

That 'trepidation' comes mainly from being painfully aware (from my Note 3 experiences), that Google closed the Towelroot exploit for ROMS later than a certain date (forget exactly without looking up) which meant that any rooting after that means a Knox 0x1.

I'm getting used to the fact that these Tablets appear less restricted.

---------- Post added at 02:46 PM ---------- Previous post was at 02:42 PM ----------

Ok looks like I've got 2 choices and Ashyx is also right in that I could try it with current ROM and see. As long as failed attempts do not risk tripping knox I've got nothing to lose.
[Galaxy Tab S General] ashyx:
Please post your firmware build version.
[Galaxy Tab S General] stefan.pilsu:
Try this Kingroot it's from [MENTION=4899305]ashyx[/MENTION] tread ( http://rghost.net/8ktMhyl9M )

But first try reboot . It's possible that after reboot the Kingroot root process to continue with your installed Kingroot apk
[Galaxy Tab S General] ashyx:
The procedure should never affect Knox no matter how many times you attempt root.
[Galaxy Tab S General] c4td0g:
kernel 3.4.39-4993066

build number LRX22G.T800XXU1B0E3

Thanks for the help. I tried rebooting and am using your beta. I get stuck at 22%
[Galaxy Tab S General] ashyx:
How long at 22%? It usually hangs at some point then continues, this is the exploit doing its thing.

Try again and leave it be.
[Galaxy Tab S General] c4td0g:
I've tried a bunch of times. Sometimes it kicks me out of the app, but now it just goes to Root Failed. No strategy now.

It goes 1 - 16 instantly, hangs a little on 17, crawls to 18 - 22 and than fails. No other apps running in the background

---------- Post added at 02:08 PM ---------- Previous post was at 02:05 PM ----------

Force closed adguard and cleared all the data for kingroot. It crawled to 26% and than failed
[Galaxy Tab S General] ashyx:
Is this version 4.5?

Uninstall, reboot then reinstall the app. Run it, if it stops or kicks you out just leave for another minute or so then reboot. After reboot unlock, but dont touch anything else. Wait a minute. If still nothing.try again. Can take a few attempts for success.

Incidentally v4.5 also managed to root lollipop on my htc m8.
[Galaxy Tab S General] c4td0g:
Uninstalled adguard, rebooted, and failed at 23%. :(
[Galaxy Tab S General] ashyx:
You may need to reflash fresh stock. I had a similar situation first time i tried, i then reflashed stock XXU1BOE3 and it worked first time. This is the firmware i used T805XXU1BOE3_T805NEE1BOE1_NEE
[Galaxy Tab S General] stefan.pilsu:
There aren't 2 choices !

Go for root...
[Galaxy Tab S General] c4td0g:
Will a factory reset be satisfactory or will I have to use odin?

I tried on 4.1, I got to 51% before failing. Uninstalled all rootkings, rebooted and will install 4.5 beta 2 again.

---------- Post added at 02:27 PM ---------- Previous post was at 02:21 PM ----------

Lol went to 37% and than network error
[Galaxy Tab S General] louiscar:
Good to know. I've got some time on my hands this pm so I'm going to give it a go.

---------- Post added at 04:23 PM ---------- Previous post was at 03:55 PM ----------

It's not working for me. I get root on Kitkat ANF7, supersu me removes kingroot, SuperSu is upto date so no need to update but installed pro key.

Reboot - root gone.

Hmm ... the only thing I find is different to others is the update binaries. Supersu doesn't request this.
[Galaxy Tab S General] c4td0g:
Do you want me to try flashing an 805 firmware on a 800 device?

Says its going to take 2 hours for the firmware to download from SamMobile, wow. This is how a 5 minute project turns into a whole day, lol.
[Galaxy Tab S General] stefan.pilsu:
No way !!!

Reflash your rom.
[Galaxy Tab S General] c4td0g:
Ok. To confirm, reflash the exact stock rom?

Is there any other sources than SamMobile?

Thanks for the help!
[Galaxy Tab S General] ashyx:
T800 stock firmware: http://www.sammobile.com/firmwares/download/48440/T800XXU1BOE3_T800NEE1BOE2_NEE/
[Galaxy Tab S General] c4td0g:
Thanks. I don't have a premium account - going to take 2 hours to complete!
[Galaxy Tab S General] ashyx:
Yep same as I experienced on kitkat with supersu me. Once you have root dont reboot, just run flashfire and install lollipop.
[Galaxy Tab S General] louiscar:
It might say that but it didn't take that long when I downloaded so get it started and keep fingers crossed. :)

---------- Post added at 05:09 PM ---------- Previous post was at 05:01 PM ----------

I also tried with Kingroot 4.1. A reboot kept root but as soon as I ran Supersu me and rebooted it was lost.

I don't want Lollipop, as I've said I need to stay on Kitkat but I'll try reflashing ANL1 (my original ROM before the downgrade).

I take it supersu me is still ok to use instead of the "Replace_Kinguser_with_SuperSU-v2.0" part in your thread? It strikes me that there may be an essential difference here.

Any ideas why SuperSu fails to request and update to the binaries? I did look for an option in the settings to see if I could force this in the hope that it might have something to do with it.
[Galaxy Tab S General] ashyx:
NEE-T800XXU1BOE3-20150619111130

https://yadi.sk/d/_kS89BPhhPc9t
[Galaxy Tab S General] stefan.pilsu:
There it's a big, BIG fight between Kingroot devs and Chainfire SuperSu and Super-Sume.

If SuperSu binaries don't update means that Kingroot blocked it.

SuperSume devs recommend to reboot, reroot, only now install and run supesume.
[Galaxy Tab S General] ashyx:
Youve, got me confused:what: why are you rebooting?

You gain root then use supersu me which fails, as i said i had the same issue. Just root then follow the instructions in the kingroot guide. Run the script in that thread and you will get root with supersu. All you need do then is flash your rom with flashfire.
[Galaxy Tab S General] louiscar:
Got it.. I'm going to give that a go. On subsequent tries I didn't uninstall supersume so that could also be a mistake.

I'll do exactly as above ... fingers crossed ..

---------- Post added at 05:44 PM ---------- Previous post was at 05:36 PM ----------

Rebooting to see if this method works and root is lost or retained. I will try your method next.
[Galaxy Tab S General] stefan.pilsu:
There aren't two methods.

The "script" it's exactly the same that one in supersume.

Kingroot somehow anihilated them.

I was beginning with the script but I wasn't able to run it in terminal. Then at first try supersume works !
[Galaxy Tab S General] louiscar:
Then I'm cooked because when following the correct method:

1) uninstalled supersu binary (Unroot)

2) Uninstalled supersume

3) reboot

4) Start again Kingroot 4.5

5) reboot (I know I didn't actually have to do that with 4.5)

6) Install and run Supersume

7) Run Supersu - This time yes! it asks to update binary.

8) result: Installation failed "please reboot and try again"

.... Gawd!

Ok here's an interesting thing. The above method actually lost me root. When I rebooted I ran Kingroot again and it immediately established root on "Try it" rather than going to the "try to get root " and waiting. It was instant! That must mean that Kingroot (or kinguser) was still present.
[Galaxy Tab S General] c4td0g:
Thank you! :)

Now if only ODIN would see the tab s in download mode. It sees it when its regularly booted. I have usb debugging on. Any suggestions?
[Galaxy Tab S General] stefan.pilsu:
Looks that remaining leftovers prevent supersu update bin...

Reflash stock with odin then continue with kingroot.
[Galaxy Tab S General] stefan.pilsu:
Change USB port ?
[Galaxy Tab S General] stefan.pilsu:
If update binary fail kinguser, wich is the supersu equivalent it's still there and you have root with kunguser as root manager
[Galaxy Tab S General] c4td0g:
Tried all 3 on the front.

In normal mode ODI sees it but in download mode it doesn't. Don't understand. Have tried rebooting pc etc
[Galaxy Tab S General] stefan.pilsu:
You have drivers installed ?

make sure that all kies related processes are stoped
[Galaxy Tab S General] c4td0g:
It says Samsung Mobile USB Composite Device and Samsung Android ADB Interface are both ready to use.

In Device Manager Samsung Android ADB Interface is listed.

How do I stop kies?

Thx for all the help
[Galaxy Tab S General] stefan.pilsu:
look in task manager: processes
[Galaxy Tab S General] louiscar:
Not sure I want to leave it like that. This is crazy! What's the point of rooting when the very app that gets you root restricts what you can do. It's just passing control from one to another! The fact that they do everything to stop you getting rid of it is suspicious in itself
[Galaxy Tab S General] c4td0g:
No Kies processes running
[Galaxy Tab S General] stefan.pilsu:
reflash rom with odin then kingroot

works for me everytime
[Galaxy Tab S General] c4td0g:
Am I supposed to hit the ADB mode? When I do the computer makes a jingle, but it doesn't pop up in Odin.

If I just stay in download mode, no jingle.
[Galaxy Tab S General] ashyx:
If you don't uninstall kinguser as indicated in my guide the su binary update will fail.
[Galaxy Tab S General] louiscar:
Yep and I think I'm going to have to do that next. Maybe after reflashing as stephan suggests just in case.

What is strange is that I can not repeat the circumstances where SuperSu requests the binary update. I thought it was due to the steps I detailed previously but that doesn't work anymore. Anyway my last try on this test was to do kingroot 4.1 and try the two reboots however I expected to lose root on reboot but it actually stayed rooted.
[Galaxy Tab S General] stefan.pilsu:
When run kingroot also an app Purify it's installed... "What's more, we just released new Apps named PURIFY 1.0 . PURIFY will make you device faster and purer. It can close App running in background automatically and let them never auto start. She also can archive notifications and make your notification bar have a new look"
[Galaxy Tab S General] ashyx:
OK, this will be my last input on this as its going in circles and sending this thread off topic.

You won't lose root after reboot with kingroot. That only happens when you convert to supersu.

You have already proved that you can gain root on your current rom. All you need do now is continue from step 6 in the kingroot thread and you will convert to supersu.
[Galaxy Tab S General] c4td0g:
Ashy and Stefan do you have any idea why I can get odin to pick up the tab s in normal mode but not in downloading mode? I'm going nuts here
[Galaxy Tab S General] stefan.pilsu:
no ideea

I just checked and when it's booted I didn't see it in odin

only in download mode the blue sign apear in odin
[Galaxy Tab S General] ashyx:
Uninstall kies if you have it then install the Samsung drivers. Reboot.

Start Odin in admin mode then plug in the tablet. You should see the added message. If not the Samsung drivers are not correctly installed. If you have windows 8.1 you may have to disable driver signing enforcement.
[Galaxy Tab S General] c4td0g:
Just installing Kies now. Will uninstall after it's done lol.

Can I flash the stock rom off the microSD?
[Galaxy Tab S General] ashyx:
Nope, you can only do that with flashfire.
[Galaxy Tab S General] c4td0g:
Should I hear a jingle / be detected in odin when its in download mode or only after selecting apply update from ADB?
[Galaxy Tab S General] louiscar:
Ok perhaps I should post in the other thread. This is getting wierder by the minute. Following your thread :

Installed the required apps and moved the /mrw folder to the internal card.

Now Kingroot fails to get root. ... this is fun.

Edit: haha yep until I remove the mrw folder and the 3 apps installed.
[Galaxy Tab S General] stefan.pilsu:
Run kies once with tab connected

disconnect tab

restart pc

close kies and all related in task manager

run odin.....

the firmware must be in pc
[Galaxy Tab S General] stefan.pilsu:
not fun

somehow KR prevent running script as also blocked supersume

right now i'll try reflash rom and go with KR one more last time

as I told you before works for me
[Galaxy Tab S General] c4td0g:
When I boot into download mode, do I stay on the initial screen or scroll down and select apply update from ADB?
[Galaxy Tab S General] stefan.pilsu:
this it's not download mode it is recovery

for download mode POWER+HOME+VOL.DOWN when ask VOL.UP
[Galaxy Tab S General] c4td0g:
Hm. Do you have a picture of what download mode looks like or what it should say? I've been donig power+home+vol down
[Galaxy Tab S General] stefan.pilsu:
you are doing for sure power+home +vol. up...if you can read install from adb...

try again
[Galaxy Tab S General] c4td0g:
You're right lol. Embarrassed :confused:

It says on the PC drivers installed when I booted into ODIN mode but still not detected in Odin :(!@#$

PATIENCE ! It worked!!!!!!

Now to flash
[Galaxy Tab S General] stefan.pilsu:
take care
[Galaxy Tab S General] c4td0g:
Thank you for the help.

Hopefully I can root after this
[Galaxy Tab S General] stefan.pilsu:
http://xdaforums.com/showpost.php?p=61905052&postcount=15
[Galaxy Tab S General] c4td0g:
LOL and it still failed
[Galaxy Tab S General] stefan.pilsu:
What failed
[Galaxy Tab S General] c4td0g:
Kingroot 4.5 after flashing the stock rom
[Galaxy Tab S General] stefan.pilsu:
Your flashing process was too fast....
[Galaxy Tab S General] c4td0g:
3.5 minutes is too quick? I can do it again but it said successful
[Galaxy Tab S General] stefan.pilsu:
you used this ?

http://rghost.net/8ktMhyl9M
[Galaxy Tab S General] c4td0g:
Yes after flashing the rom ashy told me to

---------- Post added at 07:21 PM ---------- Previous post was at 07:20 PM ----------

In Odin I have Autoreboot and Reset Time selected. I'm selected the tar file under AP. Is that correct?

T800XXU1BOE3_T800NEEE1BOE2_HOME.tar
[Galaxy Tab S General] stefan.pilsu:
Retry kingroot you must be connected to internet
[Galaxy Tab S General] c4td0g:
I tried a bunch of times 4.5 and 4.1. WiFi connected
[Galaxy Tab S General] stefan.pilsu:
Let it as it is don't change anything in odin.

I think AP it's correct
[Galaxy Tab S General] ashyx:
I guess you mean Odin was successful.

Don't give up if the first time with kingroot fails. Try again.
[Galaxy Tab S General] c4td0g:
Odin said successful after flashing not Kingroot. Kingroot still fails unfortunately
[Galaxy Tab S General] stefan.pilsu:
maybe it is not available yet

there it's a button to request blabla..
[Galaxy Tab S General] c4td0g:
How can that make any sense? I have a Galaxy Tab S, we're in the Galaxy Tab section and people are using this method to root. Why would my device not be compatible but everyone else is lol
[Galaxy Tab S General] stefan.pilsu:
[MENTION=4899305]ashyx[/MENTION] it's right retry
[Galaxy Tab S General] stefan.pilsu:
Congratulation to [MENTION=644996]louiscar[/MENTION]

"Samsung Galaxy Tab S 8.4: Android 4.4.2 - ANL1 Rooted Knox 0x0

(thanks to Ashyx)"
[Galaxy Tab S General] ashyx:
Confused?:what:

Never mind I see lol
[Galaxy Tab S General] c4td0g:
Ashy can you recommend any other firmwares to flash and try rooting? The Canadian one isn't compatible
[Galaxy Tab S General] ashyx:
Maybe an earlier version of lollipop or just downgrade to anf8 firmware which is proven to work with kingroot.

One thing you can try before changing firmware. Just try enabling USB debugging in developer options.

The firmware you are using is exactly the same as mine, except for LTE, even down to the changelist.
[Galaxy Tab S General] stefan.pilsu:
Not at all.

Just curios.

The result it's great, only missing the story's final chapters.
[Galaxy Tab S General] louiscar:
Yes it worked the script way. And thanks for your help too Stefan. I'm grateful for the input.
[Galaxy Tab S General] stefan.pilsu:
:good:
[Galaxy Tab S General] c4td0g:
Thanks for trying Ashy and Stefan.

I give up, this is just too time consuming.
[Galaxy Tab S General] ashyx:
I meant I was confused but I see now.
[Galaxy Tab S General] louiscar:
Sorry Stefan, I posted in Ashyx thread. But really I reverted to the original way. Using Kingroot 4.1. The only thing I would change in future is not to load the apps or the /mrw folder till kingroot has got root. As I had done this first, all of a sudden Kingroot simply failed to get root and I tried several times. Immediately after deleting the files and removing the apps it got root first attempt. Wierd.

No problem as all that stuff can be done next. I did make a silly mistake but somehow got away with it.

In between the terminal steps 1) get Su and 2) run the script I didn't remove kinguser. My eyes were hurting after all the messing around .:D

Somehow though once the script finished I looked for kinguser and is wasn't there so I got away with it, if it was an important step.
[Galaxy Tab S General] ashyx:
Well you can always do it the proven way with cfautoroot if you don't mind tripping Knox.
[Galaxy Tab S General] stefan.pilsu:
My first attempts at runing scripts failed.

Maybe I wasn't pay attention.

For sure I'll not go back to try them again...:o
[Galaxy Tab S General] stefan.pilsu:
I'd like to confirm that [MENTION=4899305]ashyx[/MENTION] script works perfect for rooting SM-T700 UK last Lollipop firmware: after rooting with KR, open terminal, type su, grant permision, run the script, confirm KR uninstall, update binaries. No other prompts in my case.

MRW file was in /sdcard and this time I realised that when you type in terminal there it's a space just after sh. Until now my mistake was that I was typing "sh/sdcard/mrw/root.sh" instead of "sh /sdcard/mrw/root.sh"

SM-T700 UK Lollipop Permanent Root
[Galaxy Tab S General] xxvincixx:
Yeahh, work on t705...!!! ✌✌✌✌???
[Galaxy Tab S General] Andro Uno:
Succsess rooting my SM-T700 firmware T700XXU1BOE5 (DBT) german!! Permanent Root, Knox bit 0x0:D. I'm not shure - may I uninstall "supersu ME"? SuperSu is still present. Special thanks goes to Stefan and Ashly:good:!!

:good:
[Galaxy Tab S General] louiscar:
I made that typo too but realised it when I got the error. :)

Meanwhile I'm thinking of maybe doing it again because I've ended up with ANL1 firmware and ANF7 bootloader. Not sure if I can extract the bootloader in the same way and flash that separately with Odin as per the Lollipop scenario. What do you think?

Congrats on the Lollipop success.
[Galaxy Tab S General] stefan.pilsu:
No more need for supersume
[Galaxy Tab S General] stefan.pilsu:
Go [MENTION=644996]louiscar[/MENTION] do it...

Regarding bootloader use 7zip
[Galaxy Tab S General] Andro Uno:
Thank you for the quick answer!:)
[Galaxy Tab S General] louiscar:
Sure? :D

I didn't think of 7zip. I came across this thread which I thought was useful for making .tars

http://xdaforums.com/galaxy-s3/general/guide-extract-bootloader-make-flashable-t2864264
[Galaxy Tab S General] SirUnreal:
Using KingRoot 4.5.0 beta 2 with my T705, Android 5.0.2, build BOE7 (Italian version), baseband BOE1, kernel 3.4.39-4627885.

Result after 21%: "Root Failed / no strategy now"
[Galaxy Tab S General] stefan.pilsu:
Don't give up if the first time with kingroot fails. Try again.