Develop Bugs

[Q] Debating root, but have a few KNOX related questions (P600)

Hello all! I have just acquired a Note 10.1 2014 Edition! However, the one thing that's sort of bothering me is the lack of root. I also have a Note 3 that's rooted and it's amazing, so I would like that experience on my new tablet as well. My only fear is KNOX; Because my model is the Wi-Fi (P600) edition, there is no version of a root that keeps the KNOX flag at 0x0. With that said, I have a few questions:
1. If I root my tablet, is there any chance of me later on upgrading the system software of my device (Say, Lollipop later on when it's released)? I know OTA is out of the question when rooted.
2. Other than the KNOX applications, does the KNOX flag limit the usage of my device in any other way (for example, Miracast, HDCP, etc.)?
3. How limited am it to software changes on my phone with the KNOX flag enabled (I'm not talking apps, but system changes like bootloader, firmware, recovery, etc. Essentially, would I be able to install a custom bootloader and/or recovery after my KNOX flag is set to 0x1?)?
I have tried looking up the answers to these questions, but the sources I found have confused me. I'm not worried about my warranty either.

I also like to see those questions answered

computerlife22 said:
1. If I root my tablet, is there any chance of me later on upgrading the system software of my device (Say, Lollipop later on when it's released)? I know OTA is out of the question when rooted.
2. Other than the KNOX applications, does the KNOX flag limit the usage of my device in any other way (for example, Miracast, HDCP, etc.)?
3. How limited am it to software changes on my phone with the KNOX flag enabled (I'm not talking apps, but system changes like bootloader, firmware, recovery, etc. Essentially, would I be able to install a custom bootloader and/or recovery after my KNOX flag is set to 0x1?)?
Click to expand...
Click to collapse
1.) Odds are we will see 5.0-based ROMs before an OTA update for our specific device, so don't worry. On a previous tablet, I went from 3.2 to an OTA 4.0, then rooted and flashed a 4.1 ROM (CM10). The great part is, Toshiba never pushed anything past a horribly buggy 4.0 for it. Not only can you upgrade your software in the future, you'll have better options, more options, and (in all liklihood) earlier access.
2.) Not that I know of. I'm running all of my apps perfectly and have only had one feature not work on an Xposed module (hide WiFi on Wanam Xposed module), though I can't attribute that to KNOX in any way.
3.) I've never tried installing a custom bootloader or recovery, so unfortunately I can't answer that with any degree of certainty.

computerlife22 said:
1. If I root my tablet, is there any chance of me later on upgrading the system software of my device (Say, Lollipop later on when it's released)? I know OTA is out of the question when rooted.
Click to expand...
Click to collapse
Yes. You can always upgrade by downloading firmware via a site like sammobile.com and flashing that via ODIN, or using Kies to automatically download the latest firmware and flash it to your device. Either of those methods will result in you losing root. If a root method exists for the updated firmware, you can re-root.
computerlife22 said:
2. Other than the KNOX applications, does the KNOX flag limit the usage of my device in any other way (for example, Miracast, HDCP, etc.)?
Click to expand...
Click to collapse
No. Screen mirroring (and possibly other features, but that's the only one I know of) will refuse to work if you have a custom recovery installed. You can get around this by reflashing stock recovery, or making an edit to a system file.
computerlife22 said:
3. How limited am it to software changes on my phone with the KNOX flag enabled (I'm not talking apps, but system changes like bootloader, firmware, recovery, etc. Essentially, would I be able to install a custom bootloader and/or recovery after my KNOX flag is set to 0x1?)?
Click to expand...
Click to collapse
I don't believe there are any custom bootloaders available, but you can flash a custom ROM/recovery easily.

Decided to root... but how?
Okay, thanks guys. I've decided that I would like to take the plunge and root my tablet. However, I'm confused on how I should. What method should I use to root my tablet? I'm running KitKat 4.4.2 version NI1.
Would this still work?
http://forum.xda-developers.com/showthread.php?t=2490805

Here you go, step by step.
There are also YouTube videos on rooting our tablets (albeit with different files for an earlier version) that show you the process. I like using them when rooting devices so I can visualize the steps and actually see how it's done rather than just reading about it.

Android Pay compatible ROMs

Hey guys, I'm currently on xtreolite deodexed v2.3, Android Pay will not work for me due to the root level access, some people have been able to get around this by disabling root in SuperSU and installing but that didn't work for me. Can those on different ROMs please try and report back? Does stock + root work?

I think you need to flash stock, install and setup pay, then root

^^ this! Above poster is right,

Actually, after rooting again android pay will not process transactions. At least mine failed today after rooting again when I tried at McDonald's.

Is it checking the KNOX counter or just the phone being rooted?

Just if it is rooted

Aren't there xposed modules to hide root?

[Q] Help with getting Android Pay to work on rooted Note 4 with CM12.1

I need help with getting Android Pay to work on my rooted Note 4 because I keep getting the Android Pay cannot be used message. I do know that Android Pay does does block rooted users so I've tried various workarounds with none of them working.
I tried the method where I installed Root Cloak and added Android Pay, Google Play Service and Google Service Framework to apps it hides root from and cleared the data from those 3 apps. I also installed No Device Check since from what I saw, Android Pay does use SafetyNet to check your devices firmware whether it has been modified or not. Does anybody have any ideas of how to get this to work without losing root access or having to go back to stock?

androidpay
ThatGuy94 said:
I need help with getting Android Pay to work on my rooted Note 4 because I keep getting the Android Pay cannot be used message. I do know that Android Pay does does block rooted users so I've tried various workarounds with none of them working.
I tried the method where I installed Root Cloak and added Android Pay, Google Play Service and Google Service Framework to apps it hides root from and cleared the data from those 3 apps. I also installed No Device Check since from what I saw, Android Pay does use SafetyNet to check your devices firmware whether it has been modified or not. Does anybody have any ideas of how to get this to work without losing root access or having to go back to stock?
Click to expand...
Click to collapse
In the chainfire superuser app disable superuser, then try and add a creditcard, go back to superuser reenable

Iceburn1 said:
In the chainfire superuser app disable superuser, then try and add a creditcard, go back to superuser reenable
Click to expand...
Click to collapse
I'm running CM12.1 if that matters. Would it work even with that or would I have to be running stock?

Im on stock however rooted using beastmode and twrp recovery. I disabled supersu and was able to add my credit cards however when i go to use it for example at a vending machine at school i get a message that says something like, Amex**** is unable to be used at this time and the same goes for my discover.
any ideas how to fix?

http://forum.xda-developers.com/showpost.php?p=62981452&postcount=55

SM-T707A Root w/ Kingo, Switch to SuperSU on 4.4.2

*Updated 3/2017 to include same for LL updated SM-T707A*
For anyone else who has the SM-T707A (tab s 8.4" AT&T LTE version) -
Issues with this tablet:
1. Upgrading to Lollipop - seems that without an actual AT&T sim card installed, you're not going to be able to upgrade from 4.4.2 (cannot download the OTA update, and I haven't been able to find a download of the firmware online ANYWHERE).
2. Locked Bootloader - possible to carrier unlock for any compatible GMS carrier (I'm using mine with a T-mobile sim card), but seems that there is no way to unlock the bootloader/install a custom recovery.
(**NOTE: DO NOT TRY AND INSTALL TWRP OR USE THE UNLOCK/RECOVERY UTILITIES FOR THE SM-T705 ... while it seems like they would effectively be the same devices, both have exynos cpu and identical specs...I have tested out the odin-flashable methods from the development section that are for the SM-T705, and THESE WILL SOFT BRICK YOUR DEVICE. A HUGE ISSUE, SINCE THE STOCK FIRMWARE IS REALLY REALLY REALLY DIFFICULT TO FIND..)
SILVER LININGS:
1. Even if you have to stay on 4.4.2, you should be able to root with Kingo Root.
2. If you are rooted with Kingo on 4.4.2, and want to switch to SuperSU app instead of the KingoRoot one, you can try this (worked for me):
**Update 3/2017 - this will also work on LL updated SM-T707A
1. Install SuperSU app through google play store (regular install...NOT an update via recovery). This means you will now have TWO Superuser apps installed on your phone. Only the Kingo Superuser will have the authority to grant SU permissions at this point. Now open SuperSU and make sure it is installed. It should ask you to update the SU binary (you won't be able to yet, but make sure you get the prompt).
2. Download a terminal emulator app, or enable usb debugging in dev options, connect phone to pc, and open an adb shell.
3. Follow the instructions for switching to SuperSU available on android forums (search for "bakageta" +" supersu to kingo" +"android forums" ).
4. Download @bakageta's zip file and put on your sd card. Then open your terminal emulator or adb shell as root (type "su" + press enter) and run the first command: "# ./step0.sh" Remember to leave your terminal emulator open when you move on to the next step (same goes for your adb window).
5. Uninstall the Kingo Root apps (your tablet will then ~likely~ auto-reboot, closing the terminal emulator...DON'T PANIC, THIS IS OK.)
6. After your tablet boots back up, you should still have root**, but now your Superuser app will be SuperSU.
**UPDATE (3/2017, running the LL updated SM-T707A) If you are doing this on LL, you may need to also run the subsequent bakageta script, "# ./step1.sh" after the initial reboot to get SuperSU root access.
--> If anyone here knows how I can make a backup of the firmware I currently have installed (rooted stock 5.0.1) that can be used as a restore image via odin, please let me know! I'd gladly upload the file for anyone who is having trouble unbricking their devices, since the stock files are so insanely difficult to find for this particular variant of the tab s.
--Thanks to @Kingxteam
--Thanks to @bakageta for the alcatel scripts

see PM

chixvicious, did you ever managed to get those backups? I got a soft-bricked 707A and i also cant find the stock roms anywhere

PAragao said:
chixvicious, did you ever managed to get those backups? I got a soft-bricked 707A and i also cant find the stock roms anywhere
Click to expand...
Click to collapse
still not allowed to post links, but files can be found at dropbox dot com/s/mjobo2sfa53x2dv/T707AUCU1ANH9_T707AATT1ANH9_4.4.4_USA_4Files.rar?dl=0

Okay so I can confirm Galaxy Tab S 707a 8.4" LTE can be rooted in 4.4.2 with Kingo. It's goofy like kingo is , but it worked unfortunately that's not quite enough for myself as six axis never communicates w. Stock annnnd tmobile sucks and are being jerks can't use it without special plan so I'm putting my WiFi board back in. If any one wants rooted 4.4.2 unlocked motherboard......useless wasted tech here, all thanks to software restrictions.

updated for anyone else playing with these / whom it may concern if they ever google up this old ass device , I confirm on 4.4.2 707a I have successfully root with kingo and them using SUPERSUME apk I have swtiched it fully to SuperSU . Also using online nandroid backup with the 805 LTE variant patch I was able to get a full backup. I think I'm in decent shape for experimentation as I'm on the lowest order firmware and hopefully , not sure but hopefully if anything goes badly i can just update to newer firmware. Going to attempt using SAFESTRAP recovery next

SuperlativeB said:
updated for anyone else playing with these / whom it may concern if they ever google up this old ass device , I confirm on 4.4.2 707a I have successfully root with kingo and them using SUPERSUME apk I have swtiched it fully to SuperSU . Also using online nandroid backup with the 805 LTE variant patch I was able to get a full backup. I think I'm in decent shape for experimentation as I'm on the lowest order firmware and hopefully , not sure but hopefully if anything goes badly i can just update to newer firmware. Going to attempt using SAFESTRAP recovery next
Click to expand...
Click to collapse
I still have 2 of these and am constantly disappointed at how much development there is for every other variants but this one.

I got safestrap in , was able to reboot and see it but no luck due to se enforcing , I tried everything to get it to permissive but no luck. I went back to my WiFi model ha , oh well. Have to look for a 705 that has unlocked boot / better firmware

pm me if you still have that!
SuperlativeB said:
Okay so I can confirm Galaxy Tab S 707a 8.4" LTE can be rooted in 4.4.2 with Kingo. It's goofy like kingo is , but it worked unfortunately that's not quite enough for myself as six axis never communicates w. Stock annnnd tmobile sucks and are being jerks can't use it without special plan so I'm putting my WiFi board back in. If any one wants rooted 4.4.2 unlocked motherboard......useless wasted tech here, all thanks to software restrictions.
Click to expand...
Click to collapse
PM me if you still have that! I randomly have an extra (shattered screen) Tab S 8.4" without a motherboard, and would play around with trying to unlock the bootloader on it if I had a mobo to put in it!
Thanks!

SuperlativeB said:
I got safestrap in , was able to reboot and see it but no luck due to se enforcing , I tried everything to get it to permissive but no luck. I went back to my WiFi model ha , oh well. Have to look for a 705 that has unlocked boot / better firmware
Click to expand...
Click to collapse
I could help get this permissive on kitkat, but not LL or MM.

ashyx said:
I could help get this permissive on kitkat, but not LL or MM.
Click to expand...
Click to collapse
What are your thoughts ? It's def still kitkat , but I've tried init'd stuff and all sorts crap. If i got permissive i could possibly get safestrap to boot and then try out roms intended for the regular LTE variant. It is just kind of useless for me as T-mobile it's device Id as tablet so they lock it out then if i just wanted to use it WiFi the TouchWiz stuff kills remote controls like six axis and stuff. Id prob use it daily if i could get past device id pickups / safestrap a way into better rom

anyone have the 6.0.1 firmware?

Root + Android Pay. What does OEM Unlock do?

I rooted my phone only so I could use AdAway. So once I update the hosts file with AdAway, technically I can disable root and only enable root once a week or so to re-run AdAway and update the hosts file again correct?
So I want to use Android Pay too... I keep reading that if I disable root in SuperSU it'll work, but my Android Pay flat out rufuses to work.
Only other thing I can think of is disabling OEM Unlock. What does that even do? I'm currently running custom recovey (TWRP).
Does OEM Unlock need to remain enabled? Could that prevent Android Pay working when SuperSU root is disabled?
Thanks

If your root method modified /system/ then you will never be able to use Android Pay as it checks this. Even systemless root stopped working with the August security patch. It's why I didn't root my Note 7 when I got it because I figured this out on the 6P. Sad but true.

Is there a way to un-root and re-root quickly? I disabled root in SuperSU but it doesn't help.
All I really want to do is block ads via the host file with adaway (which is how it works right?) And I can enable root every time I want to update the ad block list.
Thanks for reply

I found a few ways to do it on other sections of this forum but they seemed tedious and I haven't really looked since the August patch flarked everything up for folks who want AP. Sorry. I wish I could answer.