Database Users

[Q] Proper Rooting and SafeStrap Process NC4

Okay so I've been browsing through the forums and been reading up on this phone (even contacted Samsung about info on unlocking the bootloader, no go on that. Had to try though)
Basically I want to know what's the proper procedure for installing custom roms on an NC4 device 4.4.2
Things I know:
Bootloader is unlockable at the moment (hoping for some good news in the future)
Towelroot for rooting
Safestrap for recovery
(Both just download and install the apk)
Things I don't know:
Kernel?
Somebody said I had to flash the NC2 kernel via Odin?
Knox?
What is this? What trips it?
I did see the list of guides and I did read and watch all the necessary ones, but the date on those are from 2 years ago and I just need confirmation on if I'm going about this right.
Any help is appreciated. I thank you in advance for taking the time to read this.
Please excuse my lack of knowledge, this is my first Samsung device.
Also, what would happen if somebody were to flash the DE stock files via Odin to a Retail N3?

If you upgraded to NC4 or NK1, you're stuck until Samsung unlocks the bootloader or Verizon stops lying to their customers. There is no root available after upgrade at this moment in time.

Dravekx said:
If you upgraded to NC4 or NK1, you're stuck until Samsung unlocks the bootloader or Verizon stops lying to their customers. There is no root available after upgrade at this moment in time.
Click to expand...
Click to collapse
I didn't upgrade to NC4, it came like this.

rdar_93 said:
I didn't upgrade to NC4, it came like this.
Click to expand...
Click to collapse
That sucks. You can't do anything about it at the moment. I was forced to upgrade and lost root. Custom ROMs won't be available to you or me until someone finds a hole to unlock the bootloader. Welcome to our Verizon Note 3 rooting dilemma.

mirrin said:
You do not have a dev version so cm 11 or 12 is a far off dream you won't get. Your bootloader is locked there is no unlock.
You are in luck nc4 is root able using towel root then safe strap and the unified firmware. You will need odin and a pc for flashing a few things the NK1 modem towel root and the unified firmware. Pick a rom from the development thread i suggest jasmine 1.x or eclipse.
Click to expand...
Click to collapse
Copied from another post I had.
I don't know much about the device which is why I'm trying to find out.

Dravekx said:
That sucks. You can't do anything about it at the moment. I was forced to upgrade and lost root. Custom ROMs won't be available to you or me until someone finds a hole to unlock the bootloader. Welcome to our Verizon Note 3 rooting dilemma.
Click to expand...
Click to collapse
I actually just got root on my phone, I felt adventurous and installed towelroot and voila it rooted my phone.
I should state that I'm on 4.4.2, not 4.4.4.
Checked root status with Titanium Backup Pro, everything checked out a-okay.

rdar_93 said:
Okay so I've been browsing through the forums and been reading up on this phone (even contacted Samsung about info on unlocking the bootloader, no go on that. Had to try though)
Basically I want to know what's the proper procedure for installing custom roms on an NC4 device 4.4.2
Things I know:
Bootloader is unlockable at the moment (hoping for some good news in the future)
Towelroot for rooting
Safestrap for recovery
(Both just download and install the apk)
Things I don't know:
Kernel?
Somebody said I had to flash the NC2 kernel via Odin?
Knox?
What is this? What trips it?
I did see the list of guides and I did read and watch all the necessary ones, but the date on those are from 2 years ago and I just need confirmation on if I'm going about this right.
Any help is appreciated. I thank you in advance for taking the time to read this.
Please excuse my lack of knowledge, this is my first Samsung device.
Also, what would happen if somebody were to flash the DE stock files via Odin to a Retail N3?
Click to expand...
Click to collapse
Ahhhh... You're good to go then! Find a good custom ROM and follow the instructions. Whatever you do.. Don't upgrade!
rdar_93 said:
I actually just got root on my phone, I felt adventurous and installed towelroot and voila it rooted my phone.
I should state that I'm on 4.4.2, not 4.4.4.
Checked root status with Titanium Backup Pro, everything checked out a-okay.
Click to expand...
Click to collapse

Dravekx said:
Ahhhh... You're good to go then! Find a good custom ROM and follow the instructions. Whatever you do.. Don't upgrade!
Click to expand...
Click to collapse
Lol I still need clarification on the Kernel information that I don't know about.
What do I need to flash?
Do I flash it after I install a custom rom or before?

rdar_93 said:
Lol I still need clarification on the Kernel information that I don't know about.
What do I need to flash?
Do I flash it after I install a custom rom or before?
Click to expand...
Click to collapse
My opinion: If you're doing a custom kernel, make sure it works with whatever ROM you're flashing. I suggest sticking with the stock kernel* until you get the hang of things OR do a little research and learn a bit before you attempt anything. There's a lot of forums with details and help here. I've installed kernels before and after installing ROMs with little or zero problems, but I'm more of a dabbler than a professional.
I would suggest backing up your current setup in case you need to reflash. That's a definite.

Dravekx said:
My opinion: If you're doing a custom kernel, make sure it works with whatever ROM you're flashing. I suggest sticking with the stock kernel* until you get the hang of things OR do a little research and learn a bit before you attempt anything. There's a lot of forums with details and help here. I've installed kernels before and after installing ROMs with little or zero problems, but I'm more of a dabbler than a professional.
I would suggest backing up your current setup in case you need to reflash. That's a definite.
Click to expand...
Click to collapse
Lol that doesn't really answer the question. I hope somebody sees it and clears it up for me

rdar_93 said:
Lol that doesn't really answer the question. I hope somebody sees it and clears it up for me
Click to expand...
Click to collapse
The kernel can't be changed...although it can be "tuned" if you have root.
http://forum.xda-developers.com/showthread.php?p=58813428
Sent from my Note 3 via Tapatalk

Still hoping somebody helps me out and posts a short but precise guide to install a custom rom on 4.4.2 NC4
I don't want to end up bricking my device on the first try. I've been there already and it sucks lol

rdar_93 said:
Still hoping somebody helps me out and posts a short but precise guide to install a custom rom on 4.4.2 NC4
I don't want to end up bricking my device on the first try. I've been there already and it sucks lol
Click to expand...
Click to collapse
It really depends on the ROM, there is no set guide for all ROMs.
Did you install busybox? I like using busybox on rails. Just download the app and click install.
Download the safestrap apk (3.75 B04) and install that, open it and install recovery.
I'm currently running Clean ROM. I am on NC4. I downloaded the rom, and moved it to my SD card. I rebooted to safestrap, wiped data, cache and dalvik then installed the ROM to the stock slot. Then, following the instructions for Clean ROM, I rebooted to download mode from recovery and flashed the NC2 Kernel with odin.
The main thing is to read the installation instructions for the particular ROM you want to flash.
Don't forget to use Titanium backup to freeze SDM app (I think that's what its called) so your phone will stop trying to update.
---------- Post added at 05:29 PM ---------- Previous post was at 05:23 PM ----------
rdar_93 said:
Still hoping somebody helps me out and posts a short but precise guide to install a custom rom on 4.4.2 NC4
I don't want to end up bricking my device on the first try. I've been there already and it sucks lol
Click to expand...
Click to collapse
If you're at all proficient with Odin it is really REALLY hard to brick these phones.

BladeRunner said:
It really depends on the ROM, there is no set guide for all ROMs.
Did you install busybox? I like using busybox on rails. Just download the app and click install.
Download the safestrap apk (3.75 B04) and install that, open it and install recovery.
I'm currently running Clean ROM. I am on NC4. I downloaded the rom, and moved it to my SD card. I rebooted to safestrap, wiped data, cache and dalvik then installed the ROM to the stock slot. Then, following the instructions for Clean ROM, I rebooted to download mode from recovery and flashed the NC2 Kernel with odin.
The main thing is to read the installation instructions for the particular ROM you want to flash.
Don't forget to use Titanium backup to freeze SDM app (I think that's what its called) so your phone will stop trying to update.
---------- Post added at 05:29 PM ---------- Previous post was at 05:23 PM ----------
If you're at all proficient with Odin it is really REALLY hard to brick these phones.
Click to expand...
Click to collapse
Thanks man, I was supposed to update this thread saying that I got through with the proper procedure for installing Jasmine Rom
Although I was running Eclipse before, and I wanted to try going back to stock but it just got stuck on the Verizon splash screen
I'm thinking it's because I had the NC2 kernel active when I should have gone back to the NC4 kernel
I looked for a NC4 kernel to flash but I only saw the modems and tar files, so not knowing if those were the same as kernels I decided to just try Jasmine. So far, I like it.
I have crazy battery drain though. I think it's because I'm running it in Slot 1

just picked up a verizon note 3 android 4.4.2 NC4
one of the very first posts above says you cant do anything on NC4 and then another post says NC4 is ok but just not android 4.4.4
NC4 is the latest update as of this writing isnt it?
what can actually be done with this vzw note 3 on android 4.4.2 NC4?
non dev edition of course
what about knox?
if rooting can be done with this phone on this OS is there any safe way not to trip knox?

en11gma said:
just picked up a verizon note 3 android 4.4.2 NC4
one of the very first posts above says you cant do anything on NC4 and then another post says NC4 is ok but just not android 4.4.4
NC4 is the latest update as of this writing isnt it?
what can actually be done with this vzw note 3 on android 4.4.2 NC4?
non dev edition of course
what about knox?
if rooting can be done with this phone on this OS is there any safe way not to trip knox?
Click to expand...
Click to collapse
I'd be happy to answer your questions
If you have an NC4 device that's running 4.4.2, you are able to gain root access and install safestrap recovery on your device. However, if the android version is 4.4.4, you cannot root or install safestrap.
NC4 is just our last build number, but there are two versions I think, the 4.4.2 and the 4.4.4. In the 4.4.4, they blacklisted every single compatible kernel that could work on the device. They forgot to do it in the 4.4.2 version, that's why we're able to gain root.
On our NC4 4.4.2 Verizon Note 3, we can root, install safestrap recovery and install a very limited amount of roms from the non developer edition selection on the XDA forums.
Rooting via towelroot, to my knowledge, does not trip knox. However, installing safestrap recovery does. But if you're worried about your warranty being voided, I wouldn't panic too much because with our bootloader being locked, it is very easy to flash the original Stock Verizon files through Odin to go straight back to factory settings so it looks like if you just pulled it out the box. The knox code would be reset and you would have a device that looked like if it has never been rooted or modified.

rdar_93 said:
I'd be happy to answer your questions
If you have an NC4 device that's running 4.4.2, you are able to gain root access and install safestrap recovery on your device. However, if the android version is 4.4.4, you cannot root or install safestrap.
NC4 is just our last build number, but there are two versions I think, the 4.4.2 and the 4.4.4. In the 4.4.4, they blacklisted every single compatible kernel that could work on the device. They forgot to do it in the 4.4.2 version, that's why we're able to gain root.
On our NC4 4.4.2 Verizon Note 3, we can root, install safestrap recovery and install a very limited amount of roms from the non developer edition selection on the XDA forums.
Rooting via towelroot, to my knowledge, does not trip knox. However, installing safestrap recovery does. But if you're worried about your warranty being voided, I wouldn't panic too much because with our bootloader being locked, it is very easy to flash the original Stock Verizon files through Odin to go straight back to factory settings so it looks like if you just pulled it out the box. The knox code would be reset and you would have a device that looked like if it has never been rooted or modified.
Click to expand...
Click to collapse
Safestrap does not trip knox.

mjh68 said:
Safestrap does not trip knox.
Click to expand...
Click to collapse
Thanks. I must have tripped mine somehow cause my device says "custom" when booting.
I'm guessing it might be Xposed but I'm not too sure.

rdar_93 said:
Thanks. I must have tripped mine somehow cause my device says "custom" when booting.
I'm guessing it might be Xposed but I'm not too sure.
Click to expand...
Click to collapse
It will say custom, but that isn't tripping knox. Custom can be removed with the triangle away app. Custom just gets flagged like you were saying by changing the recovery , but it doesn't trip the knox counter.

mjh68 said:
It will say custom, but that isn't tripping knox. Custom can be removed with the triangle away app. Custom just gets flagged like you were saying by changing the recovery , but it doesn't trip the knox counter.
Click to expand...
Click to collapse
Then I must be confused about what knox really is.
What is "Knox" then?

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?

Root new out of the box NK2 updated galaxy s5?

I'm trying to help a family member root their new phone. The most up to date guide I've found here is for the previous update (NI2) and I haven't seen anything for the Verizon NK2 version. Is it still possible to root this version? If so do you know where I can find out how?

worf65 said:
I'm trying to help a family member root their new phone. The most up to date guide I've found here is for the previous update (NI2) and I haven't seen anything for the Verizon NK2 version. Is it still possible to root this version? If so do you know where I can find out how?
Click to expand...
Click to collapse
It's the same thing, doesn't matter what the starting version is. You still have to downgrade to NGC

ldeveraux said:
It's the same thing, doesn't matter what the starting version is. You still have to downgrade to NGC
Click to expand...
Click to collapse
So just downgrade the kernal to NCG, root, then update the kernal using Odin? Skipping the step about flashing the OTA since its already updated?

worf65 said:
So just downgrade the kernal to NCG, root, then update the kernal using Odin? Skipping the step about flashing the OTA since its already updated?
Click to expand...
Click to collapse
No not at all. Just go read the thread it's sticked at the top, or at least it should be

worf65 said:
So just downgrade the kernal to NCG, root, then update the kernal using Odin? Skipping the step about flashing the OTA since its already updated?
Click to expand...
Click to collapse
I believe that flashing the kernel would work but you would have to work your way through a lot of FC's. I normally flash a full tar but you having a brand new phone, this probably isn't necessary but it is what I normally do ( below is the tar file I use. It is a complete internal wipe to a like new phone on NGC). Root with towelroot, download SuperSU from play store, update the binaries and reboot. I would suggest safestrap. You would need to download from play store then install busybox first. Then install safestrap and install its recovery.
https://www.androidfilehost.com/?fid=23610159112652178

Tulsadiver said:
I believe that flashing the kernel would work but you would have to work your way through a lot of FC's. I normally flash a full tar but you having a brand new phone, this probably isn't necessary but it is what I normally do ( below is the tar file I use. It is a complete internal wipe to a like new phone on NGC). Root with towelroot, download SuperSU from play store, update the binaries and reboot. I would suggest safestrap. You would need to download from play store then install busybox first. Then install safestrap and install its recovery.
https://www.androidfilehost.com/?fid=23610159112652178
Click to expand...
Click to collapse
I'm pretty familiar with how rooting the S5 works before updates as that is how I did mine (froze the updater and didn't have time to figure out how to safely update). What I am confused about is what I do when coming from a later software version, the guide is even called "Safely Upgrade and Root..." not how to downgrade and root, and the guide to update to lollipop seems to require already being rooted.

worf65 said:
I'm pretty familiar with how rooting the S5 works before updatesj as that is how I did mine (froze the updater and didn't have time to figure out how to safely update). What I am confused about is what I do when coming from a later software version, the guide is even called "Safely Upgrade and Root..." not how to downgrade and root, and the guide to update to lollipop seems to require already being rooted.
Click to expand...
Click to collapse
I told you how to root, downgrade, root, then upgrade. Plus, you need to read down a little further. See notes #4
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546

Tulsadiver said:
I told you how to root, downgrade, root, then upgrade. Plus, you need to read down a little further. See notes #4
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
Click to expand...
Click to collapse
Ok, I had found that guide before getting this new phone for my phone but didn't look at it again since I remembered that it had to be rooted already and was assuming I had to root on an earlier version hence the confusion.

Its understandable why people without root don't read it or at least don't read on down.

New Update - G925FXXU1AODG

On Vodafone UK got the following OTA about 131MB (G925FXXU1AODG), checked Sammobile also posted there, but also branded Vodafone.
Not noticed any difference.

According to gsmarena there ia a noticeable improvement to the phone's performance (at least for S6)
www.gsmarena.com/samsung_galaxy_s6_is_receiving_a_new_502_ota_in_europe-news-12195.php

night clock fix by any chance?

So far cannot discern any changes - will play around more and see.

Can someone make sure the kernel build date is before 3th May?
Otherwise I'd not install this update if you want to root without tripping knox.
According to the S6 Forum the new root method only works for sure with kernels before 3th May.

whitepaw said:
Can someone make sure the kernel build date is before 3th May?
Otherwise I'd not install this update if you want to root without tripping knox.
According to the S6 Forum the new root method only works for sure with kernels before 3th May.
Click to expand...
Click to collapse
According to this http://www.android-hilfe.de/origina...ock-rom-22-04-15-g925fxxu1aodg-5-0-2-vd2.html build date is Apr 22

whitepaw said:
Can someone make sure the kernel build date is before 3th May?
Otherwise I'd not install this update if you want to root without tripping knox.
According to the S6 Forum the new root method only works for sure with kernels before 3th May.
Click to expand...
Click to collapse
...so you want ever use old software..?

freaksamael said:
According to this http://www.android-hilfe.de/origina...ock-rom-22-04-15-g925fxxu1aodg-5-0-2-vd2.html build date is Apr 22
Click to expand...
Click to collapse
Thank you. Then it should be save to install.
Alex-V said:
...so you want ever use old software..?
Click to expand...
Click to collapse
No. Once you got root you can flash custom Roms and then you can even update the Kernel (maybe...might not be needed so). Only for rooting the unsafe kernel is needed.
There might be the possibility to downgrade without tripping knox via Odin but I'm not quiet sure.

whitepaw said:
Thank you. Then it should be save to install.
No. Once you got root you can flash custom Roms and then you can even update the Kernel (maybe...might not be needed so). Only for rooting the unsafe kernel is needed.
There might be the possibility to downgrade without tripping knox via Odin but I'm not quiet sure.
Click to expand...
Click to collapse
OK..for the not tripping Knox..you have some info..? thanks

Alex-V said:
OK..for the not tripping Knox..you have some info..? thanks
Click to expand...
Click to collapse
You mean rooting without tripping knox?
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
They are working on a s6e version and in the thread he says it should work with all kernel before may 3. You won't be able to flash a recovery but on the s5 it was possible with mobile odin to flash custom Roms without tripping knox. I assume it's the same for the s6.
Downgrade without tripping knox should be possible with official firmwares via odin. It worked for me on the s5. Not sure about the s6. That's why I wanted to make sure the kernel is still exploitable.

whitepaw said:
You mean rooting without tripping knox?
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
They are working on a s6e version and in the thread he says it should work with all kernel before may 3. You won't be able to flash a recovery but on the s5 it was possible with mobile odin to flash custom Roms without tripping knox. I assume it's the same for the s6.
Downgrade without tripping knox should be possible with official firmwares via odin. It worked for me on the s5. Not sure about the s6. That's why I wanted to make sure the kernel is still exploitable.
Click to expand...
Click to collapse
thanks man ? sounds promising

Heads up for anyone attempting to flash it on another version.
Attempted to flash the Vodafone 925F(ODG) version on my W8. System only. No boot/radio/csc. The version boots fine even on older kernels, no fc's even without a data wipe. Sadly no in-call audio on W8 and it will be the same for TMO people as well.
For others with any 925F, you should be able to download the full image from SamMobile and then extract the system.img and boot.img. Convert them to ODIN flashable packages and then flash the tar files individually with AP mode in ODIN to upgrade. If you're using TWRP, you can then boot in and flash SuperSU and gain root back. Unsure when kernel sources would be released for the update.
The Vodafone image had 0 bloat on first boot so it should be the same for others.
Edit*
Please make a backup still to be safe. Also have a full flashable image ready incase flashing goes bad.

evonc said:
Heads up for anyone attempting to flash it on another version.
Attempted to flash the Vodafone 925F(ODG) version on my W8. System only. No boot/radio/csc. The version boots fine even on older kernels, no fc's even without a data wipe. Sadly no in-call audio on W8 and it will be the same for TMO people as well.
For others with any 925F, you should be able to download the full image from SamMobile and then extract the system.img and boot.img. Convert them to ODIN flashable packages and then flash the tar files individually with AP mode in ODIN to upgrade. If you're using TWRP, you can then boot in and flash SuperSU and gain root back. Unsure when kernel sources would be released for the update.
The Vodafone image had 0 bloat on first boot so it should be the same for others.
Edit*
Please make a backup still to be safe. Also have a full flashable image ready incase flashing goes bad.
Click to expand...
Click to collapse
I will try that..thanks my friend..
I still have my normal firmware download so I'm save.. lol..

evonc said:
Heads up for anyone attempting to flash it on another version.
Attempted to flash the Vodafone 925F(ODG) version on my W8. System only. No boot/radio/csc. The version boots fine even on older kernels, no fc's even without a data wipe. Sadly no in-call audio on W8 and it will be the same for TMO people as well.
For others with any 925F, you should be able to download the full image from SamMobile and then extract the system.img and boot.img. Convert them to ODIN flashable packages and then flash the tar files individually with AP mode in ODIN to upgrade. If you're using TWRP, you can then boot in and flash SuperSU and gain root back. Unsure when kernel sources would be released for the update.
The Vodafone image had 0 bloat on first boot so it should be the same for others.
Edit*
Please make a backup still to be safe. Also have a full flashable image ready incase flashing goes bad.
Click to expand...
Click to collapse
Please what do you mean by individual?
Also after flashing, will it trigger knox?
Do i need to be rooted to flash?
I have already combine both file and used tar package to make it flashable with odin

okolobaccess said:
Please what do you mean by individual?
I have already combine both file and used tar package to make it flashable with odin
Click to expand...
Click to collapse
I'm still download the firmware..lol..and works..?

okolobaccess said:
Please what do you mean by individual?
Also after flashing, will it trigger knox?
Do i need to be rooted to flash?
I have already combine both file and used tar package to make it flashable with odin
Click to expand...
Click to collapse
Take the ODG zip and create an Odin flashable tar package of only System.img and boot.img.
Once an image comes out for your carrier, you can update bootloader/radio if you choose.
Not sure if it will trigger KNOX. If you're worried about that, stick to OTA update from your carrier. You do not need to be rooted to flash an ODIN tar.

Alex-V said:
I'm still download the firmware..lol..and works..?
Click to expand...
Click to collapse
Yes it works.
---------- Post added at 09:53 PM ---------- Previous post was at 09:48 PM ----------
evonc said:
Take the ODG zip and create an Odin flashable tar package of only System.img and boot.img.
Once an image comes out for your carrier, you can update bootloader/radio if you choose.
Not sure if it will trigger KNOX. If you're worried about that, stick to OTA update from your carrier. You do not need to be rooted to flash an ODIN tar.
Click to expand...
Click to collapse
Thanks,
Knox didnt trigger

okolobaccess said:
Yes it works.
---------- Post added at 09:53 PM ---------- Previous post was at 09:48 PM ----------
Thanks,
Knox didnt trigger
Click to expand...
Click to collapse
yes..also on it now..works fine.

Alex-V said:
yes..also on it now..works fine.
Click to expand...
Click to collapse
have observed any changes yet

okolobaccess said:
have observed any changes yet
Click to expand...
Click to collapse
its much more stable..and noticeable faster..but still i have the night clock problem....

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.