Database Users

[Q] Any one test SuperSU OTA survival mode in s5?

has any1 tried to preserve root in an OTA update for 900F?
Moreover, is there a way to find out if the OTA will flash kernel or not?

wajiman said:
has any1 tried to preserve root in an OTA update for 900F?
Moreover, is there a way to find out if the OTA will flash kernel or not?
Click to expand...
Click to collapse
Best way to keep root is to flash the new updated factory rom with Mobile Odin Pro and keep root with nearly 100% certainty. Survival mode may or may not work after an OTA, Chainfire doesn`t guarantee it.

gee2012 said:
Best way to keep root is to flash the new updated factory rom with Mobile Odin Pro and keep root with nearly 100% certainty. Survival mode may or may not work after an OTA, Chainfire doesn`t guarantee it.
Click to expand...
Click to collapse
Damn. Mobile Odin Does not work. Phone got stuck in 2nd recovery boot. Had to flash using PC Odin

wajiman said:
Damn. Mobile Odin Does not work. Phone got stuck in 2nd recovery boot. Had to flash using PC Odin
Click to expand...
Click to collapse
What rom did you flash, everything above NE2 cannot be rooted with Towelroot anymore. If you flashed NG2 only CF Auto Root will root the device atm.

gee2012 said:
What rom did you flash, everything above NE2 cannot be rooted with Towelroot anymore. If you flashed NG2 only CF Auto Root will root the device atm.
Click to expand...
Click to collapse
That's the blunder I did.i flashed NG2

wajiman said:
That's the blunder I did.i flashed NG2
Click to expand...
Click to collapse
You can always flash a NE2 rom and root with TR again and try the survival mode in superSU Pro to keep root. It may fail but the chances of succes are greater.

gee2012 said:
You can always flash a NE2 rom and root with TR again and try the survival mode in superSU Pro to keep root. It may fail but the chances of succes are greater.
Click to expand...
Click to collapse
What about the KNOX being tripped? ?

wajiman said:
What about the KNOX being tripped? ?
Click to expand...
Click to collapse
No risk as you as long as you flash stock firmware/OTA`s afaik.

gee2012 said:
No risk as you as long as you flash stock firmware/OTA`s afaik.
Click to expand...
Click to collapse
So old boot loader flashing will not be an issue?

wajiman said:
So old boot loader flashing will not be an issue?
Click to expand...
Click to collapse
Read this http://androidforums.com/samsung-galaxy-s4/788644-knox-security-locked-bootloader-new-firmwares.html and judge for yourself. I`am not sure wether flashing an older rom will or can overwrite the new bootloader and if it leads to a faillure of the flash or tripping KNOX. Logicaly i would say option 1 but as said not 100% sure. Look on Google for more info before you try it.

gee2012 said:
Read this http://androidforums.com/samsung-galaxy-s4/788644-knox-security-locked-bootloader-new-firmwares.html and judge for yourself. I`am not sure wether flashing an older rom will or can overwrite the new bootloader and if it leads to a faillure of the flash or tripping KNOX. Logicaly i would say option 1 but as said not 100% sure. Look on Google for more info before you try it.
Click to expand...
Click to collapse
Thanks. Do you know which bootloaders are unlocked as of now if any?

wajiman said:
Thanks. Do you know which bootloaders are unlocked as of now if any?
Click to expand...
Click to collapse
Most bootloaders except some US models like Verizon and AT&T are unlocked afaik, The problem with the NG2 and newer bootloader is that it cannot be replaced atm by an older bootloader.

gee2012 said:
Most bootloaders except some US models like Verizon and AT&T are unlocked afaik, The problem with the NG2 and newer bootloader is that it cannot be replaced atm by an older bootloader.
Click to expand...
Click to collapse
Thanks. Actually I have 2 S5.i first tested on my one s5 and stopped to do it on my second. So any bootloader below NG2 can be replaced?

wajiman said:
Thanks. Actually I have 2 S5.i first tested on my one s5 and stopped to do it on my second. So any bootloader below NG2 can be replaced?
Click to expand...
Click to collapse
Wait a minute, just flashed NE2 over my NG2 and lets see what happened Realy curious if KNOX is tripped.
---------- Post added at 10:10 PM ---------- Previous post was at 09:56 PM ----------
Downgrade flash succeeded, KNOX still 0x0, bootloader downgraded from NG2 to NE2! You need to untick Auto Reboot in Odin before the flash because it doesn`t boot without a full wipe in recovery, so after the flash pull the battery, wait 10 seconds and reboot into recovery, data factory reset and reboot. Done

gee2012 said:
Wait a minute, just flashed NE2 over my NG2 and lets see what happened Realy curious if KNOX is tripped.
---------- Post added at 10:10 PM ---------- Previous post was at 09:56 PM ----------
Downgrade flash succeeded, KNOX still 0x0, bootloader downgraded from NG2 to NE2! You need to untick Auto Reboot in Odin before the flash because it doesn`t boot without a full wipe in recovery, so after the flash pull the battery, wait 10 seconds and reboot into recovery, data factory reset and reboot. Done
Click to expand...
Click to collapse
So this means we can downgrade. Thanks a ton for testing mate

wajiman said:
So this means we can downgrade. Thanks a ton for testing mate
Click to expand...
Click to collapse
I didn`t have a single issue, i expect (but cannot guarantee) that other users will not have a problem either

gee2012 said:
I didn`t have a single issue, i expect but cannot guarantee that other users will not have a problem either
Click to expand...
Click to collapse
Is it possible to flash NG2 firmware using NE2 bootloader and kernel for rooting purpose?

wajiman said:
Is it possible to flash NG2 firmware using NE2 bootloader and kernel for rooting purpose?
Click to expand...
Click to collapse
I expect not and i wouldn`t try it either as they are not compatible and will prevent the device from booting.

gee2012 said:
I expect not and i wouldn`t try it either as they are not compatible and will prevent the device from booting.
Click to expand...
Click to collapse
Thanks for your time and final question, right now iam too on NE2 on my second S5, are there any significant changes in NG2?

wajiman said:
Thanks for your time and final question, right now iam too on NE2 on my second S5, are there any significant changes in NG2?
Click to expand...
Click to collapse
For one its a lot faster and snappier than NE2 and also look in this thread http://forum.xda-developers.com/showthread.php?t=2715487&page=49 for other changes.

[share] about knox , root and odin firmware [please read before posting]

Hey friends:
im a normal member and everything above is only sharing
So you may get upset because of this thread
but i'll make things clear, everytime i open Q&A forum i see repeated questions everywhere
so here ill put some repeated answers about those stuff above
1. knox: well when you buy a new galaxy s5 the knox state will be 0*0 , but when you root your phone, flash custom recovery,custom kernel or custom rom this will trip knox and the knox state will be 0*1 and your warrenty will be void.
P.S: flashing firmware via odin will not trip knox
- so if you want to root without tripping knox you can go to this website : http://www.towelroot.com install apk by pressing the sign.
you will be able to root your phone quick from the phone itself but only if your phone on firmware from 3rd june or less
or your phone will not be rooted, but you can also root it by chainfire method from here: http://forum.xda-developers.com/showthread.php?t=2696537
you can also use mobile odin to flash firmwares but be carefull to be sure about your phone model.
you can install the app from playstore or from this thread: http://forum.xda-developers.com/showthread.php?t=1347899
P.S: firmwares can be downloaded from here : http://www.sammobile.com
i hope you Moderators understand me and dont get angry or close this thread because im only sharing and thought it will help my friends and the new forum members.
and at last im a member and i have the right to post what it usefull to xda community
hope that i helped.

Is is possible to use any Odin (I have 3 or 4 on my downloads) to flash stock over unlocked O2?

swipermusic said:
Is is possible to use any Odin (I have 3 or 4 on my downloads) to flash stock over unlocked O2?
Click to expand...
Click to collapse
to flash firmware you can use computer odin v3.09 and then extract the md5 file from the firmware zip and put it in AP in odin (and maybe different version of odin says PDA)

?
What about "System Status", in recovery I have a "System Status: Custom", knox 0x0 though, I'm rooted and use Xposed, what does this mean? how can I reverse it to "OFFICIAL", is this important when it comes to warranty?
THANKS! :highfive: :good: :fingers-crossed:

aguarello said:
What about "System Status", in recovery I have a "System Status: Custom", knox 0x0 though, I'm rooted and use Xposed, what does this mean? how can I reverse it to "OFFICIAL", is this important when it comes to warranty?
THANKS! :highfive: :good: :fingers-crossed:
Click to expand...
Click to collapse
well i think its not so important.
and look in settings>>about>>states
is it official or custom?

Galaxy_Guy said:
well i think its not so important.
and look in settings>>about>>states
is it official or custom?
Click to expand...
Click to collapse
Custom

aguarello said:
Custom
Click to expand...
Click to collapse
means your system has been modified and no OTA's will be available

?
wajiman said:
means your system has been modified and no OTA's will be available
Click to expand...
Click to collapse
I don't care about OTA's, but how does this impacts warranty? Can be reversed to "Official?
Thanks man I really appreciate your help.

aguarello said:
What about "System Status", in recovery I have a "System Status: Custom", knox 0x0 though, I'm rooted and use Xposed, what does this mean? how can I reverse it to "OFFICIAL", is this important when it comes to warranty?
THANKS! :highfive: :good: :fingers-crossed:
Click to expand...
Click to collapse
Use Triangle Away by chainfire, the system status will be reverted to Official.

This Thread - Fully redundant

pda4g said:
This Thread - Fully redundant
Click to expand...
Click to collapse
but its usefull for some new S5 users, its not necessary to be usefull for you.

?
Luckzao said:
Use Triangle Away by chainfire, the system status will be reverted to Official.
Click to expand...
Click to collapse
Will this be permanent or the status will be just "faked"?
thanks! :victory:

aguarello said:
Will this be permanent or the status will be just "faked"?
thanks! :victory:
Click to expand...
Click to collapse
AFAIK it will be fake, the only way to officially convert it to original is, uninstall root reboot and then reinstall root and SuperSU to user directory, not to system. This method worked for Roms prior to 3rd June.

wajiman said:
AFAIK it will be fake, the only way to officially convert it to original is, uninstall root reboot and then reinstall root and SuperSU to user directory, not to system. This method worked for Roms prior to 3rd June.
Click to expand...
Click to collapse
Ughhhh should have know that before updating and installing SuperSU to system... So no way to revert it if ROM is posterior to 3rd June? Even flashing official ROM again without root? :crying:
THANKS!

aguarello said:
Ughhhh should have know that before updating and installing SuperSU to system... So no way to revert it if ROM is posterior to 3rd June? Even flashing official ROM again without root? :crying:
THANKS!
Click to expand...
Click to collapse
Yes you can downgrade, i downgraded from NG2 to NE2 myself without problems. Just flash the NE2 rom with Odin and data factory reset afterwards. Then use TR to root again.

gee2012 said:
Yes you can downgrade, i downgraded from NG2 to NE2 myself without problems. Just flash the NE2 rom with Odin and data factory reset afterwards. Then use TR to root again.
Click to expand...
Click to collapse
Downgrade is possible without tripp knox,without problems?

AEkiz said:
Downgrade is possible without tripp knox,without problems?
Click to expand...
Click to collapse
Yes, KNOX is still 0x0 for me after the downgrade and the bootloader is downgraded to the NE2 one.

gee2012 said:
Yes, KNOX is still 0x0 for me after the downgrade and the bootloader is downgraded to the NE2 one.
Click to expand...
Click to collapse
Thanks for your reply
maybe I'll try tomorrow

gee2012 said:
Yes you can downgrade, i downgraded from NG2 to NE2 myself without problems. Just flash the NE2 rom with Odin and data factory reset afterwards. Then use TR to root again.
Click to expand...
Click to collapse
THANKS! To downgrade you just have to flash the NE2 rom? No more files? Sorry I'm kind of a noob

aguarello said:
THANKS! To downgrade you just have to flash the NE2 rom? No more files? Sorry I'm kind of a noob
Click to expand...
Click to collapse
Yes, i only flashed the older firmware without a extra PIT file or bootloader file. Make sure to untick Auto Reboot first in Odin, after the flash pull the battery, wait for 10-20 seconds, boot into recovery and do a data factory reset and then the phone should boot normal and both the firmware and bootloader are downgraded to NE2 and KNOX remains 0x0. At least it worked for me this way and i expect it to work for others the same way

Need root for Verizon SM-T337V Update 4.4.4

Ostensibly, srsroot supports rooting SM-T337V build KTU84P.T337VVRU2ANK1 Android version 4.4.4. It actually doesn't, and it doesn't appear that any other exploit exists. My business needs this. I'm not sure if this is right place to post, but we can definitely offer a bounty if this exploit does not yet exist.

Meditato said:
Ostensibly, srsroot supports rooting SM-T337V build KTU84P.T337VVRU2ANK1 Android version 4.4.4. It actually doesn't, and it doesn't appear that any other exploit exists. My business needs this. I'm not sure if this is right place to post, but we can definitely offer a bounty if this exploit does not yet exist.
Click to expand...
Click to collapse
Sorry just to eliminate the obvious, have you tried towelroot, and if that doesn't work, have you tried the newer method of flashing a kernel from an older build, rooting with towelroot, and flashing the latest kernel?

I've tried Towelroot- it does not support this update.
ODINing an old image over a new one is generally a bad idea- on Samsung devices, it has a nasty tendency of disabling the network devices.
Sent from my Nexus 5 using XDA Free mobile app

Meditato said:
I've tried Towelroot- it does not support this update.
ODINing an old image over a new one is generally a bad idea- on Samsung devices, it has a nasty tendency of disabling the network devices.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Not an entire firmware image, just a .tar of an older kernel, that's how I rooted my Galaxy S4 Active and my Tab 4 SM-T530NU

thisisapoorusernamechoice said:
Not an entire firmware image, just a .tar of an older kernel, that's how I rooted my Galaxy S4 Active and my Tab 4 SM-T530NU
Click to expand...
Click to collapse
Do you know of any links of this for the SM-T337V? Also, are you sure that the exploits in towelroot, srsroot, cfroot, etc are just kernel exploits and not dependent on other utilities or parts of the userspace? We just tried to flash the 4.4.2 kernel back over the 4.4.4 update and ended up almost bricking a test tablet.
To be clear, our tablets are already the latest update, so we have to find some way of rooting them that doesn't involve just rooting the previous version and then just never updating it.

Meditato said:
Do you know of any links of this for the SM-T337V? Also, are you sure that the exploits in towelroot, srsroot, cfroot, etc are just kernel exploits and not dependent on other utilities or parts of the userspace? We just tried to flash the 4.4.2 kernel back over the 4.4.4 update and ended up almost bricking a test tablet.
To be clear, our tablets are already the latest update, so we have to find some way of rooting them that doesn't involve just rooting the previous version and then just never updating it.
Click to expand...
Click to collapse
OK I don't think you see what I'm getting at. I understand you don't want to do a wholesale downgrade to a previous version, I get that. But the exploit in towelroot works on the older version's kernel. So, correct me if I'm wrong, but the kernel file is simply boot.img inside the tar.md5 file, which you can open as an archive in winrar or 7zip. So what I'm suggesting, and someone correct me if I'm wrong, but I'm pretty sure this is what they're doing to root the Tab 4 10.1, Galaxy S4, and Galaxy S5. So while on the latest SM-T337V firmware, extract the boot.img from the older firmware, create a tar just for the boot.img (may or may not need linux or at least cygwin to do that, honestly don't know for sure), flash that older kernel tar in Odin, quickly root your tablet with towelroot, then flash the current kernel. Sorry but I'm not sure if you want to install SuperSU before or after that last step.
But that's how the latest Samsung builds are being rooted

deleted

thisisapoorusernamechoice said:
OK I don't think you see what I'm getting at. I understand you don't want to do a wholesale downgrade to a previous version, I get that. But the exploit in towelroot works on the older version's kernel. So, correct me if I'm wrong, but the kernel file is simply boot.img inside the tar.md5 file, which you can open as an archive in winrar or 7zip. So what I'm suggesting, and someone correct me if I'm wrong, but I'm pretty sure this is what they're doing to root the Tab 4 10.1, Galaxy S4, and Galaxy S5. So while on the latest SM-T337V firmware, extract the boot.img from the older firmware, create a tar just for the boot.img (may or may not need linux or at least cygwin to do that, honestly don't know for sure), flash that older kernel tar in Odin, quickly root your tablet with towelroot, then flash the current kernel. Sorry but I'm not sure if you want to install SuperSU before or after that last step.
But that's how the latest Samsung builds are being rooted
Click to expand...
Click to collapse
We've tried this. As stated in the other thread about this OTA update, this doesn't appear to work. In our case, ODIN failed with _xmitdata error. Not even flashing the new kernel works.

Whelp, with the bootloader locked, downgrading not working, and Verizon/Samsung unwilling to help, it looks like we're SOL.

How to t337 rom install on t332?

Meditato said:
Whelp, with the bootloader locked, downgrading not working, and Verizon/Samsung unwilling to help, it looks like we're SOL.
Click to expand...
Click to collapse
I'm in the same boat as you but with the TM-537V. Also tried the downgrade kernel, towelroot, upgrade method and it failed. Are you still looking or have you given up on this?

any news?
any update on this? anyone figure out how to root the sm-t337v 4.4.4???

Meditato said:
Whelp, with the bootloader locked, downgrading not working, and Verizon/Samsung unwilling to help, it looks like we're SOL.
Click to expand...
Click to collapse
M,
are you still looking into this ? do you have or can you post/link the current bootimg in question ?
if so do you posess a tab that can be used as a guinea-pig?
I am trying to sort out an approach to a recovery for the sm-t337a and maybe tinkering with this might get
some answers to both problems at the same time.
thanks.
m
what i am thinking, ketut's degas bootimg tools seem to work unpacking and repacking a signed stock bootimg for the sm-t23xx without modification, from what i can get the signatures relates to sizes of portions of the bootimg. I have a thought that some combination of modifying the
img in question and changing compression, or just managing to change that i byte that makes secure=1 secure=0 might be a start
but need someone who can and is willing to experiment.
recovery.img too if you could.
also run in terminal [no need for root] the following
ls /proc/config.gz
i just want to see if it's there
my last thought is, if you have a device to "throw away" is to try flat out over-writing the locked bootloader with one that isn't?

evrkusd said:
I'm in the same boat as you but with the TM-537V. Also tried the downgrade kernel, towelroot, upgrade method and it failed. Are you still looking or have you given up on this?
Click to expand...
Click to collapse
Hi , now @sub77 upload new TWRP 2860 for all models , including T537V too . You may try to install it and in the success case , you may try to install superSU from recovery . Goodluck

repey6 said:
Hi , now @sub77 upload new TWRP 2860 for all models , including T537V too . You may try to install it and in the success case , you may try to install superSU from recovery . Goodluck
Click to expand...
Click to collapse
Thanks. I'm not sure if it's tested for 537V though! Did you see anyone saying that they used it for 537V or that the new version supports 537V?

evrkusd said:
Thanks. I'm not sure if it's tested for 537V though! Did you see anyone saying that they used it for 537V or that the new version supports 537V?
Click to expand...
Click to collapse
No , of course . It's new .

repey6 said:
No , of course . It's new .
Click to expand...
Click to collapse
I just tried flashing TWRP 2.8.6.0 to my SM-T537V with Odin and it failed

uroboch said:
I just tried flashing TWRP 2.8.6.0 to my SM-T537V with Odin and it failed
Click to expand...
Click to collapse
Did you try using the flashify app to install the TWRP img file? That's how I've been installing TWRP to my Tab 4

thisisapoorusernamechoice said:
Did you try using the flashify app to install the TWRP img file? That's how I've been installing TWRP to my Tab 4
Click to expand...
Click to collapse
I did not. I will give it a shot and let you know the outcome. I wont be able to use it as it requires root.

thisisapoorusernamechoice said:
Did you try using the flashify app to install the TWRP img file? That's how I've been installing TWRP to my Tab 4
Click to expand...
Click to collapse
Were you able to do this on an LTE Tab 4? or which one?

Rooting Verizon SM-T537V

So as i dont see the model # listed for CF root or towelroot, im guessing i need to odin custom recovery and flash SU or is there another way out there im not finding?:fingers-crossed:

Karl said:
So as i dont see the model # listed for CF root or towelroot, im guessing i need to odin custom recovery and flash SU or is there another way out there im not finding?:fingers-crossed:
Click to expand...
Click to collapse
I was able to use towelroot to get access on this device. I haven't been able to get TWRP onto it though, or get a Rom on either.
---------- Post added at 10:19 AM ---------- Previous post was at 10:07 AM ----------
Karl said:
So as i dont see the model # listed for CF root or towelroot, im guessing i need to odin custom recovery and flash SU or is there another way out there im not finding?:fingers-crossed:
Click to expand...
Click to collapse
I was able to use towelroot to get access on this device. I haven't been able to get TWRP onto it though, or get a Rom on either.

Hmm how did you get towel root to work
Sent From HTC One M9

Karl said:
Hmm how did you get towel root to work
Sent From HTC One M9
Click to expand...
Click to collapse
If this is like a lot of Samsung devices then what's going on is the early firmware (NE2) was rootable with towelroot, but the more recent one (NK1) is not. Check your settings > about tablet to see which build number you're on (I'm assuming it's NK1). The most immediate solution would be to just downgrade the firmware, root, and stay with that (disable update notifications/freeze the updater app).
However, if you know what you're doing, it's only the kernel that needs to be changed. So extract the kernel file (boot.img) from both firmware files and make a tar file for each boot.img. Flash the older kernel, root with towelroot, then flash the newer kernel, and voila you're rooted on the latest build. Your call

thisisapoorusernamechoice said:
If this is like a lot of Samsung devices then what's going on is the early firmware (NE2) was rootable with towelroot, but the more recent one (NK1) is not. Check your settings > about tablet to see which build number you're on (I'm assuming it's NK1). The most immediate solution would be to just downgrade the firmware, root, and stay with that (disable update notifications/freeze the updater app).
However, if you know what you're doing, it's only the kernel that needs to be changed. So extract the kernel file (boot.img) from both firmware files and make a tar file for each boot.img. Flash the older kernel, root with towelroot, then flash the newer kernel, and voila you're rooted on the latest build. Your call
Click to expand...
Click to collapse
do you have the NE2 firm ?

Karl said:
do you have the NE2 firm ?
Click to expand...
Click to collapse
I really wish I had a better link for you but it can be found: here

thisisapoorusernamechoice said:
I really wish I had a better link for you but it can be found: here
Click to expand...
Click to collapse
thanks,i saw it on sammobile but you gotta pay to DL

have you used this to make a tar? http://forum.xda-developers.com/showthread.php?t=2446269

Karl said:
have you used this to make a tar? url
Click to expand...
Click to collapse
I have not tried, sorry

I did this with the t337a, if you want I could take a shot at it. I have no way of making sure it works though. Let me know if you are interested or if anyone would be willing to test the kernel.

I own the Tab S. It was released after towelroot was patched. So recently when Kingroot update their root method and such, we now can root with kingroot on KitKat ANK1 firmwares and not trip Knox. Of course people who owned att devices said it worked and some with Verizon said it didn't work. I mean its worth a try if anyone wants to try kingroot.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461

Rooted! SM-T537V
Kingroot worked

DUHAsianSKILLZ said:
I own the Tab S. It was released after towelroot was patched. So recently when Kingroot update their root method and such, we now can root with kingroot on KitKat ANK1 firmwares and not trip Knox. Of course people who owned att devices said it worked and some with Verizon said it didn't work. I mean its worth a try if anyone wants to try kingroot.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Click to expand...
Click to collapse
Hi ive got kingroot goin and it says its rooted but when u restart it, its gone.

N910PVPS4COK1 100% Stock kernel ROOT. :)

Thanks to @Chainfire and his method to root on Android 6.0 Marshmallow, Samsung devices on 5.1.1 can now enjoy root with a completely stock kernel with SE Android "enforcing." I will be updating this to support "systemless" root, meaning you will be able to achieve root without modifying a your system partition thus making the system believe you are "Official" and is the first step towards being able to accept OTA updates while being rooted.
Instructions:
TAR: Flash with Odin, install SuperSU via TWRP or Google Play.
ZIP: Flash with TWRP, install SuperSU via TWRP or Google Play.
TAR: Download Stock OK1 Kernel with Root support (TAR)
ZIP: Download Stock OK1 Kernel with Root support (ZIP)

freeza said:
Thanks to @Chainfire and his method to root on Android 6.0 Marshmallow, Samsung devices on 5.1.1 can now enjoy root with a completely stock kernel with SE Android "enforcing." I will be updating this to support "systemless" root, meaning you will be able to achieve root without modifying a your system partition thus making the system believe you are "Official" and is the first step towards being able to accept OTA updates while being rooted.
I'll upload shortly.
Click to expand...
Click to collapse
You are a beast man!!!!! Way to go!!!!!

Man you are a beast!!!! Now get a note 5 already haha jk

freeza said:
I will be updating this to support "systemless" root, meaning you will be able to achieve root without modifying a your system partition thus making the system believe you are "Official" and is the first step towards being able to accept OTA updates while being rooted.
Click to expand...
Click to collapse
This bit in particular sounds really interesting!

Freebroe you are the shiz. Keep on doing good work for the community.

Awesome! Will this be odin-able or a zip to flash?

SWEET!! Can't wait for the download!

I downloaded the cok1 update can i still flash this

freeza said:
Thanks to @Chainfire and his method to root on Android 6.0 Marshmallow, Samsung devices on 5.1.1 can now enjoy root with a completely stock kernel with SE Android "enforcing." I will be updating this to support "systemless" root, meaning you will be able to achieve root without modifying a your system partition thus making the system believe you are "Official" and is the first step towards being able to accept OTA updates while being rooted.
I'll upload shortly.
Click to expand...
Click to collapse
Does this mean Android pay and such will work with root?

Anyone heard any news on this?

Uploaded.

I have COG5 Rom. Can I flash this kernel?

Dang that was fast. Awesome work!

Was about to flash this through odin but realized I took the OK1 update. Is this still safe to flash??? I'm gonna hold off before pulling the trigger just in case. Glad I checked!

@BB said:
Was about to flash this through odin but realized I'm took the OK1 update. Is this still safe to flash??? I'm gonna hold off before pulling the trigger just in case. Glad I checked!
Click to expand...
Click to collapse
Same here...but I think that is the reason for this fix.

Always-Learnin said:
Same here...but I think that is the reason for this fix.
Click to expand...
Click to collapse
Good point ...

freeza said:
Uploaded.
Click to expand...
Click to collapse
Master Freeza, what is the correct selection to use in Odin, to flash this? Sorry for the newbie question.

ya for android pay. but dang we loose xposed framework ability right. caused its not deoxed?

Always-Learnin said:
Master Freeza, what is the correct selection to use in Odin, to flash this? Sorry for the newbie question.
Click to expand...
Click to collapse
AP...

jhill110 said:
AP...
Click to expand...
Click to collapse
Thank you.
Sent from my SM-N910P using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 06:29 PM ----------
OK, I attempted to do this... I Odined using the AP option as indicated above. I installed SuperSU and Root Checker Pro. SuperSU and Root Checker Pro show "no binaries" installed. I'm wondering what I did wrong? I have redone this about 4 times.