yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 4 Android Development] tattmann:
Where did you get flashpoint 5.1 kernel? I wish this ROM was still being updated. My note 4 is still my daily and still very functional.
[Verizon Galaxy Note 4 Android Development] Modify_inc:
I have 4 batteries for my Note 4 and they all suck! If you'll really happy with yours, please tell me where you ordered yours from. I don't think you can order them directly from Ravpower. Actually, I don't think you can buy any battery for the Note 4 directly from any OEM supplier since they don't make them anymore that I'm aware of.
[Verizon Galaxy Note 4 Android Development] weaverinva:
I have purchased 3 Ravpower batteries for note 4 in our family. Very happy.

https://www.amazon.com/Battery-RAVPower-3220mAh-Replacement-T-Mobile/dp/B072KJRJ45/ref=mp_s_a_1_3?keywords=ravpower+note+4&qid=1571541199&sr=8-3
[Verizon Galaxy Note 4 Android Development] weaverinva:
Whoops. It is Flashpoint.v5 Not 5.1.

https://xdaforums.com/showpost.php?p=78913484&postcount=2064

Download https://androidfilehost.com/?fid=1395089523397893373

Process to install the new kernel below. He talks about cleanup. I installed the .img file from TWRP

https://xdaforums.com/showpost.php?p=78811009&postcount=2037

Also I am using the file from above post in Kernel Aduitor. All fantastic.....
[Verizon Galaxy Note 4 Android Development] tattmann:
[MENTION=959426]weaverinva[/MENTION], thank you for this. I must have missed some things, been a while since I've needed to flash anything. Considering I'm already on cql2, I wonder if I need to flash cql1 or stay on cql2. Since I'm still on modestrom v11, has there been any newer releases? I haven't found anything newer on here.
[Verizon Galaxy Note 4 Android Development] weaverinva:
You are welcome. Hit the thanks button on other posts if you think about it. Certainly for [MENTION=5285430]kevintm78[/MENTION] posts.

There is no cql2 that I know of. Modest v11 is newest, so you could just do the kernel procedure.

Do you find your phone getting hot or hanging at all?
[Verizon Galaxy Note 4 Android Development] tattmann:
Cql2 is listed ( it says how to update bootloader from cpd1 to cql2) on the second post as a download along with all the other regular downloads for this ROM, up to 3.1 flashpoint. This is why it surprised me about flashpoint 5. As for my phone overheating or hanging? Honestly I am on flashpoint 1. Reason is because any updated kernels were causing my phone to overheat. V1 didn't cause this. I posted about it but nobody could give me any ideas as to why. I rooted and ROM changed 2 matching phones and they both did the same thing. No idea why. V1 doesn't really hang on me very often, (in fact its extremely rare) and runs great. I may try out v5 and see if it changes anything.
[Verizon Galaxy Note 4 Android Development] weaverinva:
Thank you! I may want to try v1. Is there a download location please? Also are you using v1 with modest v11?

I would like to try a combo that is stable. I have 2 phones and they have become more unstable especially with heat across time.
[Verizon Galaxy Note 4 Android Development] weaverinva:
USB Debugging?

Anyone able to get USB Debugging working on this rom with adb? Mine says 'unauthorized' There is also no way to revoke or clear USB Debug authorizations as the menu option under developer options is missing.

Anyone found a way to get USB debugging working?

I would like to use Helium to move some of my applications to a non root phone for my wife.

Thank you for any comments!
[Verizon Galaxy Note 4 Android Development] weaverinva:
I have realized that for me Magisk 18.1 does not work. The original flash of Modest.v11 does work and I will stick with that version and not upgrade. Not sure if I will attempt xposed again. Cleaned up boot image with a Magisk uninstaller and then dirty flashed Modest.v11 again.

Seems clean....
[Verizon Galaxy Note 4 Android Development] kevintm78:
Did you get USB debugging working? I thought I had replied to this post yesterday but I must have not hit the send button.

Just in case, I was going to suggest trying to run the kill server command before the device check command..

adb kill-server

Then

adb devices

You should get the prompt for the rsa fingerprint on your phone at that point.
[Verizon Galaxy Note 4 Android Development] weaverinva:
Thank you [MENTION=5285430]kevintm78[/MENTION] for continuing to respond to things!

Two things:

1) I have tried the kill-server first. I am not using the fingerprint authorization for my phone and it does not prompt me for anything when I connect via MTP via USB and try 'adb devices'. Do I need to turn fingerprint on? I searched and one guy on xda was replacing the adb key file in /data/misc but that did not work for me either. Any reason why the Revoke authorizations is not present?

2) I continue to have random lockups on my phone. Have three Vzw Note 4s. Have redirty flashed original Modest.v11 on current phone. Kept Magisk 15.3 because thought 18.1 seemed to crash and reboot randomly but 15.3 is also doing this. So that may not be it. Recently flashed from scratch again. I never restore system apps or their data from TiBackup. The only thing I did restore were my wifi access points with TB. Perhaps that is a problem.

Would copying /data/media from another rom for particular user app data cause any problems? I would not think so. I have some book software that download is 2.5GB.

I just want my system to be clean again and not hang and reboot. If many of you don't have this issue, then I may need to rerom again. Your wisdom for 'most stable rom' appreciated. On all CQL1. Should I consider not using Magisk and using SuperSU? Never installing exposed?

I do have greenify installed. I had xposed installed (87.3 topjohnwu) on top of Magisk with same modules but not installed now after Magisk uninstall and dirty reflash and still have the reboot issue.

Sorry for my long post. Just can't get this thing to be stable for over a day now. I am a troubleshooter and this is driving me crazy.

Thank you for any comments. Peace.

---------- Post added at 06:52 PM ---------- Previous post was at 06:48 PM ----------

[MENTION=5285430]kevintm78[/MENTION]

Any chance you have the v1 or your kernel hanging around somewhere? Someone else said it was more stable.
[Verizon Galaxy Note 4 Android Development] kevintm78:
For your the adb issues I would try a different kernel just to rule that out. I wasn't able to find a copy of v1 though, I have quite a few different versions that I had tested at one point but I couldn't find the one that was released. As far the fingerprint thing, I was referring to the prompt that you get on your phone when your cpu is asking for authorization to connect via adb. The prompt refers to the key that is saved on your cpu as an RSA Fingerprint, a series of numbers that distinguishes one phone from another. It's referred to as an RSA Key on the cpu though so it's kind of confusing. Flashpoint v3.1 is adb permissive so that one should definitely connect without issues.

Another thing you might try is to install the Samsung drivers again. You can find it here.

I'm wondering if you have to already have granted some authorizations for the "revoke authorizations" button to show up in developer settings. I do have the option on my end but since mine has been connected already that may be the difference.

My setup is currently this:

Rom- Modest v11

Kernel - Flashpoint v5

Root- Magisk v20.1

Modules- busybox and systemless hosts (for adblocker)

I'm not having any lag issues but I did get a random reboot about 4 or 5 days ago. I think that was due to a bad app that I was testing, a clone of the TerrariumTV app. It may not hurt to try and flash a "safe" stock firmware and then start over with modest v11. I think your restore process is pretty similar to mine so you should be good on that front.

Worst case scenario, it's a hardware problem. My spare Note 4 started having read/write failure several months ago and so far I haven't had any luck with trying to fix it. To make matters worse, all 3 of my batteries are at least 3 years old so even on my good phone it tends to shut down at about 15% battery life.
[Verizon Galaxy Note 4 Android Development] kevintm78:
Just in case anyone doesn't check the general section, I just made a post about how you can activate dark mode for viper 2.7, the Google playstore, photos, and possibly more. See this post for more info and instructions.
[Verizon Galaxy Note 4 Android Development] kevintm78:
I need to apologize to you, I was messing with my Note 4 that's suffering from read failure and had installed a fresh copy of Modest v11. I wasn't able to get adb working either until I flashed another kernel. Oddly enough, the kernel I flashed is the same kernel that's included in the rom. I either made slight changes to it before I released the kernel as a stand alone or there's something wrong with the way it gets installed initially.

This is the kernel that I flashed. It's Flashpoint v3.1- no root, so you'll have to reflash Magisk. The latest stable version is working well for me, but you can use what you're comfortable with. You might also have to reenter your wifi passwords.

I'm sorry about giving you the run around. I'll try to get the time to fix some of these bugs and update this rom. Unfortunately, ever since my test phone has been on the fritz I've been a little hesitant to put my good phone through the kind of abuse that constant wipes, flashes, rinse, and repeat tends to bring. But some of these fixes are straight forward enough and I feel like I can at least do that much.
[Verizon Galaxy Note 4 Android Development] ForestCat:
I flashed the MODest ROM, encountered the adb issue, so I flashed the Flashpoint.v3.1-no.root kernel.

ADB is back.

No root, so I installed Magisk-v20.1.zip via TWRP.

Since I'm totally new to this phone/Samsung (coming from Motorola), I need to ask something:

Should I be worried that in both the above cases, I needed to pull the battery to get the phone to boot after the flash/install was finished(I hope...) and the screen went black?

After I flashed the MODest ROM, there were a few reboots, and a time when I thought the phone was OFF, black screen, no LED, etc., but it eventually rebooted on it's own.

EDIT: If I do the "standard" TWRP factory reset, the phone is stuck on the fading Samsung logo screen for AT LEAST five minutes. Is that what you guys are experiencing, or is my phone hosed?

Making me pretty nervous not knowing when/if to pull a battery...

Thanks for any insights from long-time Galaxy users.
[Verizon Galaxy Note 4 Android Development] kevintm78:
The edit situation is normal. If you do a factory reset it wipes the dalvik cache so it has to rebuild on the next boot. That can take 10-15 minutes for the phone to boot back up. It will be on the Samsung logo splash screen, if it's not and the screen is just black then there's a problem.

The other problems your facing could be a bad install, contaminated install (something left over from the previously installed system), or (worse case scenario) faulty hardware.

There are a lot of great things about this phone but one huge negative is that there is a real possibility that your hardware might fail. Especially in the case of emmc read/write failure. That requires a new motherboard.

Some of the things you described are the exact symptoms of emmc failure. I would first try to reinstall the rom. Do a complete wipe and also format your internal sdcard and go from there.

Keep in mind that this is basically a stock rom. You might run into some bugs here and there but overall it should work as good as stock. If the reinstall doesn't work I would see if you could return the phone for a refund and if a refund is not an option then you could try a different rom to see if you have better luck. If that doesn't work then Odin flash back to complete stock just to make sure.
[Verizon Galaxy Note 4 Android Development] crosis38:
WiFi not Working - Cant Turn On!

I flashed the ROM as instructed, also flashed the CQL1 Modem Upgrade. Was able to boot up fine. Everything works fine, from what i can tell. Mobile Operator (not Verizon) works along with 3G. However WiFi is NOT ABLE TO TURN ON. I've tried to turn it on but it refuses. Bluetooth works fine -- i can turn it ON. Power Saving mode is OFF. Battery is 60% charged at the moment.

I previously had Resurrection Remix P v7 installed just fine. Everything worked. ** The bootloader was unlocked at that time for Resurrection.

Any ideas?

My device:

Samsung Galaxy Note 4 SM-N910V

N910VVRU2CQL1

trltevzw
[Verizon Galaxy Note 4 Android Development] kevintm78:
Typically when the wifi is not working (ie. Wifi won't turn on) that indicates an outdated bootloader. You can check with this app. If the bootloader ends with BPA1 (which is a lollipop bootloader) then you'll need to update it to at least CPD1 (the first mm bootloader) or newer to get wifi working on a TW rom.
[Verizon Galaxy Note 4 Android Development] ForestCat:
Yup. Bad phone. And two bad replacements (in different ways). Got smart(I hope) & purchased this one from a private user vs. some scumbag shop reselling minimally 'tested' mint condition warranty returns. I'm learning there were substantial h/w issues w/ the Note 4 in the beginning. I'll bet most of those warranty returns for rapid battery drain, GPS problems, eMMC problems, etc. were 'bulk purchased' and are being sold on ebay, etc.

But I digress...

I'm currently bootloader-unlocked and rooted on stock 6.0.1

2 questions:

1) Does your Modest ROM retain ALL of the S Pen functionality of stock, as well as all of the desirable touchwiz stuff like multitasking/split windows, etc?

2) Is the SD card created by the unlock script worth keeping/of any possible value in unbricking my phone due to future stupidness, etc on my part?

2a) If so, could I just copy the contents to another FAT formatted 80MB partition on a small, cheap card? Hate to waste a 32g SanDisk ExtremePlus if I can avoid it

Thanks again.
[Verizon Galaxy Note 4 Android Development] nuclear_bullet:
damn, I should've posted my eBay link, I sold my pristine Note 4 that I've been babying last year when I moved onto my Note 9. I actually kinda regret it and glad that many of you on this thread is still rocking the Note 4. Keep that for as long as you can, the ROM authors are Saints, extending the life of this little gem of an Android phone.

My Note 9 does everything better than my Note 4 except for two aspects: The curved edges are serioulsy annoying, as I remote desktop into my Windows machines quite often and the taskbar is always on the curved edges, which makes pointing and clicking on it a nightmare even with the S-Pen, and the battery is sealed in a coffin so once I noticed the wear on it, it's doom from there unless I open it up and swap the battery out.

My Note 4 was truly a needle in a haystack of all the shady listings I saw on eBay. I had a magnetic micro-USB port, so the port were always covered and sealed, and had only a handful of plug/un-plug so it was pristine. The 3.5mm was never used so I had a 3.5mm rubber dust plug on it at all time. I used Airglass since the tempered kind left a halo around the edges, airglass was awesome that it stuck like plastic but had properties of glass, and my Note 4 was always wrapped in rugged cases, which made the damn thing bulky, but it prevented any drops or slips since the sides had these awesome grips on it.

I truly, truly regret my Note 9 purchase. There's really nothing the Note 4 can't do within my limited scope of usage.
[Verizon Galaxy Note 4 Android Development] BeckPC:
The Note 4 had the IR Blaster, which I still use. I owned the Note 8 and now have the Note 10. I miss that feature. I really dislike the curved edges as well. It makes it difficult to clip a picture, or write a note. I too have the mag safe adapters and love them. I have them on all my devices now. The other thing I don't really like about the newer notes is the size. It's skinny and taller than the Note 4. It doesn't fit my pocket the same way and is more difficult to use with one hand. The camera is nicer and takes great pictures, but after 5 years of improvements, it had better be good.

To this day, I still say the Note 4 was the BEST device Samsung ever made. I can still do more with it than any Apple user can. I love being able to replace my batteries and soon we'll be running Android 10 just like the newer phones. I have two spares that I use (one with a SIM and one without). They are my media devices. I watch TV on them most of the time. I don't regret buying the newer devices, but I still cherish my Note 4 just as much as I did when I got it over five years ago. I bought it on Day 1 and got the T-Shirt to prove it. Samsung was at the Verizon store handing out shirts. I got one. It says "The Next Big Thing Is Here".

What I miss about having a rooted phone is the ability to back up completely, having access to tweak settings and install custom software to make it run faster, smoother, and use less battery. That's why I keep my Note's around and they can last up to a week on a single charge.

If you want a 'close to stock ROM', this ROM is the one to get. If you want to be brave and try something new, go with Android 9 and select Havoc's ROM for the Note 4. It's official now and 'most' things work. There are a few limitations such as no screen sharing, and no pen support, but otherwise it works very well.

I gave Kevin another Note 4 a few weeks ago, so I'm expecting 'big' things from him too... and very soon. Let's hope they last a bit longer and don't give us MMC errors. I already have two dead ones here with that same problem. Electronics don't last forever, but let's keep them lasting as long as possible.

Long Live the Note 4! :)

---------- Post added at 11:04 AM ---------- Previous post was at 10:59 AM ----------

1. Yes, the S Pen works fully. This ROM is basically stock with a few enhancements.

2. The SD card is reformatted and resized to 18MB when the rooting procedure is done. You will need to wipe and reformat to use it again. I can guarantee you will NEVER use it, so reclaim your space and use the card. If you ever wanted to unroot, just flash back to a real STOCK ROM.

2a. There is not a need to save it. It does contain the actual serial number of your device, but I've rooted over a dozen Note 4 devices and NEVER had to go back. I use a little program on my PC called 'SD Formatter' to clear it up and reclaim the card.
[Verizon Galaxy Note 4 Android Development] ForestCat:
Excellent. Thanks, man. Yeah, I did exhaustive research before settling on the Note 4 as a replacement for my beloved 7 year-old Razr HD Maxx, killed by the GPS 2019 Week rollover bug.

RE: eMMC and the inevitable death of electronics, not sure I agree. I have 4 Razr HD Maxx's, they are all bootloader unlocked, rooted, etc., and they are PERFECT electronically. What I think I understand re: the Note 4 eMMC issue is that it is a combination of a bad part choice by Samsung and/or a mfg/design issue leading to the failure of the solder joints under the BGA chip in question. It is, of course, exacerbated by heat. Lead-free solder and defective Chinese electrolytic capacitors were the plague of a LOT of electronics from that era. But I don't think well-designed/built, quality-component electronics are doomed to eventual failure. I have a basement full of vintage synthesizers and pro audio stuff from the 80-90's and most of it works flawlessly, other than some dirty pots/encoders, etc.

What I'm hoping is that w/ the Note 4, if you find a "good one", that it'll keep on tickin'.

But I have adopted a policy that any flashing, etc on my Note 4 will be w/ the battery cover off and the phone resting on a paper towel over an ice pack. Cheap insurance.

---------- Post added at 11:09 AM ---------- Previous post was at 10:50 AM ----------

RE: The ADB ISSUE-

So, I have a hunch this is not kernel version-related as much as something perhaps related to flash order, etc. Read on...

I started w/ a N910V on a fresh Stock 6.0.1, bootloader unlocked, ~90% battery.

In TWRP 3.3.1-0, I wiped EVERYTHING twice (except USB/SDCard)

I queued up MODest 11 and Flashpoint 5, & let 'er rip

When the phone rebooted, and at about the time it would have been optimizing apps, I got a low battery warning, and the phone shut off. Plugged in a charger, and it was reading 0%. Pulled the plug and the battery, held power button for ~10 sec, reinstalled battery. Plugged in charger, now reading about 60% or so. Restarted the phone, and things progressed as usual, but I don't remember if it got around to optimizing the apps (green screen w/ gears).

Flashed Magisk-v20.1 in TWRP

Phone rebooted w/o incident.

Sideloaded Root Explorer 4.2, but it wouldn't run, "Root Explorer has stopped", etc. Hmmm.

Tried to connect from PC via ADB, device was 'unauthorized', an there was NO "Revoke USB debugging authorizations" in the dev options

Hmmm. OK, flashed kernel back to Flashpoint 3.1.

IMMEDIATELY checked dev options and 'Revoke USB debugging authorizations' was BACK.

Just for sh!ts and giggles, flashed back to Flashpoint 5 again.

Guess what? Revoke USB debugging authorizations' was STILL THERE, and ABD is working. Go figure.

Hopefully this is of some value to somebody.
[Verizon Galaxy Note 4 Android Development] kevintm78:
Couldn't have said it better.

Thanks again for that note 4. For those that don't know this is the second note 4 [MENTION=7749128]BeckPC[/MENTION] has given me. He's been absolutely invaluable to me the last several years and without his help I would have been out of commission several times already. I'm going to try my best to put it to good use.

Lately I've been trying to do some of the ground work to get android 10 (lineageOS) up and running. I've finally got my builds to finish but they are not booting up. Still trying to figure that out but at the very least it's progress.
[Verizon Galaxy Note 4 Android Development] kevintm78:
There's a value set in the default.prop in the kernel ramdisk that is set wrong. Since v5 is packaged with anykernel the wrong value doesn't get overwritten like it does with v3.1 which is replacing the entire boot.img (ramdisk + zImage + dtb). The best part of anykernel is that it only touches what you specify in the anykernel script but that's also what's working against us. Until recently I didn't know there was an issue with adb so the changes weren't added to the script.

In a nutshell :

Flashing v5 only= adb still broke

Flashing 3.1 only= adb works

Flashing v3.1 and then v5= adb works

Flashing stock CQL1 kernel= adb works

CQL1 + v5= adb works

I hope that makes sense. It's been a long weekend at work and my brain is feeling a little fuzzy.
[Verizon Galaxy Note 4 Android Development] ForestCat:
Makes perfect sense. Thanks.

I'm not sure if this thread is the best place to ask this, but it's loosely relate to this ROM, so...

What are the options, if any, for skinning/theming/generally altering the appearance of the UI in MODest 11? I mean, aside from another launcher. I know the question is a little general, but the answers are plenty when you're talking about non-stock-based ROMS. Not so much so with the TouchWiz stuff.

I'm not averse to cracking open apks, etc., but Samsung has just made things miserable with the.pio and .qmg nonsense.

I got a hold of Samsung Mobile Theme Editor v 7, installed it, got past the sign in crap, made a few test changes, pressed the "Apply To Device" button, and got "This theme is not supported by the connected device".

I'd much rather season various ui components to my own (bad) taste, but I'm open to any suggestions/tools at this point.

Other than wanting to make the ui appearance 'my own', the ROM w/ Kernel 5 has been amazingly well behaved so far. I haven't debloated yet or installed Xposed yet, but that's soon.

Thanks so much for the dedicated work & encyclopedic thread. Fantastic resource.