[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] dreamwave:
I do apologize for trying a method that I saw absolutely no documentation on any attempts of, it was a fool of me to try and see if it might just work. You said that JTAG would not work, you gave no links and no reasons why. I understand that there might be a kill flag in there, but if the phone believes itself to be running genuine software I don't see much in the way of proof that it wouldn't accept any firmware rewrite then, especially as at that point Samsung and Verizon would stand to benefit from being able to directly write such firmware. The petition was simply to get even just a couple more eyes on the issue, and with the FCC...IT ACTUALLY IS A LEGAL CASE. I have tried to say that, that they are given ,by forfeit of direct control of the issues by Congress and the courts, a requirement that they use internal systems that are run as courts and have the power of a court, while being only possible to challenge if they act "unconstitutionally" outside their given bounds. The petition was a thing I started basically to try and let people outside of the developer community, who are demographically very likely to be vocal on issues of corporate monopoly (based on the crowd change(dot)org attracts.

I tried doing my research for each, and in basic principle found none that matched either. No, I'm not a longstanding member of the XDA community, and no I'm not an ex-oem firmware dev, but if I have an idea and no one gives me a specific reason why it won't work in a manner that would both completely address all facets of it and in a way that would help others to try and build off of the information contained within, then I will try and implement that idea or publicize it so someone who knows how can do it. Notice, on my thread about the SD Card unlock: I completely summarized the content of my findings in the first post, dead ends I ran into, and what I personally think might work in the future. If someone adds to the thread with info that either adds or nullifies an idea then I will update it and tag the post as I care about knowledge on a whole and getting info to everyone who can use it. My rationale behind this is to allow for anyone who might have an idea, or the capability to form a successful one, to research and take into account the findings of others.

TL;DR: It helps everyone, individually and as a community, to explain why an idea won't work than just to declare that it won't and the person's efforts (all of them) are in vain.

I do not mean to insult you or attack you in any way, and I have no "but" or "however" for this statement. Just for the future, instead of saying "no" and then flaming me when I say "why not," maybe say "why not" because if you know that the answer is "no," not that many issues are so black and white that a small bit of explanation or detail physically can't be given.

BTW, in response to one of your replies in a recent thread where you mentioned how a brick would not be possible to undo even by JTAG then talked about that being universal, what I was discussing was not bricking by means of triggering any lock such as that that you mention. I was attempting to reproduce conditions that would lead to a "failed flash of newer software" wherein no flag is tripped, but the phone could not load any usable kernel, modem, or bootloader image as that would allow for using the method here: http://xdaforums.com/verizon-galaxy-s5/help/g900v-hard-brick-t2914847 that I have really worked on for the s3 to try and boot custom software to flash software to the phone. I am actually still optimistic for one method here because no one has said that it would not boot a very carefully crafted debrick image that would act as an external bootstrap and directly load a completely custom system image quite readily with no qualifiers or signature checks.

And sorry to everyone for the long post, I know it's annoying. Please forgive me :fingers-crossed: