yashsingh1/xdaforums huggingface dataset:
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
No need to clear dalvik or caches for a kernel change (unless the kernel is installing crap into /system.)

I edited my post above... the fstab is fine (support_scfs is removed.) Can you tell me about your device and the boot loop?

How is your device different from a completely stock one? (recovery, and firmware/system)

Also, please describe the boot loop.
[Galaxy Note5 Q&A, Help & Troubleshooting] Jainyankee1993:
Flashed on my SM-N920I as well. Same result. Went into boot loop after Samsung logo. Flashed Arter to get it to boot again. Not a big deal
[Galaxy Note5 Q&A, Help & Troubleshooting] guaneet:
https://goo.gl/mWPHUc

LMY47X.N920TUVU2COI5
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Odd. Those that looped, which method did you use to flash it? I want to repeat...
[Galaxy Note5 Q&A, Help & Troubleshooting] ptfdmedic:
Thanks... Is there one for Tmobile or did I miss it? Either way, thanks for this...:)
[Galaxy Note5 Q&A, Help & Troubleshooting] @Class:
ODIN. The only real difference from stock is TWRP and the kernel.

Edit: Bootloop gets to the Samsung logo then black screens. Logcat does not enable. I have the last_kmesg though. Posting in a minute after it reboots...
[Galaxy Note5 Q&A, Help & Troubleshooting] Jainyankee1993:
I used Philz recovery... Same thing, boots to Samsung logo and then restarts
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Going to hold off putting anymore together until I repeat/resolve the boot looping...

It's odd, as I'm not having the problem at all on a n920i...
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Those with bootloops - are you running encryption?

[MENTION=1306627]@Class[/MENTION], can you please run the following command (from a shell - either adb or android terminal - doesn't matter) and send me the output?

ls -l /dev/block/platform/15570000.ufs/by-name/

I just need to make sure that the partitions are mapped the same as mine.

What I'm really not understanding is the person with n920i having the bootloop. There MUST be something different about their device compared to mine (also an 'i') and the only thing I can think of would be encryption...

It's annoying when I test something for 2 days and it's running perfectly, and then it completely blows up for other people. (Not your fault... just annoying to me.)

A general question: Is it working properly for ANYONE (other than me)? Is it only boot looping for 2 people?

If I can't repeat a problem, I need as many details as I can get to blindly feel my way though... Too much information is significantly better than not enough. (Of course, I can only take guesses right now as to which specific details are significant.)

Gary
[Galaxy Note5 Q&A, Help & Troubleshooting] @Class:
Not encrypted. Also my link above contains the entire last_kmsg.txt, maybe its more helpful.

root@noblelte:/ # ls -l /dev/block/platform/15570000.ufs/by-name/
lrwxrwxrwx root root 2015-10-10 21:44 BOOT -> /dev/block/sda5
lrwxrwxrwx root root 2015-10-10 21:44 BOTA0 -> /dev/block/sda1
lrwxrwxrwx root root 2015-10-10 21:44 BOTA1 -> /dev/block/sda2
lrwxrwxrwx root root 2015-10-10 21:44 CACHE -> /dev/block/sda15
lrwxrwxrwx root root 2015-10-10 21:44 CPEFS -> /dev/block/sdd1
lrwxrwxrwx root root 2015-10-10 21:44 DNT -> /dev/block/sda10
lrwxrwxrwx root root 2015-10-10 21:44 EFS -> /dev/block/sda3
lrwxrwxrwx root root 2015-10-10 21:44 OTA -> /dev/block/sda7
lrwxrwxrwx root root 2015-10-10 21:44 PARAM -> /dev/block/sda4
lrwxrwxrwx root root 2015-10-10 21:44 PERSDATA -> /dev/block/sda13
lrwxrwxrwx root root 2015-10-10 21:44 PERSISTENT -> /dev/block/sda11
lrwxrwxrwx root root 2015-10-10 21:44 RADIO -> /dev/block/sda8
lrwxrwxrwx root root 2015-10-10 21:44 RECOVERY -> /dev/block/sda6
lrwxrwxrwx root root 2015-10-10 21:44 STEADY -> /dev/block/sda12
lrwxrwxrwx root root 2015-10-10 21:44 SYSTEM -> /dev/block/sda14
lrwxrwxrwx root root 2015-10-10 21:44 TOMBSTONES -> /dev/block/sda9
lrwxrwxrwx root root 2015-10-10 21:44 USERDATA -> /dev/block/sda16
root@noblelte:/ #
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Thanks.. I'm going to have to spend some time trying to work this out. Damn puzzles. Oh, I made a copy of that kmesg, so you don't need to keep it around if you don't want to.

Thanks

Gary
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
On that '8' variant, the partition table is different from what i expected. That might explain the loops.. will put another image together tomorrow to test the theory...

That doesn't explain the 'i' variant loop, as it SHOULD have the same partition table as my device.
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Going to lock this thread. There's no longer any need for repacking the stock kernels to make them rootable while still selinux enforcing. The same can be obtained by using SuperSU 2.67 and above by [MENTION=631273]Chainfire[/MENTION]

Quick instructions:

Steps for systemless root (with all known issues resolved) (requires SuperSU 2.67)

1. If your device isn't stock, flash stock firmware via odin. the whole thing. Boot and make sure the device works... While the device is booted, copy the SuperSU 2.67 package to your phone. You'll need it...

2. reboot to ODIN mode, select the option to not restart and flash TWRP.

3. Manually reboot the phone and make sure you boot into TWRP and not a normal boot. (If it boots normally, it might remove TWRP. If that happens, go back to step 2.)

*. From within TWRP, you can OPTIONALLY tells SuperSU to install in a way that might break some poorly written root apps, but leaves the phone in a state so that Android Pay will work. (see below for info on that.)

4. From within TWRP, install the SuperSU package. Reboot. If TWRP offers to root your device DO NOT LET IT.

That's it.. you're done.

* - The option mentioned above can be done from within TWRP by executing the following command at a shell prompt (either from within TWRP, or by obtaining an "adb shell" while in TWRP) before flashing supersu:

echo BINDSYSTEMXBIN=false>>/data/.supersu

(If I screwed up this post, please PM me and I'll fix it when I'm sober.)
[Galaxy Note5 Q&A, Help & Troubleshooting] aamirleo55:
Can you make kernel for N920G variant too ??
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Did you bother to read this thread before asking?
[Galaxy Note5 Q&A, Help & Troubleshooting] aamirleo55:
Sorry, i by mistakely skipped to read that line
[Galaxy Note5 Q&A, Help & Troubleshooting] B!GBOY:
bootloop on nameless rom n920C

Here is a log, I dont know if it helps or not (booted in to recovery to get it)...
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I've updated the thread with the images with a warning about the boot looping. This is REALLY annoying to me as I can't repeat the issue at all. For me, the boot image for the n920I works PERFECTLY installed either via ODIN or TWRP.

I suspect the only difference between my device and other's is that my system partition was virgin stock. Other people had other custom kernels on their devices that altered the system partition. (This is why I dislike "auto-root" boot images. The boot image shouldn't be mucking with the system partition. There is absolutely NO reason why a boot image should be writing to system beyond installing a simple apk or something that's easily reversible.) Of course, despite my personal opinion on the matter, I don't know if it's even related to the issues seen.

For example, it doesn't explain the USERDATA panic seen by [MENTION=1306627]@Class[/MENTION]. It also doesn't explain why he got that panic with the repacked kernel I posted and NOT with spacex or whatever (unless it's due to fs changes.)

BTW, the typical reason why the stock kernel boot loops after /system has been touched is a mount flag that essentially translates to "fail verification of the file system if it's been modified in any way" and another that translates to "if the fs verification fails, panic the kernel and reboot the device." My work around for that was to remove that "modified in any way" flag from the file in the boot image that controls mounting file systems (fstab.)

I wonder if these other kernels have also removed the "panic on fs error" flag...

[MENTION=1306627]@Class[/MENTION], you're back on spaceX, right? It might be interesting to reboot your device and grab the output from "dmesg" to see if there are fs errors similar to the ones you posted earlier in this thread, but that are being ignored instead of causing a kernel panic. They'd happen within the first 45 seconds of the boot...

Anyway, I can't obsess too much over this issue right now. I've wrapped the entire process of modifying the boot image into a linux script that I'll add a bit more commenting to and post here in case someone else wants to mess with this...
[Galaxy Note5 Q&A, Help & Troubleshooting] Ozgurce:
Im using newbootimage_N920CXXU1AOH6 on dr.ketan L2 rom and it works well.
[Galaxy Note5 Q&A, Help & Troubleshooting] @Class:
Here's the dmesg from booting with a mystery kernel (that I found in the SM-N208 how to root thread). I'm not 100% sure on where the source for this kernel is as every function on my phone works including NFC which does not work on the SpaceX and I've had zero random reboots.

dmesg after a successful boot:

https://drive.google.com/file/d/0B8l6BzXcGjjmY2J4dWZBRUhaTjQ/view?usp=sharing
[Galaxy Note5 Q&A, Help & Troubleshooting] Ozgurce:
For proof :)
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
That one doesn't even seem to be doing a filesystem check whatsoever. No check, no error, no panic. I could do that as well, but that's cheating. ;)

That makes me feel only slightly better. Now I need to figure out why it's not working for the other person with an 'i' variant.
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
first of all thx for your effort :good:

as I have tried similar modifications on my N920I kernel while running ketan rom and always failed (bootloop) both paths by_name and sda5, I gave up.

May I summarize that running stock firmware it does work for you? This I haven't tried yet, so ... please and thx for a short hint on it. :highfive:
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Works perfectly for me with a lightly modified N920IDVU1AOH6 firmware. (rooted, some stuff frozen, minor wifi tweaks.)
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
OK, I see and an additional question from me noob on Lollipop (if I may):

We wouldn't face the bootloop problem if we kept our hands away from old rom building with folder structure and flashing to certain paths, right?
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I can't answer that with any certainty. For some, it's working great. For others it isn't. What I have noticed is that when it works, it works perfectly. When it doesn't, it always boot loops. No idea why.
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
Maybe a short look into updater script of involved rom could point it out.

Ketan Rom with your N920I kernel works perfect :good::highfive:
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Maybe... some people have an issue with a mostly stock firmware for a device and this kernel. The only thing I can think of (and it's only a guess) is that there's some conflict between something their previous kernel did (mods to /system or /data) and this boot image.

For example, (and this is just guessing) another kernel might have installed something to set certain kernel parameters after the kernel boots. If those parameters are incompatible with the stock kernel, it could go BOOM.

HOWEVER, to dispute my own guesswork, the boot loop reports are saying that the phone reboots BEFORE the bootanimation. If that's the case, then no normal /system or /data installed app would have had time to do anything.

Or perhaps it's a version of supersu that they have installed being incompatible with the updated sepolicy or enforced seandroid. (Most of the other custom kernels are FORCING superSU installation on boot.) That _shouldn't_ cause a reboot, but it is possible, I guess.

Actually... come to think of it... that might be the problem... The crashes are occurring for those people very early in the boot process.. just before the bootanimation has had time to get going. That's about the same time that zygote is starting... or "app_process64" to be specific. Which, BTW, supersu replaces. (Again, this is just a guess. I honestly have no clue what is causing the crashes for anyone other than [MENTION=1306627]@Class[/MENTION].)

It really is a shame that these other custom kernels are FORCING superSU installation. It prevents users from uninstalling root, and it could lead to incompatible installations of superSU in the future. (Disclaimer: This paragraph is my own personal opinion.)

Strange.. it's all very strange. In theory, it should Just Work... but obviously it isn't for some.
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
So far, I've been able to run this kernel properly with the following 'i' variant firmware:

OH2 for a New Zealand carrier called "Spark" (CSC TNZ)

OH2 for a New Zealand carrier called "2 degrees" (CSC NZC)

OH6 for a Singapore carrier called Singtel (CSC SIN)

(All using the same 'i' OH6 kernel)

...and now to drift completely off topic:

I'd really like to find an open (non-carrier) CSC for the 'I' variant, but I haven't had much luck with that.

One thing I have noticed is that the OH2 firmware is giving me a "detected security threats" warning in smart manager (I already disabled SecurityLogAgent) while the OH6 Singtel firmware didn't. This might be something "fixed" in OH6, but I have no idea what does the security checks (SecurityLogAgent only reports the results of the check) so I can't replace those files.

I'm using OH2 for a while to see if it resolves a bug I had with google/gmail "exchange" (activesync) accounts disappearing. That bug didn't exist for my on a n920c using an OH2 build, so I'm hoping it also doesn't exist on the 'i' variant of OH2. (Although someone else reported having the same bug with an 'i' variant OH2, and another person reported having it with a 't' variant.)

I'm also encountering ANOTHER bug.. but this one occurred with the n920c _and_ n920i (but not the n920a) rooted or not and with all firmware versions: Android Auto will sometimes refuse to read incoming text (SMS) messages. It works some of the time, but not all the time.. Being that this issue wasn't present on the 'a' variant (and everything works perfectly with other android phones I have had in the US), I suspect it might be an issue resulting from the "international" aspects of the phone.
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I might be getting closer to understanding...

For those (other than "@class") who were using this kernel and getting boot loops... was the boot animation starting at all? Umm.. the phone boots up and has a something that says "Samsung Galaxy Note 5" and "powered by android" at the bottom. That's NOT the boot animation.

The boot animation comes after that, and on non-carrier phones is just the "samsung" logo with some sparkly stuff... with a carrier phone you might also get a carrier logo.

So, is the boot animation starting?

The reason I'm asking is that I just did something a little nuts... I dropped a tmobile deodex system partition on my phone. (For no good reason, to be honest), and left my kernel intact. I boot looped, but I got as far as the tmobile carrier logo in the boot animation before it would reboot. In the last log, I see this:

<11>[ 24.459685] [2: init: 1] init: zygote has died four times in 150 secs.. so we will reboot the device

So, at least I know why it rebooted (even if I have nfc why zygote died 4 times.)

---

Same thing in your log:

<11>[ 24.944699] [7: init: 1] init: zygote has died four times in 150 secs.. so we will reboot the device

...and the firmware you are running is based on N920GDDU1AOH7. So, I wonder if it's an issue mixing kernel/firmware versions. If the KERNEL is incompatible with the libraries in system, it would certainly explain zygote dying over and over.. Hmm.. I wonder what might happen if I run a "T" kernel on my "I" device with a "T" firmware...
[Galaxy Note5 Q&A, Help & Troubleshooting] B!GBOY:
yes the "nameless" rom is based on G version. it works on G/I/C... i use it with arter97's kernel, I even tested SpaceX kernel and they both boot. (both C version)

with your kernel it gets past the boot logo and displays the boot animation after a few seconds the boot animation starts from the beginning...
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I know.. damn annoying, too. It's going to be a few days before I can look into again. Things like my job and family keep interfering with what I want to be doing. ;)
[Galaxy Note5 Q&A, Help & Troubleshooting] themoto:
I have my N920C for 4 weeks now didn't root or any thing only reading here on XDA waiting for this.Only thing i want to ask you can i use this

newbootimage for my device	newbootimage_N920CXXU1AOH6.tar.zip

My build number is N920CXXU1AOH4 and this is the bootimage

https://mega.nz/#!bNMmQAbT!4ZO4kUcV96y23lmqQqkJJIm7YrRQt29R0IW7k198oec

Thanks.

I know you don't answer stupid Questions.(sorry)
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I'm not sure I understand the question. I have a n920c image posted in the thread linked in the OP. The "OH6" boot image posted should work on a "OH4" firmware, but there's no way to know for sure without trying it (and I no longer have a 'c' device to test with.)
[Galaxy Note5 Q&A, Help & Troubleshooting] themoto:
Yes that was the question and your answer is the same as [MENTION=5564860]Androidwizzard[/MENTION] gave me before.

When i try it i will let you know (still a little afraid because i'm not a dev.)

thanks.
[Galaxy Note5 Q&A, Help & Troubleshooting] Darkman:
I use the N920C with "OH4" and your Kernel from "OH6" without Issues! :good: work all fine!
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
Well, that answers THAT question. :) Just to be clear, though, it's not "my" kernel. It's simply a ramdisk repack.
[Galaxy Note5 Q&A, Help & Troubleshooting] Idan73:
Well thank you for ramdisk repack.

Flashed zip in twrp from arter kernel. Booted just fine. Seems to run stable, but had this for only couple hours.

On first screen, there's message saying kernel is not se android enforcing, but once the phone boots, in settings says that it is.

Originally, was disappointed when read chainfire post mentioning rootable reference device. Very happy that is not a must,and that you stepped up to fill this void.

Running stock odexed Canadian firmware with xposed and supersu 2.52.

Note 5 ?
[Galaxy Note5 Q&A, Help & Troubleshooting] themoto:
Thanks Garyd9 i flast kernel and installed SU everything is oke,

Note 5 N920C
[Galaxy Note5 Q&A, Help & Troubleshooting] @Class:
Yes for me it crashed before the animation... Always willing to try again :)

So to be honest I doubt its due to something another kernel's done, because I DID flash stock firmware (system.img, cache.img, boot.img, recovery.img) and then this kernel, thinking another kernel was the culprit.

No such luck, it still boot loops. Please note this firmware also has sboot.img ....
[Galaxy Note5 Q&A, Help & Troubleshooting] themoto:
I'm on stockrom with new bootimage i like to try ketans rom.

How did you flash ?,first rom and then this kernel(new bootimage) again?

Thanks.

N920C
[Galaxy Note5 Q&A, Help & Troubleshooting] mbeutler:
I just bought a N920I 32GB and used this kernel to try to get root but had a bit of a rocky start. This is my experience in the hopes that it helps someone else.

This kernel worked great on my phone with 100% bone stock configuration. I then installed SuperSU from the Play Store thinking it would install on it's own. It does not, don't do that. Next I installed TWRP via ODIN. That worked fine, phone still booted and rebooted to recovery just fine. I then flashed SuperSU Beta 2.49 via TWRP and it started bootlooping. In a panic, I used Samsung Smart Switch to recover the phone. This fixed it, with the added bonus of installing the latest H6 firmware. It wouldn't update past H3 prior to that. I then flashed this kernel again, and again it worked great with 100% bone stock configuration. I then installed TWRP and did a full backup, then proceeded to flash SuperSU Beta 2.52. SUCCESS! I'm now fully rooted running the stock rom and this kernel.

Thank you for your work, and I hope this helps some other people.

TLDR

Install latest TWRP via ODIN

TAKE A FULL BACKUP

Flash SuperSU Beta 2.52
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
If you had read OP you wouldn't have missed the fact that at least supersu version 2.51 got to be flashed.
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I added a "N920T" repack to the kernel post (http://xdaforums.com/note5/development/stock-kernels-selinux-enforcing-rootable-t3222333)
[Galaxy Note5 Q&A, Help & Troubleshooting] hin83:
Hi. Can you please make a kernel for Korean Galaxy Note 5 N920S?
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
I'm sorry, but I'm not going to waste my time helping someone who can't even be bothered to read the first posts in a thread.
[Galaxy Note5 Q&A, Help & Troubleshooting] hin83:
Sorry :(

Here you have the Boot.img

Model: SM-N920S (SK Telecom) Korean version

Rom: N920SKSU2AOI8

https://onedrive.live.com/redir?resid=83486E27FF388A76!285&authkey=!ADgg7rK89YOM-W8&ithint=file,img
[Galaxy Note5 Q&A, Help & Troubleshooting] Fmstrat:
Given this:

And this:

Would you recommend using the newbootimage_N920IDVU1AOH6.zip if my kernel is N920IDVU1AOH2, or following the procedure in post 26 (http://xdaforums.com/showpost.php?p=63250893&postcount=26) on the N920IDVU1AOH2 image?

Thanks in advance.
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
The OH6 kernel works perfectly with the OH2 firmware.

I've been using the OH6 kernel posted with the OH2 "new zealand" firmware (both the 2 Degrees firmware and the Spark firmware) with zero issues.
[Galaxy Note5 Q&A, Help & Troubleshooting] mbeutler:
Is anyone else on this kernel noticing poor battery life? This is my 2nd Note 5 (first was N920A) so I have a good reference of where it should be. It seems when the screen is OFF the battery drains as much as 10% per hour. The N920A I had, as well as the HTC One M9 I'm sending back would last several DAYS with the screen off. Nothing shows up out of the ordinary in Gsam. I've read in some of the other kernel threads something about deep sleep being fixed, so I'm wondering if that's the issue here? I have zero other issues. All the features and calls work beautifully. I did notice before flashing this kernel the battery life was normal and would hold a pretty steady charge with the screen off.

---------- Post added at 10:47 PM ---------- Previous post was at 10:43 PM ----------

If you had read the OP you would have noticed it was only TESTED with that version. I tested with an older version and it didn't work. Now we all know. Please try to be a little nicer. I'm only here to help and provide feedback.
[Galaxy Note5 Q&A, Help & Troubleshooting] unnamed777:
I have stock firmware N920CXXU1AOI3 (for Russia), so I've tried closest kernel - newbootimage_N920CXXU1AOH6.zip - and got a bootloop. Unfortunately I don't have backup with stock kernel to give you original boot.img, but I hope N920CXXU1AOI3 on sammobile is the same. Is it possible to get your modification for this version?
[Galaxy Note5 Q&A, Help & Troubleshooting] Androidwizzard:
Very helpful, indeed :rolleyes:

New devices with new kernel and security need updated SuperSu - what a surprise :p

case closed.
[Galaxy Note5 Q&A, Help & Troubleshooting] themoto:
[MENTION=4854414]mbeutler[/MENTION] I have the N920C rooted with this kernel and on stockrom,battery is like before verry good.
[Galaxy Note5 Q&A, Help & Troubleshooting] mbeutler:
I disabled a bunch of Samsung bloatware last night and today I've only gone down 5% in two hours, and that's in a low signal area. I'd say it's fixed now. This phone is awesome now! :victory:
[Galaxy Note5 Q&A, Help & Troubleshooting] garyd9:
There's nothing special here for power management. It's just the stock kernel!