[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
That's not good but I'm still not sure if you can flash that KitKat stock tar or not.

If you've had updates greater than Android 5.0 on that phone, I'd suggest not trying to flash that anymore. If that applies, try the latest stock tar.

The eMMC write error could be component failure but I'm thinking it could also be refusing to downgrade the bootloader to a less secure one which would apply if the phone is currently on a higher bootloader. Could you get the bootloader version by running this app?

https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo

You can use Galaxy Tools if you have that. Of course that requires the phone to be booted. If you can post, a screenshot.

Something to consider: it's risky so do only after determining the proper stock tar fails even using Odin default settings. So If you continue to have the eMMC write error, the PIT can be found on Sammobile in the Note 4 PIT thread (posted at bottom of this post). In order to determine if flashing error or component failure, power down, pull battery for a minute or more, and first try the suggested tar with Odin defaults. If it fails with eMMC write error again, you can try to flash with repartition and PIT with "nand erase all" and stock tar loaded, all at same time. Important: Always have the right PIT loaded with repartition option checked. Don't forget the battery pull prior to download mode.

If the last step fails, you most likely have the a component failure. If it's just a boot issue, nand erase all sometimes causes that: try factory reset in stock recovery, pull battery and flash the tar again with Odin defaults.

Before beginning, first determine which stock tar to flash. I'd recommend latest if your bootloader is Android 5.1 or higher. The Sprint version started getting the updated bootloader before Android 5.1, so only the initial Lollipop release had the less secure bootloader.

Find PIT here:

http://www.sammobile.com/forum/showthread.php?p=137840

You can find recommended safe versions of Odin here:

http://xdaforums.com/showpost.php?p=51767811&postcount=1

---------- Post added at 11:10 AM ---------- Previous post was at 10:46 AM ----------

Maybe my reply above helps you?

IMO, the Note 4 does a lot of eMMC failures. Not scientific or statistical data comparisons but I'm seeing recommendations to get TEP (insurance) in close circles on my Sprint version, especially if sluggishness starts or trying to hold out until 2017 phones are available for upgrade.

Having the phone boot to download mode is an indicator of eMMC hardware failure. Some time ago, Samsung had an ongoing to-do list that included flash errors on Odin and OTA. I have a theory that it may discovered by updating phone but may just be hardware failure.

The suggested flash with PIT and repartition and nand erase all with stock tar loaded in AP slot is only a troubleshooting step to eliminate the possibility of a bad flash or update causing the initial error. It's been proven redundant many times and some feel attempting more flashes only worsens the severity. But it is ultimately severe failure at some point so use with appropriate caution. The many eMMC failures makes me weary of updates. Time to consider TEP; $0 deductible for hardware failure without losing an upgrade on line, if available.

Main board replacement or eMMC replacement is another alternative. The local uBreakItiFixIt quoted me $10 labor to replace main board with one that I'd have to obtain myself. I've seen certified used ones on eBay and Amazon.

Hopefully mine lasts. I plan to keep it but planning to upgrade my line in 2017.