[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Zoandroid:
Good advice up to here, but you might want to hold off on using Exposed. As I understand it, Exposed lets you tinker with the existing stock ROM. I don't think I would want to do that, and I have rooted and ROM flashed several Android devices over the years. But its up to you. :)

With your being new to rooting, I'll offer this advice:

Titanium Backup (a.k.a. "TIBU") is a good way to back up all your apps. Here are some suggestions in using it:

--Buy the PRO version. It has more features, is not very expensive, and helps support a really cool app that is very handy. :)

--Set the Preferences/Backup folder to your REAL external SD Card. It will default to internal storage (also called "sd card"....don't get me started lol) which is IMO totally useless. If you lose internal storage due to corruption or whatever, you would lose all your backups. Having them on the REAL SD card you can also archive them to your PC.

--Set your Max Backup History to some number larger than the default "1". I use 7. Why? Well, have you ever seen the developer of one of your favorite apps suddenly screw it completely up in some update? Or, worse yet, sell out to some other vendor who now made it a PAY SUBSCRIPTION app?? I have. By keeping multiple backups you can roll back in time to previous versions that you know WORKED when those things happen. I have several apps I will never update, especially on the Store, for various reasons. (TIBU used to be able to disconnect the link to the Store so apps didn't try to update, but Google broke their ability to do that).

--When you do make TIBU backups, select "app and system data" which is IMO incorrectly worded and causes confusion. It should read "app and APP data". Because that is what it really does. Backs up the data IN your system that is associated ONLY with the APP. NOT any "system files". When you restore a backup, restore "app and system data" and you not only get the app installed, you get all your data it created, as well as all your customized settings restored! :) It is a real time saver. And you can "usually" even do this with a new device, using the TIBU backup folder on an SD card you had in some previous Android device. I've done it many times.

Safestrap installs a custom version of TWRP recovery. From that you can make the aforementioned "nandroid" backups of your complete system. (You won't see the word "nandroid" in TWRP while you are doing this. It just calls them backups). Couple of caveats with TWRP (and the Safestrap version):

--The date/time stamp used in both TWRP and its alternative, Clockworkmod Recovery (CW) will always be wrong. I've read (in short) there is no way for them to fix it. BUT........you most certainly CAN edit the backup file name to be whatever you like while setting it up to make the backup. So I recommend deleting the portion of the name that is the screwed up date it will generate, and putting in a date you can read, like my preferred format of 2014-07-10-1727 which is today at 5:27 PM, or whatever format you like.

--By default, TWRP recovery uses (in the Advanced settings) an inane "power saving" feature of the display, which will maddeningly keep turning it off and making you think the phone died while it is in the middle of making your backup. A - ALWAYS keep your phone on the charger when working in Recovery!! Don't even start unless it has at least 40% charge. B- Turn OFF the inane "power saving feature" and get some peace of mind. The screen will stay lit forever, until you reboot system when you are done. :)

--By default, TWRP will be set to use INTERNAL STORAGE as the place to keep your nandroids. Again, I consider that a very bad idea. Use a REAL External SD card and keep them there. And make regular backups to your PC of the SD card. I've seen a great many SD cards suddenly fail without warning. Your device will pop up and tell you the SD card is corrupt, and you need to format it. Usually, there is no way to recover the lost data on the card when that happens.

--On my Galaxy S5, making a nandroid of the stock OS via Safestrap took up over 4GB! That is almost 4 x what I normally see making a nandroid of a custom ROM on some previous device. So make sure you have plenty of room on whatever SD card you choose to use.

:)