Develop Bugs

How to properly downgrade from Lollipop back to NK2 KitKat?

I've got a Lollipop 5.1 ROM installed but want to go back to the stock NK2 Touchwiz ROM. When I flash the ROM zip in CWM the phone isn't able to boot into the OS - it tries to, fails, and then automatically boots back into recovery.

You must do a factory reset and use odin to flash the full firmware NK2 in order to go back to kitkat.
Pp.

PanchoPlanet said:
You must do a factory reset and use odin to flash the full firmware NK2 in order to go back to kitkat.
Pp.
Click to expand...
Click to collapse
I see. So in general, to downgrade you want to use Odin. To upgrade you can flash directly within CWM?

fuzzybabybunny said:
I see. So in general, to downgrade you want to use Odin. To upgrade you can flash directly within CWM?
Click to expand...
Click to collapse
Downgrading involves full firmware thus needing odin to install the full firmware.
CWM basically flashes just a rom or update and doesnt install full firmware which would be needed to downgrade, upgrade or switch operating system.
Pp.

Wow, I think I'm officially done with third party unofficial ROMs.
Now I'm reading that its impossible to downgrade even with Odin due to KNOX?
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
"if i upgraded to NB4, is it possible to go back to MK2 or MDL via the same method with odin?
no you can no longer downgrade and will have the knox bootloader"

fuzzybabybunny said:
Wow, I think I'm officially done with third party unofficial ROMs.
Now I'm reading that its impossible to downgrade even with Odin due to KNOX?
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
"if i upgraded to NB4, is it possible to go back to MK2 or MDL via the same method with odin?
no you can no longer downgrade and will have the knox bootloader"
Click to expand...
Click to collapse
Yes, but the knox thing is only an issue if your phone is under a year old and under Samsung warranty, in which case if Samsung gets your phone for some warranty related work they can technically refuse or charge you for repairs.
The newer knox firmwares are improved over the older version, better call quality, faster processing, better memory management, so it's not a bad thing to upgrade your firmware, it's actually beneficial.
I knoxed out 30 minutes after I had phone out of the box when I got my S4, made sure there where no issues everything worked the way it was supposed to and rooted and got rid of the bloatware.
And still have original phone, no returns or exchanges.
Pp.

your help urgent please

i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks

And here we go again...... What version software was installed before trying to update? Were you rooted?

zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....

done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS

zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?

rooted thru odin
now i can't get to OS ,just show samsung sign and loops

Flash whatever firmware u was on in odin

zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.

tried to do thru sd card ,but i get :
dm-verity verification failed

can i just go back to 5.1 lollipop with an official stock rom via odin ?

zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom

any firmware can get me back to lollipop with odin !!!

zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk

samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.

xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk

i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip

Marshmallow upgrade from Rooted BOB7 and no Odin

So the story is about 9 months ago my Galaxy note 4's USB port got messed up. I cannot charge my phone without using an external battery cradle, nor can I connect my phone to computer and sync/odin. I am stuck on a rooted BOB7 rom specifically the noterized rom stable 3. I know I cannot jump from BOB7 to COK1 etc... via flashing. I was wondering if the jump to marshmallow from lollipop would work.

Hmmm. let's see. I think you might be in a bad situation. You can't install ota updates if you're rooted and/or have a custom recovery. So those are the two biggest hurdles. You can use supersu to unroot so do that first. Next you will need to see if you can get a flashable stock OB7 recovery and flash it. Another thing that may be a problem is the debloated rom you're currently running. That may or may not cause problems with downloading and installing the ota's. I can make a flashable zip for you for the stock recovery but you first will need to download and flash my stock OB7 rom. Look for it here in the Sprint N4 forums.
Steps to success:
1. Download and flash stock rooted OB7 rom.
2. Use SuperSu app to unroot and uninstall supersu
3. Find a flashable stock OB7 recovery (I will provide if needed)
4. Do a factory reset by rebooting to the stock recovery
5. Once phone boots up, setup accounts, etc per usual and go to settings/system update and check for updates.
6. Let the update download and try to install it. You should have success. If it is successful then follow update instructions and once your phone is fully updated then you should check for updates again until you are fully updated to the latest MM 6.0 ota.
PM me if you need a flashable stock OB7 recovery or other help.
Good luck.

Thank you
Thank you very much tx_dbs_tx, you are a life saver! I have been stuck for the past 9 months.

tx_dbs_tx said:
Hmmm. let's see. I think you might be in a bad situation. You can't install ota updates if you're rooted and/or have a custom recovery. So those are the two biggest hurdles. You can use supersu to unroot so do that first. Next you will need to see if you can get a flashable stock OB7 recovery and flash it. Another thing that may be a problem is the debloated rom you're currently running. That may or may not cause problems with downloading and installing the ota's. I can make a flashable zip for you for the stock recovery but you first will need to download and flash my stock OB7 rom. Look for it here in the Sprint N4 forums.
Steps to success:
1. Download and flash stock rooted OB7 rom.
2. Use SuperSu app to unroot and uninstall supersu
3. Find a flashable stock OB7 recovery (I will provide if needed)
4. Do a factory reset by rebooting to the stock recovery
5. Once phone boots up, setup accounts, etc per usual and go to settings/system update and check for updates.
6. Let the update download and try to install it. You should have success. If it is successful then follow update instructions and once your phone is fully updated then you should check for updates again until you are fully updated to the latest MM 6.0 ota.
PM me if you need a flashable stock OB7 recovery or other help.
Good luck.
Click to expand...
Click to collapse
Is there a chance of doing the same on OG5? Using OBAR

So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl

Can someone confirm with me, that sending picture messages won't go through. Or is it just me?

cherylbaker said:
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Click to expand...
Click to collapse
Sorry for the late reply Cheryl. There is no reason not to update your software to Marshmallow 6.0. Typically updates bring improved performance and battery life as well as other software optimizations which are always better than previous software builds. You should backup your photo's etc before installing any update just in case. If you're one of those who doesn't like change and is content with your phone with it's current software then you don't have to update the software as long as there isn't a critical update that would prevent something from working on your phone unless you take the update. If everything works and your happy then you can leave it as is. But if you are interested in improved battery life and overall performance as well as new security features and policies of android, then by all means update your software the first chance you get. there are no drawbacks that i have noticed or read from any other users. Marshmallow is a go! :good:

cherylbaker said:
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Click to expand...
Click to collapse
OB7 is the newest bootloader that can be downgraded to kitkat.
on kitkat it's a lot easier to retrieve your MSL number, and at the time there was no xposed for Samsung lolly

Sterist said:
OB7 is the newest bootloader that can be downgraded to kitkat.
on kitkat it's a lot easier to retrieve your MSL number, and at the time there was no xposed for Samsung lolly
Click to expand...
Click to collapse
So that was it. You cannot downgrade to kk? I am sure at the time that was important but i havnt had any interest in downgrading b4 so doubt i will now. I know bob7 was the most popular for roms at the time also but honestly i am past my flashaholic phase and just want to havebrhe best phone i can.
Is there hot spot and root for mm? Hotspot is probably the only thing i really care about and even that isn't as important these days
cheryl

cherylbaker said:
So that was it. You cannot downgrade to kk? I am sure at the time that was important but i havnt had any interest in downgrading b4 so doubt i will now. I know bob7 was the most popular for roms at the time also but honestly i am past my flashaholic phase and just want to havebrhe best phone i can.
Is there hot spot and root for mm? Hotspot is probably the only thing i really care about and even that isn't as important these days
cheryl
Click to expand...
Click to collapse
if you don't have your MSL, and don't know where to find/how to get Galaxy Tools, and you still have a while left on contract, it wouldn't hurt to downgrade and grab your MSL first then jump straight to MM

Does anyone have a link to a stock OB7 recovery? All that I find are the odin variants.

kjtrini1 said:
Does anyone have a link to a stock OB7 recovery? All that I find are the odin variants.
Click to expand...
Click to collapse
I don't know how to extract it from a .tar but I know it can be acquired it like this:
1. full backup in TWRP
2. copy the backup to pc for safekeeping
3. odin full OB7 stock tar
4. without flashing TWRP, root using CF auto root*
5. install Flashify from Google Play
6. backup recovery
7. copy the backup to pc for uploading
*I don't know which version (if applicable) as I never use that method to root. sorry
obviously you wouldn't be able to do this yourself, you would need someone on the forum with OB7 bootloader to do this, and honestly, without knowing how to extract / find it in the.tar I still think that would take a lot less time and effort than this method lol

Need to unroot and can't

I rooted my n910p a while back with the emotion kernel and twrp. My phone has been messing up even before rooting which is why I rooted in the first place. All I need to know/want to do is unroot and go back to stock. I understand how to do it with odin but everytime I download the stock rom files I always get an error such as pit partition or something. I just want to unroot so that I can get another phone without them noticing its rooted. I know when you turn the phone on it says things in the top left like android is se enforcing. Is there a way to unroot to where they can't tell its been rooted?
P.S. I know I'm all over the place with this post ive been trying to unroot all day with no luck. Please help somebody!

shutdafup9 said:
I rooted my n910p a while back with the emotion kernel and twrp. My phone has been messing up even before rooting which is why I rooted in the first place. All I need to know/want to do is unroot and go back to stock. I understand how to do it with odin but everytime I download the stock rom files I always get an error such as pit partition or something. I just want to unroot so that I can get another phone without them noticing its rooted. I know when you turn the phone on it says things in the top left like android is se enforcing. Is there a way to unroot to where they can't tell its been rooted?
P.S. I know I'm all over the place with this post ive been trying to unroot all day with no luck. Please help somebody!
Click to expand...
Click to collapse
Which tar file are you trying to Odin? From my understanding, you have to Odin the tar ROM that installed the last pit file. So you might have to download and try each individual one till it takes it. Are you on MM or LP?

ianmb said:
Which tar file are you trying to Odin? From my understanding, you have to Odin the tar ROM that installed the last pit file. So you might have to download and try each individual one till it takes it. Are you on MM or LP?
Click to expand...
Click to collapse
makes sense, but what do you do when you have something like Noterized, like me, and in this case, my build is OB7, but my bootloader and baseband are OE1... I had the same odin error recently, and i am going to try to odin the full OB7 again, but if that does not work, there is no full OE1 rom, it was just a security update... and thanks much for your help, ianmb...

mlongue1 said:
makes sense, but what do you do when you have something like Noterized, like me, and in this case, my build is OB7, but my bootloader and baseband are OE1... I had the same odin error recently, and i am going to try to odin the full OB7 again, but if that does not work, there is no full OE1 rom, it was just a security update... and thanks much for your help, ianmb...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=66566610
Check this out

thanks, man…

Back to 5.1.1?

Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!

Ind3lible said:
Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!
Click to expand...
Click to collapse
Yes you can odin back to 5.1.1. Just make sure you flash the correct tar.

Ind3lible said:
Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!
Click to expand...
Click to collapse
Better not. You can go up in version , but not down.

yes
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.

chrisresponsibility said:
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.
Click to expand...
Click to collapse
Viper works fine on MM. Either flash viper installation zip than the subpolicy zip from here, http://forum.xda-developers.com/showthread.php?t=3355270 .Or a permissive kernel like beastmode, from here http://forum.xda-developers.com/showthread.php?t=3284505 .

chrisresponsibility said:
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.
Click to expand...
Click to collapse
Awesome, thank you so much!! So OK1 was the last lollipop right? I have the TAR but where is the twrp. I have not rooted the note 4 ever. So don't know much how to get TWRP on it yet.

Ind3lible said:
Awesome, thank you so much!! So OK1 was the last lollipop right? I have the TAR but where is the twrp. I have not rooted the note 4 ever. So don't know much how to get TWRP on it yet.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=66903690
Sent from my SM-N910P using Tapatalk

samep said:
http://forum.xda-developers.com/showthread.php?p=66903690
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks brotha!

i Have a bootloop when flash OK1 From PD1...... On What Version may Downgrade From PD1?

michael_0302 said:
i Have a bootloop when flash OK1 From PD1...... On What Version may Downgrade From PD1?
Click to expand...
Click to collapse
You flashed the full stock tar OK1 and got a bootloop? Just a guess but since Lollipop and Marshmallow differ on app optimization, I think you have to wipe data to get it to boot. Factory reset in stock recovery or wipe data in custom recovery.
If that's the case, you can take data to marshmallow (it seems to anticipate that but may still need factory reset adb ItsOn completely removed after root for some rooted users but also factory reset seemed to apply to PC1 OTA for un-rooted users). But maybe you can't take optimized apps back to Lollipop? Confirm that if it works.
Lollipop may be trying to rebuild the dalvik-cache but gets tripped up by the odex files in the oat folders of every app in data partition. Result could be bad boot. Loops.
Sent from my SM-N910P using Tapatalk

Thread moved to correct forums.

samep said:
You flashed the full stock tar OK1 and got a bootloop? Just a guess but since Lollipop and Marshmallow differ on app optimization, I think you have to wipe data to get it to boot. Factory reset in stock recovery or wipe data in custom recovery.
If that's the case, you can take data to marshmallow (it seems to anticipate that but may still need factory reset adb ItsOn completely removed after root for some rooted users but also factory reset seemed to apply to PC1 OTA for un-rooted users). But maybe you can't take optimized apps back to Lollipop? Confirm that if it works.
Lollipop may be trying to rebuild the dalvik-cache but gets tripped up by the odex files in the oat folders of every app in data partition. Result could be bad boot. Loops.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Did you get this working? I still have not flashed but am scared now lol =(

Ind3lible said:
Did you get this working? I still have not flashed but am scared now lol =(
Click to expand...
Click to collapse
Not sure of your question but in context, what I did was flash the OK1 bootloader, factory reset and restore Lollipop TWRP backup. I suggested to the user I quoted that his boot loop was caused by app optimization of MM. He could confirm that by factory resetting and attempt to boot. I didn't get a confirmation.
The advice I would give is to first backup and then make a clean break with Marshmallow data if intent is to temporarily go back to Lollipop. The bootloader method is ideal for users with Lollipop backup to restore but for those without the Lollipop backup, I think the full tar is best.
But remember to make sure reactivation lock in Settings/Security is disabled before flashing and remove fingerprints before backups or restore to avoid issues with those features. If you follow the forums, you can verify that it is possible to go back to Android 5.1 from Android 6.0 using Odin full tar.
I've been on MM since PD1 update. Currently on PE1 Odexed with Xposed framework.
Edit: didn't realize you were the OP. Sorry. I'd just recommend the factory reset but first disable reactivation lock and delete fingerprints and make a backup. If you have the Lollipop TWRP backup to restore, the OK1 bootloader is in the development forum for Sprint Note 4 in a thread by freeza: baseband and bootloader thread.
Sent from my SM-N910P using Tapatalk

samep said:
Not sure of your question but in context, what I did was flash the OK1 bootloader, factory reset and restore Lollipop TWRP backup. I suggested to the user I quoted that his boot loop was caused by app optimization of MM. He could confirm that by factory resetting and attempt to boot. I didn't get a confirmation.
The advice I would give is to first backup and then make a clean break with Marshmallow data if intent is to temporarily go back to Lollipop. The bootloader method is ideal for users with Lollipop backup to restore but for those without the Lollipop backup, I think the full tar is best.
But remember to make sure reactivation lock in Settings/Security is disabled before flashing and remove fingerprints before backups or restore to avoid issues with those features. If you follow the forums, you can verify that it is possible to go back to Android 5.1 from Android 6.0 using Odin full tar.
I've been on MM since PD1 update. Currently on PE1 Odexed with Xposed framework.
Edit: didn't realize you were the OP. Sorry. I'd just recommend the factory reset but first disable reactivation lock and delete fingerprints and make a backup. If you have the Lollipop TWRP backup to restore, the OK1 bootloader is in the development forum for Sprint Note 4 in a thread by freeza: baseband and bootloader thread.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I don't have any finger print and I am not sure what reactivation lock it. But I am fully stock PE1 at the moment. I would go back to lollipop for good. MM doesn't have anything that lollipop does for me at least.

Ind3lible said:
I don't have any finger print and I am not sure what reactivation lock it. But I am fully stock PE1 at the moment. I would go back to lollipop for good. MM doesn't have anything that lollipop does for me at least.
Click to expand...
Click to collapse
Reactivation Lock is in Settings/Security. Uncheck it before flashing.
No TWRP backup? Then I would suggest backing up what you want to keep, factory reset in TWRP and wipe internal memory and power down.
Odin OK1 stock tar in Odin and disable automatic updates in Settings/System update. Install TWRP, follow OP; make sure auto update remains disabled. If you don't disable auto updates stock enough, the update becomes persistent; you'll have to Google how to stop the persistent update notice if that happens.
One additional step I recommend after flashing custom ROM is to search your root folder for itson; delete what your search results. You may find a leftover folder at /carrier/ItsOn and a dalvik-cache belonging to an application in that folder in /data/dalvik-cache; that can cause a lot if persistent reboot demands after a factory reset despite the ROM not having ItsOn- this is a trace residue left in internal memory that gets added when you flash the stock tar in Odin. Enjoy Lollipop.
Personally, I think you'll want to come back to Marshmallow despite not seeing anything you want right now. You could make that TWRP backup and save TWRP folder to PC, just in case. To come back, all you would need to do is update the bootloader and baseband, factory reset and restore the backup.
Marshmallow is stricter but still manageable. Just takes some getting accustomed to. Once the tools and methods are achieved with proven compatibility, there may soon be custom ported ROMs for Note 4 on Marshmallow. At the moment it's thought to be a matter of when, not if. Time will tell if that thought is true.
Sent from my SM-N910P using Tapatalk