yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S General] sram21092:
I was reading some threads in the Fire Phone section since I've been waiting on root for that device too, but someone discovered and posted about the new version of Kingroot (v4.0), and how they were able to root with it. I immediately downloaded it and tested it out, and after two tries, I gained root access on my Fire Phone.

So I thought, what if this would work on my AT&T Tab S 10.5 (T807A)? WELL IT DOES!

I have root access on my carrier branded/bootloader locked tablet. I was surprised at first at how easy it was, and at the end, Kingroot even had a prompt to disable or remove KNOX. I don't know if it worked, but I had no problem with installing Xposed and some nice modules.

THIS APP IS ALMOST COMPLETELY IN CHINESE. I know, it sounds a little scary, but after a day of running root, I found it safe to post about it here.

Please read the english guide for some clear instructions. The links are below and make sure you download the newest version. It may take a few tries, but use a root checker to see if it actually worked or not. KingRoot will install KingUser. After obtaining root, you can delete KingRoot and the blue icon app with the Chinese name.

UNTESTED ON OTHER VARIANTS BESIDES T807A! I believe it may work on the other carrier variants also.

I am not affiliated with the app nor deserve credit for what it can do, as I just want to spread the word that this works with our damn bootloader locked devices. If the people of KingRoot have a donation page, it might be that day to actually give thanks.

THE NEWEST VERSION (4.0+) WILL WORK. All you will need to do is press the Blue Button when you open the app, allow the installation of KingUser, and it will give root access. I verified it with a root checker and both my devices after multiple reboots. I installed SuperSu and updating the Su binary will FAIL.

YOU ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. DOING THIS CAN POSSIBLY BRICK YOUR TABLET SO PLEASE BE CAUTIOUS! THIS WILL VOID WARRANTY AND TRIP THE COUNTER!

Official site for KingRoot:

http://www.kingroot.net/

Guide that I used in English:

http://androidxda.com/root-android-device-using-kingroot

DOWNSIDES:

1) Kingroot is in only chinese with no english version supported.

2) As of right now, I can not update SU binary with SuperSu, Kingroot installs its own app called KingUser, which serves the same function. (someone will eventually figure out how to make SuperSu work since we now have root)

3) Bootloader is still locked, DO NOT FLASH CUSTOM FIRMWARE OR RECOVERY!!!!! IT WILL BRICK YOUR DEVICE!
[Galaxy Tab S General] sram21092:
REQUEST:

I need someone to make a backup of the AT&T stock firmware and recovery. I made a mistake with an app that messed with my recovery and now I'm in a bootloop.

If someone could please make a backup of each with Flashify or something so I can try with Odin in download mode, then I think it might be okay or I just found root and messed up my tablet.. lol

I made a backup myself but I was stupid and chose SDcard thinking it was referring to the external microsd card.

I NEED THE STOCK RECOVERY IMAGE for the most recent update for the ATT variant. (NK1)

I will keep the file links in this post for reference and in case someone wants it.

PLEASE AND THANK YOU!
[Galaxy Tab S General] DUHAsianSKILLZ:
That's sweet! As for firmwares, there are currently none I've found. Flashing can only backup recoveries. The only thing I can suggest is using samsung kies.

Just to confirm, your still on Kitkat correct?
[Galaxy Tab S General] sram21092:
I've tried Kies but I can't get it to recognize my tablet. I'm currently on NK1 which is kitkat 4.4.2
[Galaxy Tab S General] xiaonan80:
Does it trigger Knox?
[Galaxy Tab S General] DUHAsianSKILLZ:
No
[Galaxy Tab S General] ashyx:
Just extract the stock recovery from the stock Rom and flash with flashify.

Also I'm surprised Knox got tripped with this method.

I've had great success with other devices with kingroot, but it's never worked on the tab s.

If they have now found a working exploit then that is great news for locked bootloader devices.

Also if the android app fails don't give up, try the pc version. I've had the android version fail where the pc version had success.
[Galaxy Tab S General] DUHAsianSKILLZ:
The only thing I can suggest, is for someone to use flashfire or some sort. I don't know why there's no firmware for T805W yet :(
[Galaxy Tab S General] sram21092:
Currently there is no place to download the AT&T stock firmware, which is why I need someone who roots their T807A to pull it for me and upload it so we actually have it. I've been looking all over the internet but no luck. The only thing I have access to at the moment is download mode, and I've been trying stock recovery.img I found for similar variants, but Odin is failing each time because of the locked bootloader..

Btw, installation from unknown sources needs to be allowed and it will ask to install KingUser. The first time I tried it, it didnt ask or work for me. The second time it asked to install and the root worked.
[Galaxy Tab S General] ashyx:
The recovery wont be device specific, so any recovery from stock will do.
[Galaxy Tab S General] sram21092:
Do you think I would be able to flash a stock NK1.tar using Odin and make it work again? I only get "FAIL" when I try to flash any recovery

Here is the log:

<ID:0/005> Added!!

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Erase...

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> recovery.img

<ID:0/005> NAND Write Start!!

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Tab S General] ashyx:
What did you use that corrupted your recovery?

By the way I just returned my T805 tab s to stock kit kat. The first 2 times I ran king root it froze at 20% then rebooted. The 3rd time it continued past 20% to 23%, it then rebooted and then after a short while the king root app restarted from where it left off.

It took a while to complete and at the end it said it had failed, BUT it hadn't! I checked and had root access. I then downloaded the kinguser app. After that any app could get root.

I would think that this method will work on any version. Not sure about lollipop though. My advice is if it doesn't work first time try and try again!

Here is the king root v4 app: kingroot v4

Kinguser v4: kinguser v4
[Galaxy Tab S General] sram21092:
I was messing around with twrp manager and I somehow ended up flashing some recovery. I don't even know if it was for tab s or not.

I was able to flash stock recovery for a different version on Odin and now it says I need to take it to the att store. I'm still able to get into download mode, but it won't let me get into recovery to factory reset. Hopefully a stock.tar.md5 can save me, otherwise I get a fail in odin
[Galaxy Tab S General] ashyx:
Does kies not give you the option to repair or reinstall?
[Galaxy Tab S General] sram21092:
It won't detect my tablet. It tries to connect and then fails. Drivers install properly too
[Galaxy Tab S General] ashyx:
I forgot your device is snapdragon. You need the snapdragon recovery.

I'm guessing the Sprint recovery will work. That is available. If you can't get it I may have it somewhere.
[Galaxy Tab S General] sram21092:
the AT&T and T-mobile version are actually Exynos processors and verizon/sprint is snapdragon.

KingRoot might only work on Exynos processor versions of Tab S. But then again, we have to wait til others are willing to test it out
[Galaxy Tab S General] elliwigy:
all he needs is someone with the 807a to hook up to kies and when it downloads the firmware you can copy it from the pc to desktop before the firmware dissappears as it will be gone once process is complete
[Galaxy Tab S General] ashyx:
My error you're correct, att is exynos.

I tried it on lollipop and it wasn't able to get root , so looks like its kitkat only.
[Galaxy Tab S General] DUHAsianSKILLZ:
[/COLOR]

Would this guide help http://xdaforums.com/showthread.php?p=60546134 I believe you also need a serial number in kies.
[Galaxy Tab S General] sram21092:
Thanks I tried doing this but it doesn't recognize my model name. After I put the s/n, it tells me to check the model name again..
[Galaxy Tab S General] elliwigy:
you can do the emergency recovery and initialisation or w.e option. watch the temp folder and itll turn into a tar.md5.zip once its finished then copy it over soon as it does to somewhere on your pc
[Galaxy Tab S General] sram21092:
I've tried but I haven't had my tablet connected to kies before and it doesn't connect to it when in download mode either so I'm screwed in that end too

If anyone has the T807A, please use kies to pull the stock firmware or use an app like flashify to make a backup after rooting!
[Galaxy Tab S General] elliwigy:
i meant for whoever can to pull the firmware tar for you lol
[Galaxy Tab S General] sram21092:
apparently AT&T is pushing out lollipop for the tab s today
[Galaxy Tab S General] scanjans:
Hfs

IT WORKS

Thank you. Ive been waiting so long for root.

THANK YOU

WORKS
[Galaxy Tab S General] xiaonan80:
Any idea if kingroot would work on T805? I like the idea of not tripping Knox.
[Galaxy Tab S General] elliwigy:
best idea would be to try it and let us know lol
[Galaxy Tab S General] xiaonan80:
Don't owe one yet... consider getting one if root is possible without tripping Knox.
[Galaxy Tab S General] elliwigy:
you need knox? theres not really anything its good for imo lol
[Galaxy Tab S General] ashyx:
Not being funny but this thread is only 3 pages and the post I made is only a few posts back.

Don't skim threads BEFORE asking questions.

http://xdaforums.com/showthread.php?p=60680054

Doesn't seem to work on lollipop though.

---------- Post added at 08:26 AM ---------- Previous post was at 07:40 AM ----------

I've uploaded stock recovery from lollipop. Worth a try.

http://www.mediafire.com/download/qyybs0m1yln443x/Stock_recovery_T805XXU1BOCC.TAR
[Galaxy Tab S General] sram21092:
Thanks for uploading this but the file fails in Odin also. I guess I have to wait until an AT&T stock firmware is uploaded somewhere online
[Galaxy Tab S General] godzilla8nj:
I've decided use Kingroot on my T807A, and I'd be happy to do this for you if you walk me through it.
[Galaxy Tab S General] godzilla8nj:
Ok, I'm new to all this. I have rooted devices and installed recoveries and ROMS, but have never rooted a bootloader-locked device, dumped a stock recovery, compiled a custom recovery, etc. So I'm leaving breadcrumbs for what I'm doing:

This guide is for the Samsung Galaxy Tab S 10.5 T807A (device codename: chagalllteatt)

Part I: Rooting the tablet

* Download and install latest KingRoot (I'm using v4.1.0.249). You must, of course, enable Unknown Sources.

* Root the device with KingRoot.

* Download RootChecker and verify root.

Part II: Dumping the stock partitions

* Enable Developer Mode and USB debugging.

* Follow this guide to dump the stock recovery. In Way 2 this was the device-specific path needed:

Code:

ls -al /dev/block/platform/dw_mmc.0/by-name

* Stock images HERE.

Part III: Creating custom recoveries

* First attempt: ClockWorkMod (CWM) recovery by uploading recovery.img to http://builder.clockworkmod.com.

FAILED. Sadly it looks like CWM Builder is no longer a thing: https://plus.google.com/103583939320...ts/2iKwJNBJHRF.

* TeamWin Recovery Project (TWRP) from source: http://xdaforums.com/show...5#post32965365

WIP here: https://github.com/sanicki/android_d..._chagalllteatt

* ClockWorkMod (CWM) recovery from source: http://xdaforums.com/show....php?t=...B]Volume Up + Home button + Power button[/B].
[Galaxy Tab S General] ashyx:
There are easier ways of going about this.

There is no need to create a recovery.

The existing twrp recovery for the t805 should work fine on a t807a.

Now I say should, the issue is that the bootloader is still locked even after rooting.

The recovery can be flashed via flashify or flashfire. However because of the locked bootloader it may not boot or it may simply trip Knox.

Nobody has tried it yet afaik. If it doesn't boot then you will need to reflash the stock recovery, so I suggest making sure the original is backed up with flashify.
[Galaxy Tab S General] elliwigy:
you cannot use a custom recovery on att or verizon since you have a locked BL.

You have only two options:

1) Look into multisystem

2) Use Flashfire

I personally would go with Flashfire. Id also stop waisting time now trying to brick your phone by trying to use cwm or twrp etc. since it will not work.

You should read up on locked BL's and other things before tinkering with the kernel and BL.

One thing is CERTAIN and that is CWM AND TWRP WILL NOT WORK. As stated, you will either brick your device or trip knox and still not have cwm or twrp lol.

Flashfire should work great and can flash zips and custom roms etc.
[Galaxy Tab S General] godzilla8nj:
Thanks for the advice!

As long as I have root and can block ads and use Xposed I'm actually satisfied. My only concern is that once already I got trapped in boot loop when playing around with an Xposed module's settings. Had to ship the tablet back to Samsung to restore it since there's no recovery image available.

So I guess what'd I'd really like is to create a recovery image that could be used with adb and/or the stock recovery. Is that possible now that we have root or still impossible because of Knox?
[Galaxy Tab S General] elliwigy:
you dont have a recovery option like that.. basically what you can do is create and restore backups in flashfire but the tablet would have to be able to boot to use this feature.

i create backup and move to pc so if anything goes wrong i use kies or smart switch to recover the tablet, reroot and install flashfire then move backup to device and restore.

or you can use kies/smart switch to get a copy if the full odin tar so you can just use odin if something happens. of course youd at least need to be able to get into download mode.
[Galaxy Tab S General] ashyx:
Your stock recovery should be available via kies now, so I suggest you save it as a backup should you ever need it.

Actually I think someone already posted it on this forum.
[Galaxy Tab S General] nethead72:
My t807a updated to 5.0.1 on its own. Odd that. Anyway, KingRoot does not work for this version. Can I use kies to downgrade to 4.4.4?
[Galaxy Tab S General] ashyx:
I doubt it. You may be able to flash just the stock boot and system image from another stock rom though.
[Galaxy Tab S General] Russ77:
Well now I'm bummed... I have the t707a (8.4" version) and check for updates every day no dice.

How is 5.0.1 on your tablet? I got the update on my s5 and only have good things to say about it.
[Galaxy Tab S General] ashyx:
You will get the update eventually. If you can't wait and you're still on kitkat then you can root your tablet using kingroot then follow my guide to install one of the lollipop roms from the development section.
[Galaxy Tab S General] elliwigy:
i really dont understand why it doesnt work for t807v lol but what can you do
[Galaxy Tab S General] ashyx:
What doesn't work? :what:
[Galaxy Tab S General] elliwigy:
root doesnt work.. ive tried on kk and L since king roots been out hundreds of times and no luck lol
[Galaxy Tab S General] ashyx:
Have you actually read the rooting guide? You have to downgrade to a certain version.

May not be possible though for t807v.
[Galaxy Tab S General] elliwigy:
i tried on kk and L builds (couldnt find original os for when tablet was first released)

it might work on nk1 i think it was? no one was ever able to locate the firmware and mine was already updated when i bought it.
[Galaxy Tab S General] leapinlar:
I have a T707v and I followed the guide but the earliest firmware available was ANG7 and it needed to go back to at least ANF8. But I tried ANG7 anyway and the kingroot still did not work. I have disabled automatic updates and will stay with ANG7 hoping kingroot will eventually work.
[Galaxy Tab S General] AlexNI:
Could anybody, having t807a successfully updated to lollipop, give IMEI (into PM chat). Probably if I change IMEI of my device with XPOSED IMEI Changer it will be possible to download the update and try to catch the stock firmware.
[Galaxy Tab S General] ashyx:
Kies has a feature that lets you redownload your firmware if your device is supported.

Off the top of my head can't remember what its called properly as I hardly ever use it. Something like reinitialization. Give that a go.
[Galaxy Tab S General] elliwigy:
yea.. only works with latest update.. so if youre on an old build and L is available itll dl the L stock firmware.. it will not let you choose
[Galaxy Tab S General] AlexNI:
Bricked my T807A after flashing TWRP Recovery with flashify :(. Now it says that not authorized software detected, and only download mode is available.

Waiting for a stock firmware appearance :(.
[Galaxy Tab S General] ashyx:
Flash the stock recovery.img in download mode. Any should do as long as its stock, but might be best from t807p. Tar up the recovery.img and flash.
[Galaxy Tab S General] AlexNI:
Tried it, but ODIN says NAND Write FAIL :(
[Galaxy Tab S General] DUHAsianSKILLZ:
The images for att T807A can be found here http://xdaforums.com/showthread.php?p=61326829

What you need to do Google how to convert recovery img to tar. Then flash in odin.
[Galaxy Tab S General] AlexNI:
Thank you, I've tried that recovery.img packed into tar with md5. But with no success :(.

---------- Post added at 10:17 PM ---------- Previous post was at 10:09 PM ----------

Is the AP button of ODIN for the recovery?
[Galaxy Tab S General] ashyx:
What error do you get?

Don't pack it into md5, just create a normal tar file and flash in AP slot.

Use the command:

tar cvf recovery.tar recovery.img
[Galaxy Tab S General] AlexNI:
Tried it as well. ODIN always says:

NAND Write Start!

FAIL!
[Galaxy Tab S General] ashyx:
Its quite possible that because of the locked bootloader the tar package is being rejected as its unsigned.

The only suggestion I can make is to try an official stock firmware package.

The only one available and a small possibility to flash is the t707v firmware on sammobile as that model also has a locked bootloader.

It may completely fail or if lucky it may go so far as to flash the bootloader and recovery image and fail everything else.

At least if it flashes the recovery, you will be able to boot to recovery and possibly boot to android as normal.
[Galaxy Tab S General] elliwigy:
you can only odin stock tar files.

its never recommended to flash firmware from other devices on other variants.
[Galaxy Tab S General] ashyx:
Well firstly you can flash files with odin that are not stock otherwise how would we be able to root and have custom recoveries?

Normally good advice, but his device is basically bricked and has no other route except to send it for repair to Samsung.

If he can at least get a stock recovery on his device he has a chance of recovering his device.

The only way he can do that is by flashing a firmware that the bootloader will accept.

Seeing as there is no Odin flashable stock firmware he has to try and use the nearest thing regardless of whether it is for his device or not.

If he can get recovery to flash he then has other options to recover.
[Galaxy Tab S General] ashyx:
Have you tried the Emergency firmware recovery mode in Kies. If Kies can detect your tablet in download mode you may have a slim chance of recovery.

I've never used this nor do I often use Kies. Have a quick Google about it.
[Galaxy Tab S General] elliwigy:
firstly, you can only do that if you have the ability to unlock the BL.. otherwise it will fail to flash custom tar files as jt always has on locked BL's.

second, he will still be screwed even if he can get into stock recovery if there is no system installed he will not be able to boot.. he should have no issues if someone else with the same device can just upload the firmware for him (this is the only option imo.) If he is able to power the device on there is hope.. attempting to flash firmware from another device risks a hard brick making the issue worse IF it even flashes... this should ONLY be a LAST resort since it might break completely...

---------- Post added at 05:24 AM ---------- Previous post was at 05:20 AM ----------

i thought he tried this already? this or smartswitch...
[Galaxy Tab S General] ashyx:
Are you trying to help or just here to challenge everything I post? :confused:

I'm aware only stock firmware can be flashed with a locked boot loader, however you didn't state that and made a general statement that Odin only flashes stock firmware.

If he can somehow get stock recovery on the device it may well boot. He didn't state that system wasn't installed. The problem is he installed a custom recovery which is why the boot loader is blocking the device from booting.

If kies can't recover his device he has no other choice so this IS a last resort . As already stated there is NO stock firmware available for the T807a flashable with Odin.

What I posted above likely won't work anyway, so if you've got anything constructive to add that helps the situation then post it.
[Galaxy Tab S General] elliwigy:
in his situation (locked BL) then he can ONLY flash stock odin tars.

It will not work if BL/Recovery is different than the installed system.

Someone who has a t807a can pull the stock odin firmware using kies/smart switch and upload for him. This is the ONLY way he can get a full tar if kies doesnt work for him because of his situation. This is how everyone pulls stock tar files that arent available on sammobile.

This is proven facts that will help him.. if no one wants to pull the tar img for him then his only option is to send it in for repair.

I'm ONLY trying to help with factual information not to argue with you.

You have the right idea so I was just adding on to what you posted..

This is why people shouldnt flash tars not for their device so I was just saying his problem from the start is what you were implying for him to do (flash a tar file not for his device) Which will only make matters worse..

They might be very similar but builds are different.. he has a t807a not a t807v.
[Galaxy Tab S General] ashyx:
Look, the recovery is the same for all models, I should know I've unpacked and modified enough of them. I use the same recovery in all my Cf-autoroot ports, that's T700/705/707/800/805/807 the only difference being between the Exynos and Snapdragon vesrions which use a different ramdisk. It's same for my Tab A ports SM-T350/P350/T550/P550 or are you going to tell me that those don't work too?

as for the Kies update, I was under the impression from what some others have stated is that KIES doesn't download the update as a complete TAR package, but as seperate image files.

The images are not flashable with ODIN even if packed into a TAR file due to the locked bootloader.

If this is not the case and KIES does download a complete TAR package then I stand corrected and you are right a simple flash with ODIN if someone uploads the package is all it needs.

Like I say I don't hardly ever use KIES, but with little the time I have had with it I can't actually confirm, but I seem to remember the same thing when i saved an update.