yashsingh1/xdaforums huggingface dataset:
[Sprint  Galaxy Note 4 General] yo0123yo:
I had mine rooted and everything was fine following this method and then randomly my brain told me to run root checker just for giggles and see that it is still rooted, it wasn't, so I got stuck in the beautiful bootloop upon restart. I have no idea how it became unrooted? To fix this, I did a factory reset through TWRP and did these steps again, just have to re renter passwords and download a couple of programs. I am narrowing it down to two potential suspects, I noticed it after I installed Wanam Xposed for Lollipop via TWRP flash (it worked fine) or after I connected the phone to my Macbook Pro to charge. I'm guessing it is due to Xposed? Can it possibly have anything to do with being plugged in to my Macbook Pro since it was the first time I've plugged this phone into it? Thanks guys! As of now it's working fantastic but I'm definitely going to hold off on installing Xposed for now. This is the Xposed I used, arm. http://xdaforums.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
[Sprint  Galaxy Note 4 General] Kwaii49:
Quote:

this method worked flawlessly. took me a couple tries doing it other ways without reading the whole thread, this one took the cake. thank you!!!!
[Sprint  Galaxy Note 4 General] anees02:
plese help.

i flashed oj6 tar and updated to ok1 and flash twrp and root it and everything ok.

BUT today i have bootloop ..tried to flash stock root kernel and super su again but no fix.

how to fix now?
[Sprint  Galaxy Note 4 General] samep:
Did you try wiping cache and dalvik-cache? What have you installed since OTA? Xposed?
[Sprint  Galaxy Note 4 General] anees02:
I didn't wipe cache an dalvik-cache.

But when i flash BeastMod stock OG5 kernel then the bootloop fixed.

But i tried to flash the stock root OK1 kernel again but the bootloop comes again.

Then the issue is in kernel itself.

Now is it any possibility to flash the stock unroot kernel for OK1?and where i find it's link?
[Sprint  Galaxy Note 4 General] samep:
Sorry, I didn't follow the last part. The kernel is linked in OP; you flashed that already? If you're referring to stock OK1 kernel, there's no tar yet but it's not rooted with exploit so it won't allow root.

What SuperSU install and version did you use?

When you swap kernels, you should wipe and cache and dalvik-cache if it didn't do that but looped instead.

You may try using the method described on post 29 if you want try this kernel again. (After the cache and dalvik-cache wipe)
[Sprint  Galaxy Note 4 General] anees02:
I flashed the kernel in OP.

flashed with odin ,also with recovery but no way.

wiped cache and dalvik-cache no way.

I used BETA-SuperSU-v2.52 flashed it before kernel or after kernel no way.

BUT when reboot to recovery there is pre-recovery black screen that said (KERNEL IS NO SEANDROID ENFORCED)

When i flash BeastMod OG5 kernel the bootloop fixed.
[Sprint  Galaxy Note 4 General] samep:
So permissive kernel is more stable for you? Did you flash any mods that conflict with SELinux enforcing mode? Did you try to disable SELinux? That could be the issue but factory reset or data reformat may be a shorter route to recover as opposed to Odin OJ6, OK1 OTA and trying this again with minimum mods.
[Sprint  Galaxy Note 4 General] anees02:
I recently tried to install twrp manager and flashify from Google play but after installing them they said that you are not rooted although i already rooted the device and using some root required apps without problems.

Then i open supersu app and said that the binary files not installed..

Now i have to reset the device from Android OS itself not from twrp recovery?
[Sprint  Galaxy Note 4 General] samep:
Sorry, the option I meant for TWRP was reformat data.

TWRP has issues with Chainfire patch with systemless SuperSU. You're not running systemless root but maybe the SELinux enforcing is masking root in a way that TWRP thinks you have no root?

If it's only TWRP and TWRP manager that thinks you have no root, ignore it; don't let TWRP apply SuperSU for you. Just use SuperSU beta.

Have you at any time applied SuperSU 2.56 or higher? Those are systemless SuperSU and should not be flashed over with older SuperSU, particularly the one that TWRP prompts you to write over it.
[Sprint  Galaxy Note 4 General] anees02:
Thank you samep

I just wipe the data, cache & dalvik-cache partitions.

Now my device rooted with stock root ok1 kernel.

But i have one more question.

How could i take OTA while i am on this kernel as freeza said?

My status in about phone : custom.
[Sprint  Galaxy Note 4 General] samep:
That is a future development project; see OP. Most likely a freeza ROM and kernel with SuperSU systemless root by Chainfire. Freeza or Chainfire could tell more than I could imagine.

But I'm imagining big with stock recovery backup to restore with full un-root for OTA and possibly a minimum un-root for Android Pay, if that is even needed.
[Sprint  Galaxy Note 4 General] kaos420:
Ya i dont get it.i say official the whole time until i update.after update it says custom. And i cant get android play to work.says unsupported. So weird.and ive full tar odined oj6 like 6 times now.factory recovery wipes and all.

Sent from my 0x1 Note 4...... I love tep
[Sprint  Galaxy Note 4 General] TheBaconator:
Will it brick or bootloop my phone?

Will this brick or have my phone go in a bootloop cause I tried rooting my phone when it was running android 4.4.4 and it would always go in a bootloop, my phone is using this version of Android Lollipop: N910PVPS4COK1. Thanks!!!
[Sprint  Galaxy Note 4 General] ianmb:
Just follow post 29 and you should be good. I've used that process 5 or 6 times now going from OJ6 to OTA OK1 and rooting with this kernel and every time was flawless. No trouble at all.
[Sprint  Galaxy Note 4 General] DrKaotica:
I do have a custom device status showing. I don't use Android pay so I couldn't speak to that.

Just happy i have the latest stock ROM rooted so I can use adaway. That's how I've been rolling on this phone for a year now.
[Sprint  Galaxy Note 4 General] anees02:
Hi samep

After i fixed the issue yesterday.

Now the issue returned again.

Something wrong i don't know what is it?

Today i reboot my device and enter to the bootloop again.

I didn't install any app that probably causes the issue.

It comes by itself.

Now i flashed beast mod kernel COG5.

I will stay with it until finding new kernel to try it.

I attatch this image during boot it says

Kernel is not seandroid enforcing.
[Sprint  Galaxy Note 4 General] samep:
Sorry to hear that. I get that message, kernel is not enforcing on boot as well. I think it's possibly the mods you're running that make permissive kernel more stable for you. I think this kernel is actually in experimental stage. I can say Chainfire's enforcing kernel patch is experimental. But this one is a bit unique from that of Chainfire because it didn't come with the prerequisite to run systemless SuperSU root.

Are you making any system modifications after flashing this or just just staying full stock? And to be thorough, which SuperSU version are you using? Have you changed versions or been prompted by TWRP to allow TWRP to apply it for you?

It could also just not be playing nice with Knox. Did you remove or freeze Knox?

Those answers may help our developer. Thanks in advance. There are plenty of options in permissive kernels to run. The one you're running, if fully compatible for you, is most likely as efficient as any out there.
[Sprint  Galaxy Note 4 General] anees02:
All these questions, their answers no.

I didn't use any mods or modifications

EXCEPT that i freezed all knox relative apps.

Is this the main cause for the issue?
[Sprint  Galaxy Note 4 General] samep:
Good question. If you're looking for answers, you could try again without the freezing. You may have frozen too many applications or SELinux depends on Knox with enforcing mode present. I can't answer that at this point but IMO that is a good data point to note.

Thanks for the reply. If you don't mind, could you post all the frozen applications you froze?
[Sprint  Galaxy Note 4 General] anees02:
Please tell how to export the list of frozen files automatically?

I froze 27 pre-installed apps.
[Sprint  Galaxy Note 4 General] samep:
You could copy by keyboard typing or post screenshots... Screenshots could come from the unfreeze menu or app manager far right tab for disabled apps.
[Sprint  Galaxy Note 4 General] anees02:
All these apps are frozen
[Sprint  Galaxy Note 4 General] jhill110:
There's a way in TiBu to export frozen apps list.. It's been a long while since I've done it. I'll see if I can figure it out again
[Sprint  Galaxy Note 4 General] samep:
Are you using third party apps like Link2SD or Titanium to link system updates to extSdCard or install dalvik-cache in system partition?

I don't think that would play nice with SELinux, if so. Just me saying this, but I'm not sure you need or have to freeze all those Knox apps even using enforcing kernel?

I don't know if you want to pursue any of this until more is known or shared by our developer, [MENTION=309990]freeza[/MENTION], but only if you want to try again, you might consider try thawing the Knox apps when using enforcing kernel and avoid using some of the capabilities those apps offer; they may just be too extreme for SELinux and enforcing mode by kernel. It's up to you; I think you'd prefer to wait for more information so I'm just thinking out loud.

But a reply could be of use, anyway. Thanks in advance.
[Sprint  Galaxy Note 4 General] anees02:
I use Link2SD to freeze or delete system apps. But i don't link any app because Note 4 has enough internal storage.

Still wait for developers to release another kernel to test.
[Sprint  Galaxy Note 4 General] antila:
Hello!

If I installed the COK1 Rom already trough ODIN, can I flash this kernel just flashing trough TWRP? If Yes, do I need to flash SuperSU also?

Thank you!
[Sprint  Galaxy Note 4 General] samep:
You found the right post. Some have said it works best in sequence as posted.

However, update to OK1 method makes no difference. After you Odin TWRP, you can follow the rest in recovery. Flash both in sequence shown with the reboot back to recovery to flash SuperSU zip as suggested.

I've yet to do it so go with those that said it was just what they needed.
[Sprint  Galaxy Note 4 General] ianmb:
Is your OK1 ROM stock tar? If so, you should be able to Odin TWRP. Then follow the post you quoted #29. I know there is a pre rooted OK1 ROM in the development section. But you would still need to Odin TWRP in order to flash it.

---------- Post added at 04:13 AM ---------- Previous post was at 04:12 AM ----------

Sorry [MENTION=4375749]samep[/MENTION], must've been answering at same time...lol!
[Sprint  Galaxy Note 4 General] samep:
Not a problem. It's better you answer; you had the experience with the install. LOL. I'll get to this soon, though.

Thanks for responding.
[Sprint  Galaxy Note 4 General] richardjrdeal:
AP

---------- Post added at 03:09 PM ---------- Previous post was at 02:51 PM ----------

Try here for deodex to use xposed

http://xdaforums.com/showthread.php?t=3271966
[Sprint  Galaxy Note 4 General] DrKaotica:
Just an update on my experience. I was up and running with root access on stock OK1. Last night my phone ran out of juice. When i plugged it in and tried to boot it back up I was stuck in a boot loop. Seems weird to me after it was working fine for a few days. I got back to unrooted OK1 just fine.
[Sprint  Galaxy Note 4 General] LinuxGuru007:
I was also, having issues with boot loop. If on a fully stock OK1, use twrp and Chainfire's SuperSu Beta 2.62, it patch's boot and then your rooted.
[Sprint  Galaxy Note 4 General] samep:
I also hoped that [MENTION=309990]freeza[/MENTION] had some feedback on this. It's a theory and a suggestion until we know more. I had thought that the patch freeza used was permanent and wouldn't be dependent upon SuperSU systemless root? Maybe, maybe not? Chainfire systemless SuperSU is experimental...

Just be careful not to break the Chainfire boot patch by flashing older SuperSU system based versions, post 2.56 over your systemless root. That would include not allowing TWRP to install SuperSU. Maybe that's resolved now but earlier versions of systemless SuperSU were not detected by current TWRP.

The versions of systemless SuperSU prior to 2.62 were eventually losing root with me on the Chainfire patch over stock kernel. The one you mentioned didn't fail me but I didn't run it very long.

Let us know if you lose root. It may not boot loop but you may find that you suddenly can't use your su granted permission apps.
[Sprint  Galaxy Note 4 General] LinuxGuru007:
Will keep you posted, so far so good, no problems running 2.6.2-3. Twrp still doesn't see root, ignore, don't let it install.
[Sprint  Galaxy Note 4 General] samep:
Just to be clear, are you running freeza kernel with systemless root or running stock kernel with systemless root that only includes the Chainfire boot patch?

I'm not clear on that, myself. Fully stock OK1 would mean you patched the stock kernel and didn't flash the freeza kernel, right? Since we have the OK1 stock tar, it's fairly easy to get back to stock kernel.
[Sprint  Galaxy Note 4 General] LinuxGuru007:
Correct, fully stock kernel with chainfire boot patch, I couldn't get Freeza's too work by any method on mine. So im on Stock kernel with systemless root.
[Sprint  Galaxy Note 4 General] ianmb:
So rooted apps still working correct? And does your device status read official or custom? Just curious. Thanks!
[Sprint  Galaxy Note 4 General] LinuxGuru007:
Yes, all rooted apps I use, work. ATM, its still custom.
[Sprint  Galaxy Note 4 General] JFay22:
Can anyone confirm that OK1 with freeza stock kernel works with Wanam's modified xposed framework for odex? I'm still on OJ6 with freeza OG5 permissive Beastmode kernel and xposed is working perfectly. I don't want to update with new stock kernel and lose xposed. Thanks
[Sprint  Galaxy Note 4 General] jhill110:
I'm running [MENTION=1503720]tx_dbs_tx[/MENTION] 's stock OK1 with v79 and it's working fine so far.

I ran it fine with the DeOdexed version also.
[Sprint  Galaxy Note 4 General] jhill110:
Deleted weird double post on XDA premium.
[Sprint  Galaxy Note 4 General] kaos420:
does theming work for you?on odex i couldnt get the notification toggles to change color like i can on deoxed. figured it was just cause of odex.
[Sprint  Galaxy Note 4 General] jhill110:
That's most likely.
[Sprint  Galaxy Note 4 General] JFay22:
I am on stock odex OJ6 and with xposed and wanam app plus serajr's Blurred System UI app I was able to theme my toggles uniformly here is a screenshot I can tell you my settings if interested http://imgur.com/XzFcAxq
[Sprint  Galaxy Note 4 General] richardjrdeal:
I Odined stock OK1 from sammobile, TWRP, Flashed this kernel, installed xposed installer 3.0 apk, then flashed xposed 79-sdk22-arm version, added modules, like wanam for LL, etc etc it all seems to be working fine.
[Sprint  Galaxy Note 4 General] yo0123yo:
OK so this is odd....whenever I use this method, Rootchecker says I am rooted and then a couple hours pass and then it says I am not rooted, without even installing any software. any idea whats going on? whats causing it to unroot?
[Sprint  Galaxy Note 4 General] arrogant437:
Anyone know if theres an OK1 modem only tar available yet? Looking for the modem.bin/NON-HLOS.bin files

My P.C. is out of commission so im not able to odin the full stock tar this go round.
[Sprint  Galaxy Note 4 General] kaos420:
Freeza said you cant recovery flash modems any more.all has to be odined now.

Sent from my 0x1 Note 4...... I love tep
[Sprint  Galaxy Note 4 General] antila:
I've Odin'd COK1 Rom, Tar. Then i've installed TWRP and after that i've Flashed Stokish rooted COK1. Can I install this kernel right now and do I need SuperSU beta?

---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------

I've installed Odex prerooted rom. Can I install Xposed and where can I find it?

Thank you!
[Sprint  Galaxy Note 4 General] antila:
I've installed Odex prerooted rom. Can I install Xposed and where can I find it?

Thank you!
[Sprint  Galaxy Note 4 General] samep:
[MENTION=341864]antila[/MENTION]

Does the first screenshot in this OP, post 1, match your current About device in Settings? Compare the kernel and SE Android status, please. But you already have SuperSU; compare to 2nd screenshot in this OP.

As far as Xposed working with Odex OK1, it works as posted here:

http://xdaforums.com/showthread.php?p=64386449

You can find Wanam custom framework for TW below; use the arm, not the arm64. Download the arm uninstaller too.

http://xdaforums.com/showpost.php?p=62377731&postcount=1

For Odexed ROM, I recommend applying Xposed framework last to avoid installation difficulty you may have with applications installed in system app and priv-app directories.
[Sprint  Galaxy Note 4 General] antila:
Hello!

First screenshot is the same. Second little difference, I have the same SuperSU version, only PRO. I've paid.

Thank you. I'll try.

---------- Post added at 04:32 AM ---------- Previous post was at 04:12 AM ----------

Sorry, I have one more question. I've downloaded everything. What I need to do with the uninstaller?

---------- Post added at 04:48 AM ---------- Previous post was at 04:32 AM ----------

Hello!

If I understood you right I need to do:

1.Flash this kernel

2.nandroid backup (maybe first I need to do nandroid backup)

3.flash installer arm.

4.reboot

5. Install xposed apk file.

Is it correct step-by-step or I missed something?

Really sorry for those stupid questions?

Thank you very much!
[Sprint  Galaxy Note 4 General] samep:
[MENTION=341864]antila[/MENTION]

You already have the kernel and root. Skip step 1. The rest looks good to me but I forget if script wipes so best to wipe cache and dalvik-cache before flashing Xposed.

The uninstaller is good to have in case of unexpected boot loop or if you have difficulties installing a system application mod that doesn't install despite one extra reboot. You may have to uninstall Xposed, apply mod and reinstall Xposed. You'd also use it in part to un-root.
[Sprint  Galaxy Note 4 General] kaos420:
Why uninstall it?boot to safe mode.uncheck the corrupt module. Reboot to normal mode.then delete said module.everyine forgets about safe mode.lol

Sent from my 0x1 Note 4...... I love tep
[Sprint  Galaxy Note 4 General] samep:
You're right that's an option but he's installing Xposed- not in a boot loop and was asking about the uninstaller I suggested.

Running Xposed over Odexed ROM, I've had a couple of situations where I couldn't install a modified application in system due to the .odex.xposed extensions that v78 Wanam custom framework applies and manages the system applications. I didn't boot loop but couldn't get those applications to install until I uninstalled Xposed.

The other occasion I had, I discovered two reboots actually applied the application but I couldn't remember if I even had Xposed installed or was that after I updated to Wanam v79. Not recalling had me just suggesting to have the uninstaller, if needed.

If you had an issue with boot loop and had just applied an Xposed module, that would apply; sure. LOL; every time I think to use or suggest safe mode, I have to look up the key sequence. Which is it again? LOL.

Thanks.
[Sprint  Galaxy Note 4 General] kaos420:
Not hard just press volume down at splash time it right.and safe boot happens.

Sent from my 0x1 Note 4...... I love tep
[Sprint  Galaxy Note 4 General] L_B_J_1:
I just read the entire thread to see if this had happened to anyone else. my phone has been running great I used the root method found here. been running it for a week now . went to use a root app tonight it said that I wasnt rooted so i rebooted the phone and now its stuck in a boot loop. nothing was done to the phone accept rooting it. my question is, is there a fix for this or do i need to do a factory reset? because that was the only way i got it working the first time i rooted with this method even following post #29. I have also wiped cache and dalvic cache.
[Sprint  Galaxy Note 4 General] samep:
Let's try to full un-root by booting into safe mode, launch SuperSU and full un-root.

See kaos post above yours. Trigger should be second splash screen and hold volume down.

Did it boot? If you get far enough to un-root, try reboot and see if it boots without SuperSU. Don't let TWRP install it yet. You can also wipe cache and dalvik-cache if un-root alone doesn't do it. Did it reboot after un-root?

If you get that far, I'd suggest a different SuperSU. Hard to say if you should go back or forward. I'd say try SuperSU 2.50 first. Later try SuperSU 2.64 or latest if another update drops. But you can go the way you prefer.

http://download.chainfire.eu/741/SuperSU/BETA-SuperSU-v2.50.zip

Edit: I've tried both versions of SuperSU and 2.50 lost root and 2.64 only gave me partial root. Can't see the SuperSU apk merely flashing SuperSU 2.64 with kernel because the script exists when it discovers the kernel is already patched and no stock image for backup exists.
[Sprint  Galaxy Note 4 General] anees02:
That exactly what happened to me.

I fixed it by flashing another kernel

Either BeastMod kernel for COG5

Or Emotion kernel rc20 or rc21.

Any One of these kernels should fix this bootloop.
[Sprint  Galaxy Note 4 General] JFay22:
Just had bootloop out of nowhere. Flashed BeastMode og5 and fixed.
[Sprint  Galaxy Note 4 General] mahadri:
Can't boot into safe mode from the bootloop. SuperSU 2.52 with StockOK1RootKernel.tar

The first time it bootlooped, TWRP factory reset fixed the boot loop. Clearing Cache and Dalvik Cache alone didn't.

This 2nd time, Odin flashing stock OK1 fixed the boot loop without clearing Data.

Just TWRP installed SuperSU 2.64 with stock OK1 kernel. Hopefully it's stable.
[Sprint  Galaxy Note 4 General] samep:
IDK, pull the battery and power up and get to the volume down button quickly but not so quick it just hangs the first splash screen?

Sorry that didn't work but thanks for the update. I zigged and you zagged; I installed SuperSU 2.50 beta and you installed 2.64 beta.

Let's see if any of us lose root now. May take a few days to happen but I'll update this thread since I'm on the kernel now.

For an update on my situation, I haven't gotten on this kernel until this morning. I had tried stock OK1 and OJ6 kernels with SuperSU updates as they came starting at SuperSU 2.60 beta. First one boot looped after about 48 hours. The next two I tried were losing root but not boot looping. SuperSU 2.63 was stable but I heard 2.64 had even more bug fixes but I had already gone back OJ6 tar, then restored OJ6 TWRP backup before thoroughly testing SuperSU 2.63 beta. I've been running Beastmode Rage 1.2 kernel until I finally decided to test this kernel.

Once l got on it, I immediately got the pop-up below, persistently. Reboot took me to recovery. So there must be some kind of recovery fix anticipated there but thwarted by custom recovery. Long-pressing the notification that also appeared in pull-down; notification was coming from SecurityLogAgent. Froze it and rebooted; persistent nag is now gone.

I said all that to suggest if you or anyone else running this kernel haven't done it already, you should freeze or uninstall SecurityLogAgent. It may not be there if you flashed a ROM. My older OJ6 bootloader may behave differently altogether than your OK1 bootloader. It's possible the newer bootloader reacts more aggressively rather than the persistent security notice I got.
[Sprint  Galaxy Note 4 General] LinuxGuru007:
I've been running 2.62-3 then updated to 2.64 since they were released. On Full stock OK1 and stock kernel with xposed, no issues as yet.