[Galaxy S 5 Q&A, Help & Troubleshooting] BruceElliott:
Hey VV,

Sorry that you had to go through all of this. I can empathize as I am going though it now myself due to similar mistakes. Unfortunately, I am only now learning the solutions and so I could not have helped you sooner. I do have a few suggestions for you for the future, though:

(1) Yes, you could have recovered ALL of your data by flashing TWRP via Odin after your system crash and backing up from the TWRP environment.

(2) Also, you could likely have changed the disabled file permissions back to "execute" using the CHMOD button in TWRP ---->"Advanced" ------>"File Manager". Alternatively, one might use the appropriate Linux bash syntax using the "Terminal" in TWRP, assuming the limited bash in TWRP supports the "PM" commands. I just posted in the "S5 General Development" TWRP thread (https://xdaforums.com/showthread.php?t=2727406&page=117) for help in sorting this out.

(3) I found disabling bloatware, junk systems files, and even spyware systems files to be extremely helpful to battery life and to limiting the constant flow of personal information outward from my phone. So I will continue to do that, but with a bit greater care from now on. Also, using ADB is REALLY a rough way to go. The GUI interface in BK Disabler is definitely your friend in this regard.

(4) That said, many of the lists of "safe to disable" apps and services floating around out there are just plain crazy. I would trust none of them. I can tell just from the names of the four that you mentioned in your previous post, for example, that all of those are critical system files. But then I am an engineer and not everyone is technical. Also, the file names do not always so easily give away the file functions. If you are not absolutely sure about any particular system file, don't disable it. By all means, DO NOT trust the lists! BK Disabler will automatically select the bloatware apps and you can just disable the entire group of bloatware apps and then uncheck any bloatware apps that you need to use. That will do 75% of the trick; just skip the other 25% (any improvement from disabling system apps) if you are not absolutely sure about what you are doing.

But even with 40 years of technical training, I made the same mistake as you did; so don't feel too bad. I can tell you this: (a) I will never be without TWRP recovery; and (b) I will create regular nandroid image backups using TWRP to my external sd card (as in every few days) and transfer them from the sd card to my PC RAID array. Doing that, if at any point you lock down things too tightly by disabling some system app, resulting in no system boot, you just boot to TWRP recovery and use the TWRP recovery function to get your entire system back from your last backup. If you have no PC, you'll just need an extra sd card to keep in a safe place. Also keep an important caveat in mind: TWRP does not back up either your internal or external sd cards. That is not really a problem with a simple system crash, because TWRP lets you access both sd cards via USB for transfer to your PC. But of course it would be a problem if you lost your phone.

So, a FULL back up requires check-marking all listed partitions in TWRP and creating the resulting nandroid image file, PLUS copying all of your personal data from both sd cards as displayed on Windows Explorer when you plug in the USB cable. If you need to restore because your phone does not boot into Android, you boot into TWRP recovery and press the recovery button. That reinstalls the complete OS (even more of the OS than a factory reset, but with everything already configured, just as your system existed when you did the TWRP backup. Then you copy the sd card files and folders to each respective sd card.

Good luck,

Bruce