yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S General] ashyx:
You didn't need to do any of that. Many of the roms fail at hidden.img or cache.img if it's not for your specific country.

Everything that is required will flash.

All you need do after it fails is boot to recovery and wipe the cache and it will boot just fine.

If you'd have continued with the procedure in step 1 regardless and wiped/reset then it would have booted.

This information is posted all over this forum, quick search would have found it.

If flashfire cannot see the images in your stock Rom then it is probably corrupt in some way. Just because you can see the images it doesn't mean it won't fail a hash check. I would download again or flash a different Rom.

You only need to flash the system.img and boot.img with flashfire.

If you are using iron Rom which by the way works fine with this procedure, as I have tested it, then you need to flash a lollipop kernel. Do not flash a custom kernel or you will trip Knox

You need to wait at least ten minutes or more for boot to complete. If you see the Samsung logo with the sparkles then it's booting.
[Galaxy Tab S General] mathurmatt:
[MENTION=4899305]ashyx[/MENTION] kingroot not working i reflashed to anf8 and still not working downloaded the updated version of kingroot not working it's just check for root status and gives back no root strategy available again and again now i checked with af6, af7 and af8 kingroot is not cutting it from me any idea..... tried i don't even know how many times.
[Galaxy Tab S General] ashyx:
Someone else had success with the desktop version of iroot. Maybe that can work for you?

http://www.3ptechies.com/mobile/android/vroot-rooting-method-for-android.html

http://www.mgyun.com/en/GetVRoot
[Galaxy Tab S General] mathurmatt:
will it trip my knox counter....
[Galaxy Tab S General] Yokobln:
Regarding my journey:

I tried it again with the latest Kingroot 4.1.0.524 on my anf7 galaxy Tab S 8.4 LTE.

I got a

red

circle now with a crying droid smiley saying "Root Failed no strategy now" instead of the usual blue one.

No success, no reboots.

I believe this method will trip the knox efuse, right?

Or is iroot/vroot any different to other rooting methods in that regard?

What makes your solution so unique and appealing to me is the ability to keep knox for warranty reasons.

Will try a T705XXU1ANF8 [AUT] [4.4.2] Switzerland next. Let's see if that changes anything.

Thanks,

Yoko
[Galaxy Tab S General] baristaman:
So many little things are different from this tablet than all the Samsung phones I'm used to. Different key configurations to battery pull, enter download mode, and recovery. This silly hidden.img thing.

It's great to hear that IronROM works. I was left with the impression that only people flashing stock had been reporting success in this thread. I tried to replace the kernel in the IronROM zip because I didn't know at what point a modified kernel would trip Knox. But if you could flash an unmodified zip, and then flash a stock kernel separately, that removes one potential pitfall.

Could you tell me more about your IronROM installation? What version did you use? And more importantly, how did you flash the stock kernel? Did you set Flashfire to do nothing in the boot options after flashing IronROM, then flash the stock kernel, setting the reboot option to download mode?
[Galaxy Tab S General] ashyx:
Flash the stock lollipop kernel with flashfire then flash the system.img from ironrom. I used 2.1.

Remember to wipe data afterwards.
[Galaxy Tab S General] ashyx:
Not as far as I'm aware not according to the person that used it.
[Galaxy Tab S General] Yokobln:
Just as a quick update regarding my rooting attempts...

I downloaded the T705XXU1ANF8_T705AUT1ANF1_AUT (Switzerland) from Samdownloads.de as it is the only anf8 without carrier customization on their site:

(Download section) DL speed is better than other sites btw and I'm just a 4free member...

Odin checked the tar.md5 and I went ahead.

On one of the last steps Odin displayed: Fail!

Apparently the hidden.img file failed to flash or validate. Odin didn't display any further explanation.

After rebooting I was luckily able to flash the T705XXU1ANF7_T705DBT1ANF1_T705XXU1ANF7_HOME.tar.md5 I was coming from.

I don't know how close I came to a hard brick, as mentioned before I'm no expert at all.

I have no idea what went wrong and which anf8 I might be able to flash successfully.

As far as I understand I might have to mess with the pit file if i want to flash certain roms and I don't know if I feel brave/knowledgeable enough to do that...

So right now I'm stuck right where I started off.

Any suggestions are greatly appreciated!

It would be awesome to have root without voiding my warranty.

At least for some others ashyx's method is working.

Good night from Berlin, Yoko
[Galaxy Tab S General] ashyx:
You should have read the post a few posts above yours. I already explained the hidden.img issue, its a known issue on some roms from a different region. When it fails at that point simply reboot your device to recovery and wipe cache. Then just continue with rest of the procedure as normal, everything will be fine.
[Galaxy Tab S General] 3DSammy:
Did something stupid while trying to theme and borked my install. Not finding any other way, although there was likely something I could have done, I use Odin to flash back to Kitkat.

I was working my way through this guides steps, as I'd done before, but at the KingRoot (v4.1.0.249) step, I must have tried near 20 times without any luck. The last time I rooted it took three attempts before gaining root with that version. I had read a post saying there was a new KingRoot version (June 13th v4.1.0.524). I downloaded that version uninstalled the old one and installed the latest one.

This time my SM-T800 rooted in just two attempts. Thought others may want to know.

Having a little bit of sense I had taken a FlashFire backup to my extSD card before I flashed my new theme. At this guides step 12 where you flash the stock Lollipop firmware I instead used Flashfire to restore my latest backup added a clear Dalvik cache and boot into Download mode.

Flashfire performed all those tasks. The last thing I did was use Odin to flash the Lollipop bootloader just as in guide step 13.

This worked great as I'm now back to before my misadventure started, still with Knox 0x000.

If there was a faster way to replace bad system files (could not get device to be recognized using "adb shell"), I sure would like too know. At least I don't have to rebuild from scratch but I do miss having a TWRP recovery which made restoring a complete system far easier than I just did. It would be equally nice if Flashfire's backups could be flashed using Odin.

Thought others may be interested in this information. Especially if someone else suggests better ways of recovering.
[Galaxy Tab S General] ashyx:
Flashfires backups would trip knox if flashed with Odin.

Only stock can be flashed with odin and not trip Knox.

Glad you got sorted. By the way I did post a link to the new version in a previous post.

You won't get adb shell because the stock kernel uses a secure adb. You need a custom kernel for that.
[Galaxy Tab S General] 3DSammy:
That is just the kind of confirmation and info I was looking for. I love keeping my warranty but risky hacking like theming TW settings and Notifications (replaces SystemUI.apk, SecSettings.apk and framework-res.apk) can be a hassle when you don't have a custom recovery. I'm evaluating how I can take the risk and recover faster so your info goes a long way. I'm just learning how to theme the UI so am bound to mess up now and again.

Thanks
[Galaxy Tab S General] DUHAsianSKILLZ:
Btw, themeing framework res leads to bootloop no matter if you modified it or not after compiling and decompiling. If you haven't don't so already, you may need to delete the android manifest XML and meta inf from the themed framework res and copy the meta inf and manifest XML from the original apk back to the themed one. I simply don't mess with framework as its an hassle.
[Galaxy Tab S General] baristaman:
Success! I installed IronROM 2.1 together with the stock T800 kernel using this method. The whole process only took about 15 minutes or so, practice clearly makes perfect. ;)

Knox is still at 0x0000. I've got an OTA notice that IronROM 2.2 is available, I guess I'll see if it includes a new kernel before I install it. Thanks!
[Galaxy Tab S General] ashyx:
Don't ota, it will install a custom kernel!

Congrats on the install. Remember thanks is only a thumb away. ;)
[Galaxy Tab S General] mathurmatt:
[MENTION=4899305]ashyx[/MENTION] thanks (with thumb up button clicked thrice) i rooted my t705 sucessfully without triping knox now i want to install iron rom i have put the stock lollipop frimware zip and iron rom v2.0(only 2.0 availble for t705) in sdcard now can you guide me how to flash with flashfire what i should flash from iron rom v2.0 and what from stock and how to flash the kernel is it the boot.img do i use odin or flash it from the flashfire i didnt get how to flash only the system then bootloader than kernel ????????????? please a little stepwise guide will guide many of us out there.......??????
[Galaxy Tab S General] ashyx:
All you need to do is flash the ironrom zip minus the boot.img with flashfire.
[Galaxy Tab S General] mathurmatt:
i am on kitkat so will it boot properly without boot.img or i have to flash boot.img from lollipop ?????if yes how will i flash it...
[Galaxy Tab S General] ashyx:
Sorry thought you'd already upgraded to lollipop.

See the post before yours. I explained how to install Iron Rom.
[Galaxy Tab S General] alialexali:
sorry i didi not get it

so we dont need your steps more? if we use the flashfire + iron? i dont get it

uccess! I installed IronROM 2.1 together with the stock T800 kernel using this method. The whole process only took about 15 minutes or so, practice clearly makes perfect.

from which your steps we should do the iron?

im on t805 lollipop
[Galaxy Tab S General] baristaman:
Thanks given. :)

Actually, I thought I could have installed the 2.2 OTA and flashed the stock kernel afterwards. But from my reading, it looks like this OTA has an Aroma installer. Flashfire would choke on this, so I won't be installing it. Ironically, the purpose of the Aroma installer here seems to be to give you the choice of a custom kernel or the stock kernel.
[Galaxy Tab S General] ashyx:
The ota is no different to what is already available to install.

If you install the custom boot img it's going to trip Knox regardless.
[Galaxy Tab S General] alialexali:
can u gave hand to make mine like yours? Knox to be at 0x0000

did u make all first page steps?

lollipop t805

thankx
[Galaxy Tab S General] baristaman:
I'm not so sure about that. I thought that IronROM 2.1 had a custom kernel as default, that was the point of my flashing the stock T800 kernel immediately afterwards. So for at least an instant before the stock kernel was installed, a custom boot.img was in place.

---------- Post added at 07:21 AM ---------- Previous post was at 07:14 AM ----------

I followed the instructions in the OP of this thread almost exactly. I downloaded the T800 (in your case, the T805) *stock* kernel zip from the OP of the IronROM thread. I set Flashfire to flash the IronROM zip, and also to reboot to Download mode for the bootloader installation with Odin, as the page 1 instructions said to do. But I did make one change! Before I hit 'Flash!' in Flashfire, I hit the Plus sign again to also add the stock kernel zip. This will make sure IronROM and the stock kernel get flashed together in one session.

You should read some of the Flashfire thread as I did, the user interface takes some getting used to.
[Galaxy Tab S General] Paddiii:
Tried it about 20 times to root my T705 with King Root, but it doesn't work! After trying 5mins it always tell me Root failed, and after this i can't try it again till i delete the data of the App.

It doesn't even try to restart.

Flashed on the oldest available Firmware, ANF7
[Galaxy Tab S General] ashyx:
No you misunderstood what I'm saying.

The ota is the same as what's posted in the development section, so yes it will have a custom kernel.

If you even flash it then it's quite likely Knox will trip. As soon as you start the tablet up, even into download mode the boot loader will check the boot partition for its signature and that's it Knox will trip.
[Galaxy Tab S General] ashyx:
Try the other versions I posted. If they don't work try vroot desktop, someone had success with it.
[Galaxy Tab S General] baristaman:
I actually do agree with you. I would have used Flashfire to install the OTA file as well as the stock kernel, in the same way that I installed IronROM 2.1- that is, if I could have with the Aroma installer. If I had used the native stock recovery to install the OTA, Knox would have been tripped.
[Galaxy Tab S General] ashyx:
You seem to be getting mixed up regarding the Iron Rom ota.

It's not the same as an official ota. It's just a download that has to be flashed with custom recovery. You cannot flash it with stock recovery.
[Galaxy Tab S General] baristaman:
Okay, I stand corrected. I wasn't going to try it anyway.
[Galaxy Tab S General] ashyx:
No worries I wouldn't want you wasting all that effort! Thanks for your feedback. :thumbup:
[Galaxy Tab S General] Yokobln:
Sorry to bother you again, but I am exceedingly puzzled why everything I do seems to fail...

I reflashed the swiss T705XXU1ANF8_T705AUT1ANF1_T705XXU1ANF7_HOME.tar and sure enough Odin failed on the hidden.img

I tried to switch off and/or enter the recovery of the Tab S 84 LTE, but that didn't work either!

I tried all possible key combos but only PWR Vol- and Menu do anything at all and get be back into a "yellow triangle mode" with the message "Firmware upgrade encountered an issue. Please select recovery mode in KIES & try again".

I tried THIS method to shut it down while being connected to a PC and every other key combo I can think of. All it does is shutting down for one second and than immediately coming back with the yellow triangle screen. Of course I also tried to switch to vol+ in that one second "reboot" window to enter recovery so I could wipe the cache...

Nothing works :(

If you have any thoughts on the subject, I would appreciate it a lot.

Thankfully, Yoko
[Galaxy Tab S General] ashyx:
What you are seeing is perfectly normal.

To get into recovery from that mode press and hold POWER + VOL DOWN +HOME.

As soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.

Keep pressed until recovery boots.
[Galaxy Tab S General] Yokobln:
Thank you ashyx - I did exactly that, but I will try it once more tomorrow!

(Perhaps this is a good time to mention that I am generally a tech savvy person and that all my android devices have been rooted, sometimes in more complicated ways... but I feel like a total beginner here) :)

@mathurmatt

I just read the whole thread once again and you seem to be the

only person with a t705

who succeeded in rooting using ashyx' method.

Would you be kind enough to share with us what exact rom version and kingroot version you where using and what else might have contributed to your successful root?

It appears you had my exact same problem in the beginning (anf6, 7, 8) but somehow succeeded in the end.

I would *very* much appreciate your reply!

Thanks again,

Yoko
[Galaxy Tab S General] jumb4531:
Can't downgrade, on 5.0.2

I'm on stock 5.0.2 using SM-T700, no root, knox is untripped. I've tried downgrading to 4.4.2 but it stay on the Samsung boot logo. I've tried to get to recovery to clear cache but I can't enter recovery mode only download mode. Am I doing something wrong? How can I enter recovery mode without the button combos since that doesn't work for me. I am able to reflash back to 5.0.2 in Odin, but not to anything below that.

Thanks.
[Galaxy Tab S General] shayind4:
Try this for Recovery Mode:

1) Power+ Volume down+Home button: to enter first screen for download mode

2) Volume down button

3) Immediately: Power+Volume up+ Home button

Wipe cache in Recovery mode then reboot.
[Galaxy Tab S General] Darelica:
Can i use the bootloader in the first page with a stock rom (T805XXU1BOD1) or i need to find another one? Pls help thank you.
[Galaxy Tab S General] jumb4531:
This worked and now I'm able to get into recovery. I wiped cache but that didn't work, then wiped data/factory and now it boots. So now on 4.4.2 with no knox trip. Now gonna try Ashyx guide. Thanks for the help. You've got the magic touch!
[Galaxy Tab S General] ashyx:
It's all about the timing. I'm expert at it now and can do it every time from any state. :cool:

As stated earlier, after wiping cache, you need to continue with the rest of the procedure, that means including wiping data.

Just add wiping cache as an extra step.
[Galaxy Tab S General] ashyx:
Should be fine.
[Galaxy Tab S General] Darelica:
Can i unroot without tripping knox too? With this method? In case i want to claim the warranty?
[Galaxy Tab S General] ashyx:
Flash the stock Rom with Odin to unroot.
[Galaxy Tab S General] mathurmatt:
Hey YOKO the kingroot is apparently not working for t705 correctly no matter which version you use what i did is following

1. download ioroot and root with it (I used af8 frimware ) , you have to enable developer mode and usb debugging.

2. you will see kinguser app and other chinese apps don't touch them You downloaded the relplace kinguser with superuser from the link is in the op put the mrw in to internel and follow the op commands

3. It will be install supersu if any knox prompts come select cancel.

4. Now don't reboot install flashfire give permissions and flash lollipop or any of your desired frimware. select reboot into download

5. extract lollipop bootloader tar it up if you flashed lollipop and flash it with odin

and you are done..... you have a rooted lollipop or your choice of rom without tripping knox....

---------- Post added at 11:52 AM ---------- Previous post was at 11:48 AM ----------

@ashyx iron rom ZIP for t705 have no system.img it got a extracted system folder any idea how to make it work with flashfire
[Galaxy Tab S General] ashyx:
You need to Remove the boot.img from the zip then use the Flash zip or OTA option in flashfire.
[Galaxy Tab S General] Yokobln:
Wow! Thank you mathurmatt - very kind of you!

Did you use ioroot or iroot?

In case you where using iroot... did you use the android apk or did you download the pc program?

I did not fully unterstand "you will see kinguser app and other chinese apps don't touch them You downloaded the relplace kinguser with superuser from the link is in the op put the mrw in to internel and follow the op commands" but maybe it will be clear when I get there!

-No touching of kinguser and other chinese app - got it!

-You downloaded the relplace kinguser with superuser from the link is in the op put the mrw in to internel and follow the op commands

-->

My understanding

: Just use the "iroot" linked by op in previous post a few pages back, don't use kingroot, than proceed with op's instructions as soon as root is achieved

I don't understand "You downloaded the relplace kinguser with superuser from the link is in the op put the mrw"

I will report back...

Thanks again!

Best regards,

Yoko
[Galaxy Tab S General] idoit:
Can ioroot be used with other devices? Mine is Galaxy Mega SGH-I527M. I was going through the way it does it ->

It will go to stock recovery and enter update from ADB and execute "adb.exe sideload datroot.zip"

Would this trip Knox or soft/hard brick the device? It's on Kitkat 4.4.2.
[Galaxy Tab S General] Tinderbox (UK):
I suppose you know about the mega section, and are just seeing if the tab s guy`s are having any luck rooting.

http://xdaforums.com/galaxy-mega

John.
[Galaxy Tab S General] Paddiii:
Will Root be gone if i do a Factory Reset after rooting? Or will it remain, even if i Reset the device (without flashing a new rom)?
[Galaxy Tab S General] leapinlar:
Root should remain.
[Galaxy Tab S General] idoit:
Oh, is it ioroot we're talking about or iRoot? They're two things.

Yes, I know. I was just wondering if this method is general and can be applied on other devices without being harmful.

[MENTION=4899305]ashyx[/MENTION]: You mentioned

What would happen if I run this code snippet from ioroot on my Mega's stock recovery:

"adb.exe reboot recovery

adb.exe sideload datroot.zip"

I don't need custom ROM or custom recovery, just root.

Looking at the code, I want to know, if by using STOCK recovery and being an absolutely untouched NON-rooted galaxy phone, if the side load update of datroot.zip doesn't finish for any reason, would it harm my phone?

or trip Knox flag or status of system from official to custom etc... ?
[Galaxy Tab S General] Paddiii:
After rooting i need to flash the Lollipop Bootloader. Won't it be necessary to flash the new Lollipop Modem?

Someone got a working T705 BOD5 Bootloader? Tried to put my sboot.bin into a .tar (7zip) file, but i can't flash it with odin :(
[Galaxy Tab S General] ashyx:
It will probably work with the current modem. You can actually flash the modem with flashfire. I know it warns about protected partitions, but it flashes fine.

Don't use 7zip to create tar files, they won't work. You need to use a proper command line tar utility then use the command TAR CVF FILENAME.TAR SBOOT.BIN
[Galaxy Tab S General] idoit:
Well, to answer myself: the adb sideload in Stock recovery said "failed to verify whole-file signature".

I knew that stock recovery only updates if signed by OEM, but I was just wondering how some people in this thread did update datroot.zip with Stock recovery?!!!!!
[Galaxy Tab S General] Darelica:
After doing this method my tm805 cannot detect the sim card
[Galaxy Tab S General] idoit:
Go to Mobile network type in your setting and change it to other options... I had this issue a while ago. Let me know if it solved. Also, enable flight mode and then disable it.
[Galaxy Tab S General] Darelica:
Did not work, restarted, airplane on and off, always insert simcard
[Galaxy Tab S General] Yokobln:
Okay, I read a couple more threads and I am

maybe

getting an idea of why we install the script and system app remover-

If we follow op's method, we only use kingroot as an interim solution to gain root while uninstalling it afterwards and replacing it.

So it seems to me! I might be wrong! But given the potentially unwanted chinese "payload" it might be a good idea to get rid of those helping hands...

My question now: If i am using the iroot - will the script also take care of the

additional

malware parts of iroot, which seem to have been injected into the PC Programm to be transfered to our phones....?

See what I mean (just used AVIRA - nothing fancy):

KingRoot-4.1.0.524t:

C:\Users\xxx\Desktop\KingRoot-4.1.0.524.apk
[0] Archivetype: APK
--> classes.dex
[FOUND] Enthält Erkennungsmuster des [B]SPR/ANDR.DroidRooter.266[/B]-Programmes
[WARNING] Infizierte Dateien in Archiven können nicht repariert werden

iRoot_1.8.5.15285:

C:\Users\xxx\Desktop\iRoot_1.8.5.15285_cid1005_7337ba1e.exe
[0] Archivetype: Inno Setup
[FOUND] Enthält Code des [B]ANDROID/Spy.Agent.RY.Gen-Virus[/B]
[WARNING] Infizierte Dateien in Archiven können nicht repariert werden
[FOUND] Enthält Code des [B]ANDROID/Spy.Agent.GJ.Gen-Virus[/B]
[WARNING] Infizierte Dateien in Archiven können nicht repariert werden
--> {app}\kinguser.zip
[1] Archivetype: ZIP
--> kinguser.apk
[2] Archivetype: APK
--> classes.dex
[FOUND] Enthält Erkennungsmuster des [B]SPR/ANDR.DroidRooter.225-Programmes[/B]
[WARNING] Infizierte Dateien in Archiven können nicht repariert werden

What I don't know / understand: Are we on the safe side anyway because we flash another rom, bootloader & superuser afterwards?

Or do we have to make sure that no unwanted parts of the iroot package remain installed and functional...?

And where would they remain - if so?

Best regards and thank you in advance,

Yoko
[Galaxy Tab S General] ashyx:
Update your modem.
[Galaxy Tab S General] _imperator:
I had the same issue.

Extract the modem.bin from the current lollipop image an flash with oldin.