yashsingh1/xdaforums huggingface dataset:
[Sprint  Galaxy Note 4 General] samep:
Update: I lost root with SuperSU 2.50 beta. Stock kernel appears to be stable with systemless root do that may the path I take but I'm still testing and hoping to get this kernel running. Maybe an update or clarification from [MENTION=309990]freeza[/MENTION] will fix that? No rush; Merry Christmas, all!

I tried systemless root but I think the Chainfire script exits early due to not having a stock su image for un-root and backup. I'm partially rooted but can't see the SuperSU application. That's fine for now.

Later I'll try a fresh system flash as Chainfire recommends and see if I can swap the kernel after starting systemless root with stock kernel. Just my thoughts so I wouldn't recommend trying it without knowing the outcome.
[Sprint  Galaxy Note 4 General] antila:
Hello! Can you help me, please? How can I boot into Safe Mode? Phone is turned off. Tried Volume UP + Volume Down. Still can not get into.

Thank you
[Sprint  Galaxy Note 4 General] LinuxGuru007:
Power off, then hold power button until Samsung Note4 logo appears, release button, then hold Volume down button until safe mode appears.
[Sprint  Galaxy Note 4 General] samep:
Quoting myself to update further...

This appears to have gotten me fully rooted, for now at least, without having to flash system again. I established the systemless root with stock kernel and 2.64 SuperSU beta, confirmed with a boot and then flashed freeza's kernel zip. Booted and confirmed the screenshot in OP matches kernel in About phone. I do have some adb access with this kernel despite "adb remount" of system yields permission denied. I can still adb reboot and adb pull folder/file(s).

I'll continue to post updates if I lose root again or if progress is realized.
[Sprint  Galaxy Note 4 General] anees02:
What about supersu 2.64?

Is it general for any android phone or just for our variant?

Since i used to cf-auto method which differ from phone to another phone.

Also if it is any link for supersu 2.64 beta will be better.
[Sprint  Galaxy Note 4 General] samep:
The link is here, try the latest one.

http://xdaforums.com/showpost.php?p=64161125&postcount=3

It won't do any good to try to patch a kernel already patched like this one. In order to work, it needs to be flashed while on stock kernel. An example would be Odin the tar and root it with this SuperSU in TWRP rather than CF Auto Root in Odin.

Of coarse you could also just go with freeza's permissive kernels like Beastmode 1.0 or Rage 1.2 or another 5.1.1 custom permissive kernel.

I just extracted the stock kernel from the tar and flashed both kernel and SuperSU beta in the same flash I made. Tried that this morning and haven't lost root yet. I think it was a redundant step but I also flashed this kernel over my systemless root. Don't know, but it may be the same kernel; the patch is similar. If you try to flash the SuperSU over this kernel, the script says it's already patched but exits without completing the script so it didn't fully root that way.
[Sprint  Galaxy Note 4 General] @BB:
Can anyone please confirm whether Android Pay works after this???
[Sprint  Galaxy Note 4 General] antila:
I do not know what to do. For some reason all files with SuperSu, when I'm flashing it says "file is corrupted". Tried downloaded few times with same result. TWRP says "file is corrupted".

Any idea?
[Sprint  Galaxy Note 4 General] LinuxGuru007:
Did you try downloading with chrome or internet? I know ES File Explorer at times has this prob.

stop@hammertime:~> touch /this touch: cannot touch "/this": Permission denied
[Sprint  Galaxy Note 4 General] tx_dbs_tx:
We may need a seperate thread for this root stuff, not sure if the root issues discussion should continue here but it is an important topic right now that's for sure.

I would think that if you start with bone stock OK1 system and kernel and apply the latest systemless supersu that you should have root. Doing this then turning around and replacing the kernel with this one or any other will break root obviously. The only options I see are to root using the older 5.1.1 OK1 kernels with the traditional system root binaries prior to 2.50 or use the new beta systemless root with this kernel or any other OK1 kernel that is completely pre-patched with the new systemless root method, which I don't think this kernel is right now. I'm thinking an update should be in the works for this kernel. Until then i think this kernel & root works fine by following the OP's instructions but you MUST turn off system updates in settings or you will eventually lose root if the system updates either on it's own or by the user. this includes the samsung security patch updates. If I'm wrong here feel free to correct me.
[Sprint  Galaxy Note 4 General] shepardstuff65:
After completly stripping everything but sd card, installing the ok1 complete firmware, android pay works. I was previously rooted on the og5 ported note5 rom. even after firmware upgrade, knox is still tripped. 0x1. I have not ran this kernal yet, wanted to experiment with samsung pay and android pay first. Samsung pay doesn't work. I get the following;

< SamsungPay info >

Version : 1.3.3216

VersionCode : 133216

< Stack trace info >

FATAL EXCEPTION: main

Process:com.samsung.android.spay, PID:21125

java.lang.NoClassDefFoundError: Failed resolution of: Lcom/sec/dcm/DcmKeyManager;

//////////////////// Spay Stack Trace ////////////////////

at ni.a(Unknown Source)

at mh.a(Unknown Source)

at mh.b(Unknown Source)

at mh.a(Unknown Source)

at lo.b(Unknown Source)

at lo.b(Unknown Source)

at lo$6.onComplete(Unknown Source)

at me.a(Unknown Source)

at me$1.handleMessage(Unknown Source)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:145)

at android.app.ActivityThread.main(ActivityThread.java:6872)

at java.lang.reflect.Method.invoke(Native Method)

at java.lang.reflect.Method.invoke(Method.java:372)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1404)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1199)

//////////////////// Spay Cause ////////////////////

java.lang.ClassNotFoundException: Didn't find class "com.sec.dcm.DcmKeyManager" on path: DexPathList[[zip file "/system/framework/org.simalliance.openmobileapi.jar", zip file "/system/framework/seccamera.jar", zip file "/system/framework/minimode.jar", zip file "/data/app/com.samsung.android.spay-1/base.apk"],nativeLibraryDirectories=[/data/app/com.samsung.android.spay-1/lib/arm, /vendor/lib, /system/lib]]

at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)

at java.lang.ClassLoader.loadClass(ClassLoader.java:511)

at java.lang.ClassLoader.loadClass(ClassLoader.java:469)

at ni.a(Unknown Source)

at mh.a(Unknown Source)

at mh.b(Unknown Source)

at mh.a(Unknown Source)

at lo.b(Unknown Source)

at lo.b(Unknown Source)

at lo$6.onComplete(Unknown Source)

at me.a(Unknown Source)

at me$1.handleMessage(Unknown Source)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:145)

at android.app.ActivityThread.main(ActivityThread.java:6872)

at java.lang.reflect.Method.invoke(Native Method)

at java.lang.reflect.Method.invoke(Method.java:372)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1404)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1199)

not sure if the community can use this info to engineer a work around. Fixing to dirty flash this rom with android pay already working. updates soon.
[Sprint  Galaxy Note 4 General] samep:
[MENTION=6232501]shepardstuff65[/MENTION]

This is not a ROM but a kernel. If you're looking to keep Android Pay, you need to review systemless root and systemless busybox if looking to keep that function.

Start with the SuperSU for systemless root, linked below and follow the links for discussion. Plus, the root may be lost with this kernel without the stock backup and su image. A simple reboot would recover that with systemless flashed over stock kernel. Read and consider first. I'd like to hear your report though.

http://xdaforums.com/showpost.php?p=64161125&postcount=3

Stericson busybox has the systemless busybox.
[Sprint  Galaxy Note 4 General] shepardstuff65:
So, without thinking it through, i attempted to flash this kernel via odin, without first installing su or twrp. Ended up in boot loop. So, reflashed ok1 firm. Will attempt again here later, with the installing the seamless stuff first. I was aware of losing root after firmware upgrade. I was actually trying to see if Knox would reset with a full firm upgrade [MENTION=4375749]samep[/MENTION]

Food for thought, I've read across a few threads about individuals using the og5 port on newer basebands, wondering if i chose so, to be able to flash that again depending how this all works out, without resorting to the og5 firmware.
[Sprint  Galaxy Note 4 General] anees02:
What about trying to root with another root method like kingroot? [MENTION=4375749]samep[/MENTION] You didn't tell us about your root method result. Did you lose the root with your method or still rooted?

And we need stock non-rooted ok1 kernel also to try.

Could you upload the stock non-rooted kernel?
[Sprint  Galaxy Note 4 General] samep:
I read through the Chainfire threads. The method that freeza introduced was more like the original manual script in SuperSU beta 2.52

Auto scripting the stock kernel was introduced in SuperSU beta 2.60 and those after it. Chainfire had said those that had used the earlier manual methods needed to reflash system and stock kernel in order to transition to the new auto script and because it's also systemless root. System shouldn't be modified as he sees root in marshmallow at this time.

There was also the Samsung security update that broke root for a lot of devices that had to be included in updates. Or as [MENTION=1503720]tx_dbs_tx[/MENTION] posted, you could flash the OK1 ROM or tar cleanly and quickly disable updates to refuse the update that breaks this kernel.

Have I lost root? Some apps don't like systemless root but if all apps suddenly say there is no root, a reboot cures that rather than looping the boot. It's not prefect but if wanting to use enforcing SELinux with stock kernel, this is currently it.

I've asked [MENTION=309990]freeza[/MENTION] to provide us with another one of his permissive kernels based on stock OK1 kernel. I really think permissive is more stable which is why I've suggested others try an older 5.1.1 permissive kernel of freeza's or a newer permissive kernel.

You could restore the stock kernel and root again with systemless root but you're more likely to get results by cleanly installing a stock OK1 ROM and updating the SuperSU beta as needed (it may already be updated). Or you can Odin the OK1 tar and root it with the updated CFAR (Chainfire auto root) for Note 4. That method also backs up the stock recovery to restore on full un-root. It should work for OTA updates if system is not modified. Problem is that there are many mods that modify system. This is the private reason freeza has given systemless root little attention.

IDK, maybe system can be backed up to restore due OTA and the method works? That's the direction I'm going to try next: clean install OK1 tar, root with CFAR, mage a backup of stock kernel, just in case, install TWRP and backup system and flash the mods i want and see if system restore she full un-root in SuperSU make OTA possible later.

If you like Xposed framework for mods, I'd suggest going with a deodexed ROM for ease of modifying system. Odex makes it harder to apply system changes. The phone and battery just doesn't need all those heat cycles of rebuilding art/dalvik partition to apply a new system application. [MENTION=309990]freeza[/MENTION] is working on an update.

If stock is just right for you, systemless root is ideal; restart with clean Odin stock tar and root with CFAR. Done. But if you lose root, reboot. If that happens too frequent, check Chainfire for systemless beta updates.
[Sprint  Galaxy Note 4 General] anees02:
How to disable Samsung security updates?

And what about the new kernel by freeza which called Beastmode kernel stock optimized 1.5.

Is it permissive or enforcing kernel?

And when i flashed a new version beta of SuperSu 2.66 on previous 2.52 version it couldn't flashed... Should i have to return to stock before flashing a new SuperSu version?
[Sprint  Galaxy Note 4 General] samep:
You're still wanting to retain OTA capability, if possible, right? If so, I think you should remain stock with the stock kernel rooted with SuperSU 2.65 or you can use Odin and Chainfire Auto Root (CFAR) for Note 4 right over stock tar OK1 after it boots and setup.

Beastmode 1.5 is better than stock but flashing that may not retain your OTA capability.

Edit: you shouldn't have to stop the Samsung security updates with stock kernel or Beastmode 1.5 kernel but to disable, uncheck the auto update in Settings/System update.

Beastmode 1.5 plus SuperSU 2.52 yields permissive mode. I think the Enforcing mode would require SuperSU 2.65, currently. IDK why SuperSU 2.66 wouldn't flash over SuperSU 2.52; there's a script you can run when switching between system and systemless SuperSU. Goto the link below and scroll to unSU script link.

http://xdaforums.com/showthread.php?t=2239421
[Sprint  Galaxy Note 4 General] antila:
Hello!

I'm still loosing root. But what more annoying after reboot I'm getting boot loop. And fixing it only after restoring previous Nandroid Backup. As I understand I can root with CF-Autoroot, right?

I really want systemless root because I'm using only stock rom, but for some reason it is not working for me.
[Sprint  Galaxy Note 4 General] samep:
CFAR uses SuperSU 2.65 unless it's been updated. 2.65 is recommended AFAIK. Which kernel are you using?

The kernel in this thread is only suggested if you can disable Samsung security update before it updates; i.e., Odin OK1, disable software updates, install kernel and then flash SuperSU 2.65 beta to patch it.

But the stock kernel should work with SuperSU 2.65 with or without the security updates. Try backup of internal memory, wiping everything but extSdCard, format data, power down, Odin OK1, let the tar auto reboot and setup with data and GPS sync/lock. Then Odin the updated CFAR and you should be set. No loss of root or boot loops.

If you're going to use TWRP for any other reason, I'd recommend a backup of mostly stock and use osmOsis busybox, if you need busybox. Otherwise, if retaining stock recovery, just use the Stericson busybox installer from Google Play, if needed. Retaining a close to stock system with systemless SuperSU may retain OTA update capability with full un-root. Systemless busybox-if busybox is needed may help also but unsure about that; I changed too much myself to succeed in OTA update in my testing from OJ6 to OK1.
[Sprint  Galaxy Note 4 General] antila:
Thank you!

I want to ask you. Can you write step-by-step what to do? I did so many times but looks like I'm not doing something right. Help, please? I want Stock,root, TWRP. Also, what is the better kernel to use if I want stock? I have stock tar file.

Help me, please?
[Sprint  Galaxy Note 4 General] antila:
Thank you very much!

I have one more questions. I understand about Beast kernel but I do not see anywhere where I need to flash stock kernel. I understand about tar but here only stock kernel from the Rom. Do I need to flash kernel from Freeza also?

Thank you very much, again.
[Sprint  Galaxy Note 4 General] samep:
Read my post again. Sorry the word correction wasn't caught and I also added a couple of comments that may help.

No you don't have to flash both kernels. The 2 methods described steps for each kernel rooted with systemless SuperSU 2.65 That one word correction may have confused you. If you've had SuperSU below 2.60 flashed since your ROM flash, try unSU script flashed in recovery prior to kernel, then Beastmode kernel, and SuperSU and finally osmOsis busybox installer zip. I suggest wiping cache and dalvik-cache as well.

http://xdaforums.com/showpost.php?p=40409356&postcount=1 osmOsis OP for unSU and busybox installer
[Sprint  Galaxy Note 4 General] antila:
Finally it's working and I'm really appreciated for your help. Beast kernel works just fine but stock kernel doesn't work for me for some reason.

Thank you very much!
[Sprint  Galaxy Note 4 General] antila:
Hello!

Somewhere I've heard that by asking the right question you've already have the half of the answer. So, I've asked a lot of questions and you patiently answered but I was not really good reader. Few times in your answers you were saying about patching the system for systemless root to work. I've checked the threads about systemless root and here are a few boot images for patching. What is the correct boot image for our Note 4? And more importantly, what is the right way (step-by-step) how to apply this patch? What to do and how to apply Sepolicy? What is the right way to apply the patch and install root together? Step-by-step? sure only if my questions do not annoy you very much? I'm still like the Stock and systemless root if possible.

Sorry for my incredible stupidity and thank you very much for your patience.
[Sprint  Galaxy Note 4 General] samep:
Correct boot image is stock kernel but the latest Beastmode kernel has been reported to work in enforcing SELinux mode if systemless patch like SuperSU 2.65 is used. Using systemless root is the patch for root you're asking about. Beastmode doesn't rely on this patch for root but still requires a superuser application like SuperSU. Beastmode kernel already has an exploit for root but if you want that custom kernel to run in Enforcing mode, you use systemless root (SuperSU 2.65).

The order that I gave in the first numbered sequence uses the stock kernel from Odin of stock tar; if you're looking to retain OTA update capability, best do it that to start with stock system, recovery and kernel.

Basically, Chainfire Auto Root uses SuperSU 2.65 beta to patch the stock kernel for root; it also restores the stock recovery and prepares system to be put back as if it hasn't rooted with full un-root prior to OTA update. SuperSU beta 2.65 uses the systemless root method in order to make that happen among other things.

I'd suggest using the steps I already gave without busybox but maybe the explanation was all you were looking for? Or were you considering Beastmode kernel and giving up on OTA update capability?
[Sprint  Galaxy Note 4 General] Codepoet100:
Newby question for you. I'm on a Note 4 Sprint rooted running Kit Kat 4.4.4.. Can I use TWRP to flash your OK1 rom with root support?
[Sprint  Galaxy Note 4 General] mammothjojo88:
Yes you can.
[Sprint  Galaxy Note 4 General] Codepoet100:
Thanks for response. I tried yesterday and my phone was in a boot-loop . I used TWRP and flashed a new rom that is still Kit Kat 4.4.4.

Phone INFO:

Software version N910PVPU1ANIE

Hardware version N910P.05

Model number SM-N910P

Android version 4.4.4

Baseband version N910PVPU1ANIE

Kernel version 3.10.0-2774708 dpi@SWDD5004#1

Build number KTU84P.N910PVPU1ANK2

I just want to make sure I can flash this without going through that stress again. :)
[Sprint  Galaxy Note 4 General] mammothjojo88:
i think the reason you might have bootlooped is becasue your firmware is still on 4.4.4. see if you can update that first then do the stock rom. remember backup to be safe, its like putting on a condom lol
[Sprint  Galaxy Note 4 General] Codepoet100:
How do I update that first?
[Sprint  Galaxy Note 4 General] GavinMazey:
If you want to be on the latest note 4 update you have 2 options take ota updates or odin the latest cok1. Check this thread for the latest update. http://xdaforums.com/showthread.php?t=3250864
[Sprint  Galaxy Note 4 General] Codepoet100:
If I do that I would loose root right?
[Sprint  Galaxy Note 4 General] samep:
You would lose root, yes, but it's still capable of root. If upgrading to Lollipop, consider the recommended steps first and consequences first.

_______________________

Steps:

You should format your data before the update because of different file composition. Also, expect initial boot of custom ROMs or when wiping dalvik to take much longer to boot, gets stuck at splash screen a while before optimizing and starting apps with ART- Android Run Time.

You may consider backing up your keepsakes in internal memory, wiping everything but extSdCard, formatting data, power off, Odin the stock tar with Odin 3.10.7 defaults. Run setup wizard when it boots; do not pull battery or rush the process: expect one reboot to complete activation and afterwards verify data sync and GPS lock before proceeding... the link you were given before has the stock tar and reconnected Odin.

Rooting Stock OK1 requires:

1) Odin TWRP with no auto reboot, pull battery and USB 30 seconds and boot to TWRP https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar

2) In recovery, flash Beastmode kernel 1.8 http://xdaforums.com/showthread.php?p=64610967 and SuperSU zip and boot.http://xdaforums.com/showpost.php?p=55256620&postcount=1

Installing pre-rooted ROM only requires the above step 1 but in recovery, for step 2, flash the custom ROM instead.

_________________________

Consequences:

One important thing to consider, Odin update to latest or beginning with stock tars after the initial Lollipop, OB7, have the reactivation lock capable bootloader. The reactivation lock can be disabled to upgrade in Odin or flash mods and ROMs in recovery but Odin stock tar to downgrade is mostly blocked by the bootloader with few exceptions. Going back to KitKat via Odin would not be possible. There are other means to use KitKat after update but Odin is out of the picture in that regard.
[Sprint  Galaxy Note 4 General] Codepoet100:
Thanks for your help, let me see if I'm getting this right. With the ROM I have now if I use TWRP and flash the (N910PVPS4COK1 100% Stock kernel ROOT) after following the steps you listed I should be good?
[Sprint  Galaxy Note 4 General] samep:
I meant use the stock tar you were linked to in the previous post before I quoted you to answer your question about root.

I also outlined an update procedure to update to OK1 from KitKat.

Additionally, I recommended the updated kernel because this one was not working well with systemless SuperSU root as it updated and progressed. There was also a Samsung security update that broke the kernel's stability.

Beastmode 1.8 will work with latest SuperSU systemless root but systemless root is intended for users that leave system untouched stock, no custom recovery or custom kernel to allow full un-root to OTA update path.

You'd have to decide if you want systemless root or go a custom root that would require Odin to update.

If thinking OTA update with untouched stock but still having root for some purposes, consider stock tar to update and root with Chainfire Auto Root for Note 4 in Odin instead; that uses systemless root and leaves you with stock kernel (temporarily patched for root and boot), stock recovery and system fully un-rooted would allow OTA update provided you don't mount system or trip to modified status. Only ideal for stock users.
[Sprint  Galaxy Note 4 General] brons2:
If you are 100% stock with no recovery installed, you can Odin the TAR file and then install SuperSU via Google Play after booting up?

(and then once you have Super SU you should be able to install TWRP?)

I haven't had a Samsung phone since the S3 and I just got my Note 4 like three weeks ago. I'd really like to flash a custom rom but there seems to be so many issues with this phone. little scary. My LG G2 was rock solid and I had it on Temasek CM Unofficial 12.1 before switching to Sprint.