[Sprint Galaxy S 5 Android Development] TheWebMachine:
Since the OP file is a Full Restore, an upgrade-friendly flashable is not yet widely available, and I'm partial to my current setup, I will be attempting to follow the following guide to flash my device with root included and knox removed:

http://xdaforums.com/showpost.php?p=57114587&postcount=157

I will then wipe the data partition and restore the TWRP backup of my data partition I will make before I begin. The big question is, what are the chances that the 5.0 system will behave as if it had just been presented a legitimate upgrade candidate and setup correctly with my 4.4.4 (just updated to the NK4 release about a week ago) data?

I welcome your thoughts, especially if you have tried this already! I will likely give it a go in the next few hours, unless someone strongly advises against it for some reason.

Cheers to those who have made the L leak possible. I'm sure the powers that be aren't thrilled, but they know they will ultimately benefit from it in the end. They read these forums, too. They will use our experiences to update the final product, ideally. They really should just embrace this process. :)

---Update 1---

My attempt to "upgrade" using the method posted above worked, despite being a bit of a headache. Here's what I have observed:

It took over half a dozen reboots (waiting about 10 min between each) to get the device and all apps to settle out. Different apps pitched fits about this process...but nothing major (spare the other notes below).

Root access is VERY slow and not available until about 2 minutes after boot, which leaves boot time apps without root access. It also can take up to 2 minutes before the SuperSU prompt for access to root appears for a new app, resulting in root apps needing closed and relaunched after they time out attempting to get root. Is this the case on "non-upgrade" installs? It has proven to be annoying with several of my root apps not gaining root under normal circumstance. I'm going to try CF-AutoRoot for 5.0 shortly to see if that makes SuperSU work more reliably.

Handcent SMS does not work, despite saying it is Android L ready. I've had to revert to the stock SMS app for now.

As reported by others, Chrome Beta simply closes on open but regular Chrome works fine.

---Update 2---

I have attempted CF-AutoRoot. It appears to have done the trick. I have root at boot and no more root delays. I wonder if those who have tried CF-AutoRoot solo would benefit from flashing the SuperSU from post #157 in recovery, then flashing the CF-AR in Odin to fully achieve root support.

That said, I also have issues with my NeoRouter VPN. The app connects and I can see the clients, but I can pass no packets to them. While I'm assuming this is the NeoRouter app itself that needs updated, I can't test a traditional VPN because I don't have a VPN server set up to connect to. Can someone check traditional VPN support and report here? NeoRouter is rather important to me, so I will likely contact NeoRouter support about 5.0 support, as well. Would be good to know where the break down is occurring.

---Update 3---

I had to flash CF-AutoRoot a second time, as su literally vanished 15 min after rebooting. The second flash seems to have stuck, as su has survived several reboots now.