[up] Update 3: OH6 Update
If you’re looking for root on the latest OH6 update, the UniKernel v8-0002 is reported to be working. We don’t know about the Aou kernel linked below though, chances are good for it to work as well, you may try. Below is download link for UniKernel if you need, along with installation instructions:
[icon name=”download” class=”” unprefixed_class=””] Download UniKernel v8-0002
[icon name=”hand-o-right” class=”” unprefixed_class=””] Installation instructions (KNOX counter will be tripped) [/up]
[up] Update 2: Replaced UniKernel with Aou kernel by Aou, which seems to have fixed the in-call sound and battery life (deep sleep) issues. Thanks D Dougherty for the info. [/up]
[up] Update: Looks like the custom sboot.bin isn’t playing very well, causing issues with Calls and Fingerprint sensor. Take a look at the comments section below for details. [/up]
Oh, yeah! Gotta say that the 3rd party Android development community is pretty awesome. So what if Ping Pong Root was patched, folks over at XDA have now come up with a new method to root the T-Mobile Galaxy S6 that doesn’t trips the KNOX counter.
Exactly, boy! You read it right, developers did something with the sboot on T-Mobile S6, such that flashing a custom kernel to it afterwards doesn’t trips the KNOX counter. Pretty amazing. Let’s just cut talk and get straight to the process for ya all waiting for this day to come.
Downloads
[icon name=”download” class=”” unprefixed_class=””] Download Odin 3.10.6
T-Mobile S6 G920T files:
T-Mobile S6 edge G925T files:
Instructions
NOTE: Make sure you follow the exact process as detailed in the guide below, or else you’ll trip the knox counter.
- Download Odin 3.10.6, Aou kernel, TWRP recovery and SuperSU v2.49 from the downloads section above. And transfer the SuperSU .zip to your phone’s storage while keeping other files on your PC.
- Download the sboot.bin for your T-Mobile S6 (G920T) OR S6 edge (G925T).
└ Be very cautious. Download sboot.bin file meant for your model number only. - Open Odin 3.10.6 on your PC.
- Boot your T-Mobile S6 into Download mode:
- Switch off your phone.
- Press and hold “Home + Power + Volume down” buttons for a few seconds until you see a warning screen.
- Press Volume Up on the warning screen to accept it and boot into Download mode.
- Once your T-Mobile S6 is in download mode, connect it to the PC with a USB cable. The Odin window on PC should detect the phone and show an “Added!!” message.
- Now click on the BL button on Odin window and select the sboot.bin file that you downloaded above (specific for your device model number).
└ Note: DON’T play with any other options on the screen. You’re only required to connect your Galaxy S6 and select the SBOOT file in BL tab. - Click the Start button on Odin and wait for it to finish the process. Once it has finished successfully, you’ll see a pass message on the Odin screen and your device will automatically reboot. You can close Odin now.
- Once phone is booted. Power off and boot into download mode once again.
- Open Odin 3.10.6 again. And this time click on the AP button and select the Aou kernel .tar file that you downloaded above specific for your device.
└ Note: (again) DON’T play with any other options on the screen. - Click the Start button on Odin. Your device automatically reboot once Odin is done with its process. Close Odin.
- Now once again, reboot your your device into Download mode and flash the TWRP recovery .tar similarly like you flashed the kernel in Step 9 above.
- Now boot into TWRP Recovery:
- Switch off your phone.
- Press and hold “Home + Power + Volume Up” buttons for a few seconds and soon as you see Galaxy S6 logo on screen, release the buttons. You’ll boot into TWRP recovery.
- Once in TWRP recovery, flash the SuperSU .zip file that we transferred to your phone in Step 1.
└ In case you aren’t able to flash SuperSU via TWRP, then just grab it from Play Store (link), it might work. - Reboot your phone.
That’s it. Look for SuperSU app when your phone boots. And to verify KNOX status, boot back into download mode and check info in upper left part of the screen. It should look like “KNOX WARRANTY: 0 (0X0000)”
Cheers!
158 responses to “[Update: OH6] Root T-Mobile S6 and S6 edge on 5.1.1 without Tripping KNOX counter”
[…] Root T-Mobile S6 and S6 edge on 5.1.1 without tripping Knox [0x0] […]
Worked…although KNOX Warranty says: 1 (0x0000) still getting the Security Notification. I just need to determine how to disable this notification and I think it would be okay.
Update: Downloaded Package Disabler and disabled SecurityLogAgent (com.samsung.android.securitylogagent) and this stopped the security notifications. All appears to be good to go.
Worked…although KNOX Warranty says: 1 (0x0000) still getting the Security Notification. I just need to determine how to disable this notification and I think it would be okay.
Once again, had to reflash stock 5.1.1. Something…disables making calls with this method. I tried again without disabling any notifications and zero phone at the point of this root method. Thoughts anyone?
Update: Downloaded Package Disabler and disabled SecurityLogAgent (com.samsung.android.securitylogagent) and this stopped the security notifications. All appears to be good to go.
The unikernel doesn’t seem to want to download, Can I use the other kernel?
Once again, had to reflash stock 5.1.1. Something…disables making calls with this method. I tried again without disabling any notifications and zero phone at the point of this root method. Thoughts anyone?
it rooted but phone start flashing a bright white from the screen whenever i tried to wake it… what’s up with that
The unikernel doesn’t seem to want to download, Can I use the other kernel?
T-Mobile G920T 5.1.1…The Sboot engineering reset KNOX (0x0000) but when KNOX was tripped in the first root method earlier on in these posts (e.g. using just the Unikernel) the phone kept record of that first KNOX trip, so it looks like this: KNOX WARRANTY: 1 (0x0000). Most likely why I kept getting the Security Notification. This most resent method using the Sboot broke in call sound and from what I read, also breaks the fingerprint scanner and possibly other features. I am back on stock 5.1.1 unrooted and KNOX still shows a 1 w/ (0x0000). The xda thread is all over the place so I’ll just keep reporting findings here. One step forward two steps back lol.
Well, that’s just bad. Post updated.
Ok so i tried this root method and I’m noticing a few things: 1. When I restart it automatically goes to custom recovery, 2. I think KNOX was tripped because my smart manager keeps saying “security threat detected”, 3. SuperSU keeps flashing something at the bottom of my screen saying something granted permissions.
Is anyone else having these problems??
No, KNOX shouldn’t trip. The Smart Manager app gives that notification because it knows that the system has been tampered with. It’s okay. If you want to get rid of it, follow D Daugherty’s advice; Download and install “Package Disabler” from Play Store and disable the “SecurityLogAgent” (com.samsung.android.securitylogagent)” app.
and also my mobile data keeps turning on by itself and turning off whats up with that?
and also as well my battery life isnt the greatest..
My KNOX counter shows “KNOX WARRANTY VOID: 1 (0X0000)”
Also do you know of any good roms to flash??
Can you also put a Video on how to install xposed framework, i keep getting bootloops on my G920T
@Justin …SU grants permissions to com.tmobile.pr.adapt which is thought to be T-Mobile’s diagnostic stuff in the My T-Mobile App. As stated above, you can disable that security warning but I too also found something is sucking the battery even after disabling “SecurityLogAgent” (com.samsung.android.securitylogagent). The com.tmobile.pr.adapt may be the battery culprit. I denied it permissions and then re-granted superuser because I thought that was what was causing call sound to not work. That said, I am fairly certain this had nothing to do with the no call sound when I had it disabled however, I did not have it in the denied status long enough to determine if this is what is causing the massive battery drain.
it rooted but phone start flashing a bright white from the screen whenever i tried to wake it… what’s up with that
com.tmobile.pr.adapt is the battery culprit? i notice it keeps flashing every few seconds at the bottom of my screen, so i should just deny it in SU
I’m not having any issues with call sound or even making a call
Try denying permissions for a spell…see if your battery lasts. I hadn’t had permissions denied for long enough to determine if it was indeed the culprit or not. Maybe download a battery app to see if it gives you any more detail on the process that is draining it, if not com.tmobile.pr.adapt that is.
You may want to add com.tmobile.pr.adapt to the other one you disable in Package Disabler, I think you get 5 free disables with the unpaid version. Even though the permissions are denied, doesn’t mean it won’t still try to run…all of this on the theory that this is the battery culprit of course.
just turn off SU ad that anoying pop out will dissapear also when you do that android pay will work again however samsung pay still wont work if you want to do other options with your phone just activate SU again
Oh ok thanks, well I just went back to stock such as yourself so I’ll try it again in a day or so.. Especially when I know xposed framework is ready with no problems, and also a good ROM to flash.
T-Mobile G920T 5.1.1…The Sboot engineering reset KNOX (0x0000) but when KNOX was tripped in the first root method earlier on in these posts (e.g. using just the Unikernel) the phone kept record of that first KNOX trip, so it looks like this: KNOX WARRANTY: 1 (0x0000). Most likely why I kept getting the Security Notification. This most resent method using the Sboot broke in call sound and from what I read, also breaks the fingerprint scanner and possibly other features. I am back on stock 5.1.1 unrooted and KNOX still shows a 1 w/ (0x0000). The xda thread is all over the place so I’ll just keep reporting findings here. One step forward two steps back lol.
Well, that’s just bad. Post updated.
Ok so i tried this root method and I’m noticing a few things: 1. When I restart it automatically goes to custom recovery, 2. I think KNOX was tripped because my smart manager keeps saying “security threat detected”, 3. SuperSU keeps flashing something at the bottom of my screen saying something granted permissions.
Is anyone else having these problems??
No, KNOX shouldn’t trip. The Smart Manager app gives that notification because it knows that the system has been tampered with. It’s okay. If you want to get rid of it, follow D Daugherty’s advice; Download and install “Package Disabler” from Play Store and disable the “SecurityLogAgent” (com.samsung.android.securitylogagent)” app.
and also my mobile data keeps turning on by itself and turning off whats up with that?
and also as well my battery life isnt the greatest..
My KNOX counter shows “KNOX WARRANTY VOID: 1 (0X0000)”
Also do you know of any good roms to flash??
Can you also put a Video on how to install xposed framework, i keep getting bootloops on my G920T
@Justin …SU grants permissions to com.tmobile.pr.adapt which is thought to be T-Mobile’s diagnostic stuff in the My T-Mobile App. As stated above, you can disable that security warning but I too also found something is sucking the battery even after disabling “SecurityLogAgent” (com.samsung.android.securitylogagent). The com.tmobile.pr.adapt may be the battery culprit. I denied it permissions and then re-granted superuser because I thought that was what was causing call sound to not work. That said, I am fairly certain this had nothing to do with the no call sound when I had it disabled however, I did not have it in the denied status long enough to determine if this is what is causing the massive battery drain.
ok now im having call sound issues..
com.tmobile.pr.adapt is the battery culprit? i notice it keeps flashing every few seconds at the bottom of my screen, so i should just deny it in SU
I’m not having any issues with call sound or even making a call
Try denying permissions for a spell…see if your battery lasts. I hadn’t had permissions denied for long enough to determine if it was indeed the culprit or not. Maybe download a battery app to see if it gives you any more detail on the process that is draining it, if not com.tmobile.pr.adapt that is.
You may want to add com.tmobile.pr.adapt to the other one you disable in Package Disabler, I think you get 5 free disables with the unpaid version. Even though the permissions are denied, doesn’t mean it won’t still try to run…all of this on the theory that this is the battery culprit of course.
just turn off SU ad that anoying pop out will dissapear also when you do that android pay will work again however samsung pay still wont work if you want to do other options with your phone just activate SU again
Oh ok thanks, well I just went back to stock such as yourself so I’ll try it again in a day or so.. Especially when I know xposed framework is ready with no problems, and also a good ROM to flash.
ok now im having call sound issues..
I just went back to Stock 5.1.1 I’ll try the root later when I know that there will be no hiccups
I just went back to Stock 5.1.1 I’ll try the root later when I know that there will be no hiccups
This method (link below) fixed the Call sound issue…apparently it doesn’t fix the fingerprint scanner but I personally don’t use it so I’m not too worried. So far this method has been the most stable and I haven’t experienced any issues. Check it out: http://forum.xda-developers.com/showpost.php?p=61744127&postcount=68
Cool. Updated the post and replaced UniKernel with Aou kernel. Thanks for the updates 🙂
Thanks D!
I’ll try it later on
Do you know anything about Xposed Framework??
I dont have root or supersu after using the Aou kernel..
Sorry man! I forgot to include TWRP recovery and SuperSU zip. Downloads and instructions updated for the same now. Btw, you’ve normal T-Mobile S6 or S6 edge? If normal S6 (G920T), then do let us know if the TWRP recovery linked above for it works or not.
I have to Galaxy S6 NOT the Edge
Well, can you try the Sprint S6 TWRP recovery linked above on your T-Mobile S6?
Nothing is working for me now, I’ve tried several times but to no avail.
I’m going back to stock, I dont know whats going on but nothing seems to work now.
Can you help?? I tried the Sprint image but I dont think it worked
Try this TWRP recovery: https://dl.twrp.me/zeroflte/twrp-2.8.7.1-zeroflte.img.tar
I have that one alrerady, I dont know whats going on maybe Im doing something wrong..
I use ODIN for sboot, then the kernel, and finally for the twrp recovery.
and it doesnt work..
I just did everything according to instructions but I STILL dont have root or superSU.. -_-
Well, UniKernel is your only option then, for now. I’ll let you know if I come across a working TWRP recovery for G920T on 5.1.1
The G925T TWRP recovery did indeed work for me on G920T and I was able to boot to it. I was unable however to install SuperSU using TWRP, I decided to just go get it from the Play Store, then downloaded Root Checker and SU kicked in just fine. All is running well.
i got TWRP recovery to work BUT I still DONT have root access.. What gives
should the Kernel be MD5 OR tar??
It worked for me as named… g920t_of6_aou_kernel_vi.tar.md5 …so I presume it is an md5