yashsingh1/xdaforums huggingface dataset:
[Galaxy Note5 Q&A, Help & Troubleshooting] Phil3759:
Answering you from your closed thread.

You should search and read about dm verity to understand a few basic things you're failing at booting.

PhilZ Touch will never modify /system, except in 2 situations:

- you accept the root prompt

- you use the pin lock option in recovery

However, PhilZ Touch does mount partitions in R/W as dm verity wasn't effective until now. Simply mounting rw changes the superblock and fails dm verity

Why people do need a custom recovery if they don't root? Rooting kills dm verity by definition.

So, adding options to mount RO in recovery seems useless for me.

The only solution will be recompiling kernel as I doubt mount option in fstab will work too long, unless Samsung and/or Google want to be nice with root users and keep a ramdisk level switch

PS: I am not monitoring this thread and I don't receive any @ notification
[Galaxy Note5 Q&A, Help & Troubleshooting] طوني تبولة:
920C rooted by flashing noble kernel then after suffering from frequent reboots, I flashed SpaceX and that didn't help at all.

I just flashed your kernel via TWRP and flashed SuperSU 2.52 and its been half an hour and made phone calls with NO issues at all. I know it is too early to evaluate the matter but I'm gonna report back after 24 hours.

Thank you for your efforts.

Edit: It's been more than 40hrs since I flashed the kernel, no reboots or any issues at all.

Can't thank you enough :good:
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
(for others reading the thread, this is what he's replying to: http://xdaforums.com/showpost.php?p=63207768&postcount=6)

What I hadn't known at the time I was doing that was "anything about dm verity or the mount option of support_scfs" (The firmware is still lollipop and I hadn't seen verity or anything like it implemented on any pre-6.0 android version.) I didn't expect that a simple r/w mount would cause a boot panic. In the case of TWRP, I later found out that TWRP modifies the system partition to prevent samsung from resetting the recovery partition. I don't know if Philz does the same thing or not. I don't suppose it really matters.

However, all those issues were overcome.

I think you might be misinterpreting my posts in that thread. I was "talking out loud" while trying to work out the issue. There's no blame for anything. When reverse engineering, which I was doing, taking notes on what doesn't work is almost as useful as taking notes on what does work.

Oh, and a perfect reason for a custom recovery and not rooting: backup. I've installed a custom recovery on many devices without rooting them just so I can back them up. It's also useful as a method to install and modify a kernel and/or system without rooting. While that will trip KNOX, by NOT having the device rooted, Android Pay (and several other apps that check for root) will still function.

Then I guess I'm replying to myself. It's okay. I talk to myself all the time. :laugh:
[Galaxy Note5 Q&A, Help & Troubleshooting] gundal:
just posting for reference incase anyone else is also mucking with this..

I had tried to get stock kernel booting with root on n9200hk and ran into a boot loop

I got it working now. This is awesome.

Enforcing with root :)

gj and ty again for pursuing this gary.

now I will be rebase-ing my kernel from OI1 sources and then applying commits and other changes, to ensure I don't miss anything instead of trying to put back SELinux.

The 9208 that was failing, did you confirm he flashed the 2.52 beta zip..? that was my issue..

already had 2.49 installed on my system, and used that just fine to patch the sepolicy, but wouldn't boot (loop right after samsung jingle)
[Galaxy Note5 Q&A, Help & Troubleshooting] Phil3759:
np

I didn't take it personal at all

Just wanted to direct you to dm verity. It was introduced already in 4.4, but probably not used in wide spread devices until now.

With Marshallow, chances it becomes standard + forcing kernel recompile

CWM and PhilZ Touch + probably new cm recovery as I seen do mount /system in rw

It is easy to disable, but needs to recompile recovery.

For backup, yes, true.
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
No, but a quick mention will call this to his attention. [MENTION=1306627]@Class[/MENTION] (do you realize its a pain in the rear to use standard 'mention' syntax with your username???)
[Galaxy Note5 Q&A, Help & Troubleshooting] pratik_193:
[MENTION=336863]garyd9[/MENTION] - any chance for G kernel ?
[Galaxy Note5 Q&A, Help & Troubleshooting] unnamed777:
[MENTION=336863]garyd9[/MENTION] sorry for duplicate, probably you haven't seen this post, but I really want to try you kernel:) :
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
You're the second person to ask for a 'G' variant. Like the previous person, you also seem to have either not read or ignored the first post in this thread.

If the OH6 is giving you a boot loop, then I seriously doubt that the OI3 kernel will do any better. I won't be back home to work on this for at least another 12 hours (assuming I have a chance to work on tonight at all), so you might be more quickly served by getting OH6 working. Are you using the stock OI3 firmware (nothing custom), and SuperSU v 2.51 or 2.52? So far, the most common causes of boot looping is using the wrong SuperSU version and using a mismatched firmware version. Where in the boot process is it looping? Are you seeing any part of the boot animation?
[Galaxy Note5 Q&A, Help & Troubleshooting] pratik_193:
I have clearly read the op. Just wanted to know your willingness so that i can provide u necessary files.

Anyways, i'll stick to arter's kernel.

P. S. : It's good that you mentioned about your rudeness part in op.
[Galaxy Note5 Q&A, Help & Troubleshooting] unnamed777:
I tried to reproduce the problem, but everything start working. I guess first time I mis-hit SuperSu version (I had 2.49 and 2.52). Thanks!
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I'm not going to be doing the new OJx firmware kernels until after I've heard various reports on it. I won't post anything until I've at least tried the "i" variant kernel on my own personal device, and I'm not quite ready to move my personal device to OJx.
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
Agreed :good:

For testing purposes I have flashed OH6 C-kernel on my N920I running newest OJ4 firmware and it works,

so I assume those kernels I+C are either identical or as close as possible.

Maybe it would save time to make only one for both devices :confused: (just in case you consider to do it again)

What do you think about it? [MENTION=336863]garyd9[/MENTION] (I could take a look by myself of course) ;)
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Even if they were 100% identical, I can assure you that it would NOT save any of my time having a single kernel for both I and C variants. The 5 minutes it would save me in repacking would be immediately consumed, each day, explaining to people that they are probably interchangeable.
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
From this point of view you are totally right, sorry for the stupid idea ;)
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Not really a stupid idea.. It's just that I've become jaded from years and years on XDA.

Even though the first post in this (and linked) thread gives clear instructions for requesting a different device, how often do you see people not following those instructions? Same thing for the version of supersu.

It doesn't matter if I use ALL CAPS, make the font larger and/or use different colors... a large percentage of people will refuse to read. Once, in a fit of sarcasm, I posted google translations into 3-4 different languages. It didn't help.

One of these days, if I'm feeling bitter enough, I'll post two sets of files. One set will be something that does something nasty like wiping off the system partition. The other will be whatever it is I'm sharing. I'll explain the different in the first post of the thread with big bold letters. Then I'll watch how many people download the WRONG set and complain about it.
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
[MENTION=336863]garyd9[/MENTION] may I pm you in an important matter?
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I don't think anyone has ever asked to PM me before. Sure, but please understand that I reserve the right to ignore it. :)
[Galaxy Note5 Q&A, Help & Troubleshooting] Yuhfhrh:
[MENTION=336863]garyd9[/MENTION] Thanks for the kernel, exactly what I was looking for. No problems booting, everything including NFC working, on my SM-N9208. Flashed this kernel on stock OJ3. I flashed TWRP via Odin, then flashed your kernel zip along with the SuperUser 2.52 zip in TWRP.

http://m.imgur.com/STNdWqA

Edit: I take it back, wifi is forgetting all passwords every time I turn it off or reboot the phone. Wifi is also taking about 7 seconds to turn on, much longer than the ~1 second before.

I'm also getting a security notice notification saying unauthorized actions have been detected. Clicking it brings up the device security portion of smart manager, but freezing smart manager isn't making this go away. I'm not sure what I need to freeze to stop this from happening.

In case these problems are from flashing the older kernel:

SM-N9208, N9208ZTU2AOJ3, https://drive.google.com/file/d/0B-B4fuuBmPzlWTIy...
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I suspect (but I'm not sure) that these issues might be related to flashing the pre-Jx kernel. As I mentioned in a previous post, however, I'm not ready to update my own device to the "2A" series, so I can't test this stuff and I won't release what I can't test on at least one device.

I'm curious: Have any n920T users tried the "T" variant kernel?
[Galaxy Note5 Q&A, Help & Troubleshooting] Yuhfhrh:
Sure, I understand. The boot file for 9208 is all ready for you when you are ready to update. :good:

I also don't mind being a 9208 test subject if you ever need one, as I have many other backup devices. Just send me a PM.
[Galaxy Note5 Q&A, Help & Troubleshooting] themoto:
@ Yuhfhrh

I'm also getting a security notice notification saying unauthorized actions have been detected. Clicking it brings up the device security portion of smart manager, but freezing smart manager isn't making this go away. I'm not sure what I need to freeze to stop this from happening.

I had the same problem when using this C kernel,just freeze security login agent with titanium backup.
[Galaxy Note5 Q&A, Help & Troubleshooting] Yuhfhrh:
Thanks, yeah I figured out the security login agent but I still can't figure out why wifi won't remember any passwords (still assuming it's because I flashed an old kernel on the new build.)
[Galaxy Note5 Q&A, Help & Troubleshooting] gundal:
No it's because of secure storage.

Use rom toolbox, build prop editor, search for "secure"

Ro.securestorage.support, set it to false.

Reboot.

Enter passwords one more time (for last time) reboot.

Works
[Galaxy Note5 Q&A, Help & Troubleshooting] Yuhfhrh:
Thanks, that did the trick!

So after freezing security login agent and turning off secure storage, all is well. I still managed 6 hours SOT today too, so battery is top notch.
[Galaxy Note5 Q&A, Help & Troubleshooting] leongzxc:
[MENTION=336863]garyd9[/MENTION]

hello. thank you for creating stock kernel with root!

however, i would just like to ask if this is for 5.1.1 ?

anyway, i understand the risks im taking as i've always been a rooted android user. though its been 3 years since i last used a samsung so most of my samsung knowledge have gone down the drain.

would just like to confirm if the download links in the other thread are kernels for 5.1.1 firmware?

thanks! :)
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
If the second statement was true, then you wouldn't be asking the first question. You'd have already figured out which firmware versions from Samsung contained which android versions. (And then come to the conclusion that there is only ONE version of android currently available for the note 5.)
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
[MENTION=336863]garyd9[/MENTION]

In case you don't have seen: In this thread we are dealing with rooting kernel for 5.1.1 and upwards by modification in sepolicy (last 5 pages) LINK
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I haven't seen it, but I generally avoid "kitchen" type things. Personally, I'd discourage people from using "kitchen" type stuff, as you learn absolutely nothing when doing it that way.

I firmly believe that someone who doesn't understand the HOW shouldn't be rooting their device to begin with. How can a person correct or even troubleshoot problems when they don't understand the process? By posting on XDA and demanding the some RD fix the problem for them?

I know.. I know.. quite a few devs on XDA don't post about the process (and go through great lengths to HIDE the process) instead only posting the results (and then ask for a donation.)

That isn't me.
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
Sorry, seems like you misunderstand my posting:

We are discussing kernel root in general. For the rest you've said I generally agree with you :highfive:
[Galaxy Note5 Q&A, Help & Troubleshooting] leongzxc:
oh! i never thought about that.

thanks anyways.

just thought there could be minor upgrades between multiple 5.1.1 (so i thought it might not be compatible)

i guess i'll read through again when i am flashing your kernel.

thanks :).
[Galaxy Note5 Q&A, Help & Troubleshooting] sajju73:
Hi [MENTION=336863]garyd9[/MENTION] ...any plans for update fw oj5
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Probably not - unless someone finds that the already repacked kernels do NOT work with OJx.
[Galaxy Note5 Q&A, Help & Troubleshooting] mbeutler:
I'm running OJD and it's been pretty solid with your kernel. None of the ongoing issues I have can be blamed on the kernel.
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
They still work - generally - but there's an issue some users reported: WLAN password gets lost/forgotten with every reboot. This was then solved with OJx kernel.
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Added N920TUVU2DOK5 modified kernel. (This is a leaked M for "t" variants) to the dev section thread: Post #5 here: http://xdaforums.com/note5/development/stock-kernels-selinux-enforcing-rootable-t3222333

Some special notes on that leaked TMO image: I can't even begin to support this boot image. I don't have a 't' device (and even if I did, I'd have to walk a 1/4 mile away from my house just to get t-mobile coverage.) As well, the firmware that this goes with is a LEAKED image. It's incomplete and not "done." If something goes wrong, there's no "known good" state with a leaked image to compare with.
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
A bit of a rant... please skip this post.

Samsung sucks. No, really.. They do. Either their kernel devs are among the worst in the industry, or their management is beyond clueless. Either way, I can't understand how any engineer could sleep at night knowing that they put out so many bugs.

Back in APRIL of 2015... 7 months ago... a bug was discovered, diagnosed, and FIXED for the Samsung Galaxy S6 that would cause a device to not go into deep sleep. 7 Months ago.

That EXACT SAME BUG shows up again in the kernels for the Note 5 running 5.1.1. That's August... so 4 months later. Then, with the leaked "M" release that uses a kernel compiled on November 13th, 2015 (for US people... "13 Nov 2015" for everyone else), THE SAME BUG EXISTS. 7 months later. STILL!

I'm sure that Samsung might claim that this bug doesn't impact a device when it's completely stock. However, THAT IS NOT TRUE. On my "c" variant (that was completely stock) I had the deep sleep issue. On my "i" device, I also had it before I rooted it and worked around the problem with sysfs writes. (Of course, being that I was using a 'c' and 'i' device in the USA, I couldn't even talk to their support people about it... not that it would have helped any.)

Okay.. I'm done (for now.) I just can't understand how any engineer can live with themselves when such garbage gets published. I'd have quit or committed suicide long ago if I were in that situation.
[Galaxy Note5 Q&A, Help & Troubleshooting] BarakOsama:
@garyd9, Could you please build a selinux enforcing and rootable stock kernel for N920L variant.

I have attached the boot.img from the latest N920L firmware (AOJ6).
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
You might have. In fact, I was about to download it to do the work on it, but your missing a piece of information I need. Please re-read the first post in this thread.
[Galaxy Note5 Q&A, Help & Troubleshooting] BarakOsama:
Here it is. :)

N920LKLU2AOJ6_N920LLUC2AOJ6_N920LKLU1AOJ6_HOME.tar
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Added here to the first post here: http://xdaforums.com/note5/development/stock-kernels-selinux-enforcing-rootable-t3222333
[Galaxy Note5 Q&A, Help & Troubleshooting] sajju73:
Hi [MENTION=336863]garyd9[/MENTION], Could you please build a selinux enforcing and rootable stock kernel for KSA N920C variant.

Mega link below is for the boot.img from the latest N920C firmware.

N920CXXU2AOJ5_N920COJP2AOJ5_N920CXXU2AOJ3_HOME.tar

Sorry i cld'nt attach zip file here as i don't have option.

https://mega.nz/#!zkIVxDTC!16N4AZ1j5v-AOou5AfWMzN8CVc6--yh6a6-dAfI5S6E
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I'm guessing that "KSA" is a CSC? All the "C" variant phones should use the same kernel (regardless of CSC.) The posted N20C kernel should work for that firmware (though there might be some oddities with secure storage that are revealed and discussed in this thread.)
[Galaxy Note5 Q&A, Help & Troubleshooting] TheUndertaker21:
Hello Im on t mobile. The kernel worked but the multi task button stopped working. It doesn't do anything when i press it
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
See my reply in the other thread you posted this in: http://xdaforums.com/showthread.php?t=3250812
[Galaxy Note5 Q&A, Help & Troubleshooting] pratik_193:
Gary, If you can help with 920G kernel. required boot.img here

Extracted from - N920GDDU2AOJ5_N920GODD2AOJ6_N920GUBU2AOJ3

Indian Base.
[Galaxy Note5 Q&A, Help & Troubleshooting] spikesfire:
Can you make modified bootimg for n920c aoj5 ?

boot.img here: https://www.dropbox.com/s/0yjzks90ow2i4gw/boot.img?dl=0

Extracted from N920CXXU2AOJ5_N920COJV2AOJ3_N920CXXU2AOJ3_HOME
[Galaxy Note5 Q&A, Help & Troubleshooting] Raveen XD:
Hello.. I'm not very familiar with all the technical stuff but I need help because of similar problems like it restarts during a call. I have a rooted phone and from all the searching that I've done it seems like I have to do some flashing the firmware but I dunno which one. I have LMY47X.N9208XX01AOH4. I've read through the first post but it seems like there wasn't one with this? I'm not sure because I'm not the one who rooted my phone.

Also the version of the superSU is v2.49
[Galaxy Note5 Q&A, Help & Troubleshooting] love_rain_2303:
Could you please build a selinux enforcing and rootable THE LASTEST stock kernel for N920L : N920LLUC2AOK5

I have attached boot.img here : https://mega.nz/#!CcF1XYaZ

Extracted from N920LKLU2AOK5_N920LLUC2AOK5_N920LKLU1AOK3_HOME.tar
[Galaxy Note5 Q&A, Help & Troubleshooting] NewtPulsifer:
I tried just unpacking the kernel and repacking it, then flashing it on a stock ROM and still got the notification.

It looks like the bootloader is responsible for that - any chance that it could be modified to no longer check?
[Galaxy Note5 Q&A, Help & Troubleshooting] Idan73:
You could try letting super su root 2.61 beta do it for you from stock. At least till Garyd9 has time to post his repacked image.

Note 5 ?
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
My paying job has been keeping me busy.. sorry for the massive delay in getting back to some of these queries...

Can you please post it someplace with no advertisements? I'm not familiar with "zippyshare" and I hate when I get massive popups and crud when I'm just trying to help someone. I think you should be able to zip up the boot.img and attach it to a post here, even. Edit: working on it..

There's already a 'C' image posted. (see below)

There's already an 'L' image posted.

I've posted several times already that I'm not going to post new repacks for every revision that Samsung puts out.

I'll reply with the exact same string that you quoted: That red notification is normal (and it'll show for ANY modified image.. it IS enforcing.)

Additional info: The kernel boot image doesn't have a signature that the bootloader is looking for. I could probably fake it, but I really have no reason whatsoever to do so.

EDIT: Just so people are clear: If it's a variant I haven't already repacked, I'll do so when I get time. Otherwise, I'm not going to repack only for updated revisions as long as the existing repacks still work. (And that will likely happen when Samsung starts rolling out android 6.)
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I think you're in the wrong thread. I'd suggest finding and using a guide to restore your phone to stock (via ODIN.)
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Done - in the first post here: http://xdaforums.com/note5/development/stock-kernels-selinux-enforcing-rootable-t3222333
[Galaxy Note5 Q&A, Help & Troubleshooting] Ozgurce:
Im using your kernel since you posted. My girlfriend and i have same note 5 (920c). I installed a **** both of them stock oj5. but mine doesnt go to deep sleep. and I go crazy about that before reading your messages on the development thread. (your messages really entertaining and funny by the way:) ) What a **** move on samsung side. So if you tripped knox you can never go back to stock or your device doesnt deep sleep.

SM-N920I cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I'm not sure how to interpret your post. Are you asking about deep sleep? Are you saying that one device goes into deep sleep but another doesn't - and that they are both using the same kernel? Which device are you referring to? (Your post suggests the "c" variant, but your tagline shows a "i" variant.) Keep in mind that there are many possible reasons why a device doesn't go into deep sleep outside of the kernel. Many apps are poorly written and hold the device awake forever.

At the current time, there's no known way to "untrip" KNOX. It's likely a fuse (similar to qualcom's "q-fuse" tech) that can't be reset. It may eventually be possible to hook or replace the code that detects if it's tripped in the normal boot, but the bootloader will still show that it's tripped.
[Galaxy Note5 Q&A, Help & Troubleshooting] Ozgurce:
for clearence;

I have two note 5 (one is used by my girlfriend and never got knox voided and both). of them 920c). I have installed custom rom for know thats 920i" because of that. Mine is knox tripped. I install same stock rom (complete package) to both of them with odin and after opening both of them with no account, no custom apps.. so both of them are as stock as possibld. mine doesnt go to deep sleep and my gfs one goes. So if you tripped knox you cant install the stock image to your device, or it will dont go deep sleep. I hope they fix this in the Marsmallow update but im guessing not. You have to use custom kernel everytime if you tripped knox. I hate samsung for that. Like they are saying "once you go to darkness you can never came back, not enterily." :)

SM-N920I cihazımdan Tapatalk kullanılarak gönderildi