Develop Bugs

Stock Recovery and Cache for enabling OTA after CF Auto Root

These files will restore stock recovery and cache for those who have rooted with CF Auto Root, so that you can return those partitions to factory status for an OTA. Remember that any changes to /system in Lollipop nullifies OTA capability so you also need to undo any changes you've made, restore any bloat, unroot from within SuperSU, etc. For those who used CF and have done minimal mods or changes, this is merely a faster (both in terms of download time and flash time) way of restoring recovery and cache (which are modified when you flash CF Auto Root) than flashing the full stock tar. If you've deleted a whole bunch of bloat, installed Xposed, flashed mods in recovery, etc. then you probably just wanna use the full tar
Flash via Odin PDA/AP slot.
OC9:
OCF:
https://www.androidfilehost.com/?fid=24052804347756900
OE2:
https://www.androidfilehost.com/?fid=24052804347756938

Sweeet!!! DO you know of anywhere else to get the full stock TARs (particularly OE2)?? Or do you know anywhere to get full data wipe TARs? Thanks!

JoeFCaputo113 said:
Sweeet!!! DO you know of anywhere else to get the full stock TARs (particularly OE2)?? Or do you know anywhere to get full data wipe TARs? Thanks!
Click to expand...
Click to collapse
Well where do you think I pulled the recovery and cache from haha? I'll have an AFH mirror up later today

iBowToAndroid said:
Well where do you think I pulled the recovery and cache from haha? I'll have an AFH mirror up later today
Click to expand...
Click to collapse
AHHHH!! You are a God! Thanks so much :good:

I flashed the stock rom downloaded directly from Sammobile and it still didn't allow OTA. It said that my phone had been modified... Not sure if I missed something because it stuck in a bootloop with the stock ROM after TWRP unless I flash Unikernel. Maybe the newest 5.1.1 doesn't allow OTA. I tried it with the OFE ROM completely stock.

Johnrob011045 said:
I flashed the stock rom downloaded directly from Sammobile and it still didn't allow OTA. It said that my phone had been modified... Not sure if I missed something because it stuck in a bootloop with the stock ROM after TWRP unless I flash Unikernel. Maybe the newest 5.1.1 doesn't allow OTA. I tried it with the OFE ROM completely stock.
Click to expand...
Click to collapse
If you install a non-stock recovery (like TWRP) you cannot take OTA updates. Any version, doesn't matter.
Follow the guide posted at http://forum.xda-developers.com/sprint-galaxy-s6/general/how-to-to-100-stock-root-t3075448 and you will have the latest version with custom recovery and root.
Or, if OTA updates are crucial to you, Odin the TAR file and stop there.

Mine wasn't working after I flashed the stock rom from Sammobile before I flashed twrp, since it wouldn't update I figured I needed twrp to stay up to date from now on but I'm not trying to post bad information to anyone, it wasn't working for me but maybe these caches can bring back OTA. I wish there was a way to get Samsung pay working.

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

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

So I was rooted and had a custom recovery...

I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?

Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk

samep said:
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
So, now I am on PJ1 and I don't know how to put TWRP on my phone, I want to put tx_dbs_tx's UN7 hybrid on my phone and I am having issues both finding and putting TWRP on my phone... and I can't find a download or anything for it...
I've downloaded 2 different versions of twrp and used odin to put them on but I think I am doing something wrong because it isn't booting into twrp

Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working

Curtai said:
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working
Click to expand...
Click to collapse
Oh your talking about installing twrp? Yeah you have to not let it reboot. And when is done pull battery and boot into recovery to get it to stick. Obviously you figured it out. But just saying. I think earlier versions you didn't need to do that but now you do.
Glad you got it going. How you like the Rom? Running smooth for me.

ROM is good
Well I obviously got it going and didn't read the first couple posts after the install and didn't notice the SMS issue so I had that problem and I can't find a lot of the menu options that I had with the OB7 original I've been running for about 18 months... It's pretty smooth now and I'm wondering how fast it will fill up my internal memory I like that it's almost 20 gigs free.. for a while I was running on less than 6 I need to find an efficient way to use my external SD card... Other than that the options are neat but it seems really bloated all the extra Google apps make me sick even though I never use them... I've got titanium backup and am freezing them and will probably uninstall them soon... I want a small ROM that I can customize myself or apps that are easily removed or whatever half the apps I don't want are in ROM which is a pain to remove or I just don't know how to unless I use TB
Wow that's a novel sorry but yeah that's my ramblings for the next week I guess... Now I'm gonna hit the rack...

Upgrade Help Please

I am rooted from chainfire, with twrp, on this n910pvpu1ank2 version kitkat 4.4.4
I want to update to the latest, if possible, and retain root. if that's not possible, then I think just update it. all help appreciated.
what steps do I need to take to accomplish this? do I need to odin back to stock and then update? I haven't been able to find the kitkat stock firmware for n910pvpu1ank2.
do you have links to trusted files for the update? I found the most recent update on sammobile here and downloading now. is this the correct file and can I odin this one directly or do I need to go through all the updates first?
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910P/SPR/download/N910PVPS4DQG1/184468/
thank you.

toenail_flicker said:
I am rooted from chainfire, with twrp, on this n910pvpu1ank2 version kitkat 4.4.4
I want to update to the latest, if possible, and retain root. if that's not possible, then I think just update it. all help appreciated.
what steps do I need to take to accomplish this? do I need to odin back to stock and then update? I haven't been able to find the kitkat stock firmware for n910pvpu1ank2.
do you have links to trusted files for the update? I found the most recent update on sammobile here and downloading now. is this the correct file and can I odin this one directly or do I need to go through all the updates first?
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910P/SPR/download/N910PVPS4DQG1/184468/
thank you.
Click to expand...
Click to collapse
You lose root updating.
Fyi: recent updates do not have developer support but maybe latest security update is your goal?
If you're not interested in rooting again and flashing custom ROM and prefer latest stock ROM, I'd recommend:
decrypt any data encrypted
backup any keepsakes to ext SD Card
remove fingerprints
make a TWRP backup (backups should be on external SD Card)
factory reset
wipe internal memory
Power down and remove battery prior to download mode
Flash latest stock tar with Odin from this thread (it may download faster- QB3 would be OK unless you want to download latest, if available. Updates usually aren't available for some time). Use Odin defaults and go through setup wizard.
https://forum.xda-developers.com/showthread.php?p=63868221
Quickest way to latest update is to install Smart Switch (unless you found latest to download for Odin).
https://www.sammobile.com/samsung-smart-switch/
Note: If you do decide to run a custom ROM, security updates are not up to date but it's recommended to install the update recommended in OP for those custom ROMs. You may lose some compatibility by not flashing the recommended update.
Stock tar updates for Odin are full updates so they're not required to be flashed in sequential order. Same for Smart Switch updates. Smart Switch likely only works for non rooted phones which is why I recommended to start with Odin stock tar.
OTA updates patch the previous update sequentially. So OTA update would only be ideal to update after getting to latest with Smart Switch. Odin updates are slower to become available as I recall.
Make your battery is charged to 80% or more. I wouldn't recommend a battery that's over a year old. Start with a fresher battery and replace batteries that have over 500 recharge cycles on them. This could save you trouble in the long run.
Also, keep your phone cool during these initial boots after flash. Forced air from a small fan or air purifier should do fine.
Sent from my SM-N920P using Tapatalk

"Fyi: recent updates do not have developer support but maybe latest security update is your goal?"
this mostly. though I will read through your response carefully. I like kitkat and everything is the way I like it, but I feel as if I should also update the firmware. rather torn honestly. all thoughts and advice on the trade-offs, etc. and I don't play with roms.
thank you for your help. was hoping you'd pop by. you were so much help before.

wow. so much valuable information in your reply. this is amazing. thank you.

toenail_flicker said:
"Fyi: recent updates do not have developer support but maybe latest security update is your goal?"
this mostly. though I will read through your response carefully. I like kitkat and everything is the way I like it, but I feel as if I should also update the firmware. rather torn honestly. all thoughts and advice on the trade-offs, etc. and I don't play with roms.
thank you for your help. was hoping you'd pop by. you were so much help before.
Click to expand...
Click to collapse
You do recall that once you upgrade past OB7 that you lose the ability to return to KitKat via Odin stock tar?
The TWRP backup I recommended is still useful but likely you'd need to downgrade bootloader firmware to 5.1 (OG5 to OK1 is recommended once you've upgraded beyond OB7), factory reset, wipe internal, restore backup and flash Beastmode 1.0 kernel prior to booting.
I think you also need to flash SuperSU zip after kernel to get a boot but I'm not sure on that.
Have you already been through this with lollipop 5.1 and went back to KitKat? If so, you know the drill, just make sure you have the right bootloader.
If you're looking for developer support on stock like ROM, check out dtux or UN7 ROMs with aroma flash modset mods. There's also a few modified stock ROMs that are newer.
I discovered this morning that older updates for Note 4 are vulnerable to BlueBorne exploit through Bluetooth. I keep mine off mostly and disable the options in improve location and nearby devices so it shouldn't be a issue for me. There's a BlueBorne vulnerability scanner in Google Play to check later updates if you like. Search for it in Play.
Sent from my SM-N920P using Tapatalk