[Galaxy S III General (US Carriers)] TheDiabolicaL1:
TL;DR - Verizon blocks your ability to unencrypt the boot loader and upload another wireless carriers software for use on their network which is explicitly written into the law. While Verizon stated the encrypted boot loader helps keep customer support high and FCC deemed it reasonable, Verizon will have a hard time explaining the reasonableness of it's encryption when you've decided you would like to take your device to another network. This "locking" of the device to Verizons network only is the noose we're going to tie around Verizons neck.

The concept:

Say you've decided you may be interested in taking your 4g device to another network. Unfortunately, the bootloader is encrypted and any flash of another providers software renders the device "bricked."

The law, as it is written (Feel free to skip to the next section):

§ 27.16 Network access requirements for Block C in the 746–757 and 776–787 MHz bands.

​

(a) Applicability. This section shall apply only to the authorizations for Block C in the 746–757 and 776–787 MHz bands assigned and only if the results of the first auction in which licenses for such authorizations are offered satisfied the applicable reserve price.​

(b) Use of devices and applications. Licensees offering service on spectrum subject to this section shall not deny,	limit, or restrict the ability of their customers to use the devices and applications of their choice on the licensee’s C Block network, except:​

(1) Insofar as such use would not be compliant with published technical standards reasonably necessary for the management or protection of the licensee’s network, or​

(2) As required to comply with statute or applicable government regulation.​

(c) Technical standards. For purposes of paragraph (b)(1) of this section:​

(1) Standards shall include technical requirements reasonably necessary for third parties to access a licensee’s network via devices or applications without causing objectionable interference to other spectrum users or jeopardizing network security. The potential for excessive bandwidth demand alone shall not constitute grounds for denying, limiting or restricting access to the network.​

(2) To the extent a licensee relies on standards established by an independent standards-setting body which is open to participation by representatives of service providers, equipment VerDate Mar<15>2010 16:46 Dec 15, 2010 Jkt 220201 PO 00000 Frm 00334 Fmt 8010 Sfmt 8010 Q:\47\47V2 ofr150 PsN: PC150325 Federal Communications Commission § 27.20 manufacturers, application developers, consumer organizations, and other interested parties, the standards will carry a presumption of reasonableness.​

(3) A licensee shall publish its technical standards, which shall be nonproprietary, no later than the time at which it makes such standards available to any preferred vendors, so that the standards are readily available to customers, equipment manufacturers, application developers, and other parties interested in using or developing products for use on a licensee’s networks.​

(d) Access requests.​

(1) Licensees shall establish and publish clear and reasonable procedures for parties to seek approval to use devices or applications on the licensees’ networks. A licensee must also provide to potential customers notice of the customers’ rights to request the attachment of a device or application to the licensee’s network, and notice of the licensee’s process for customers to make such requests, including the relevant network criteria.​

(2) If a licensee determines that a request for access would violate its technical standards or regulatory	requirements, the licensee shall expeditiously provide a written response to the requester specifying the basis for denying access and providing an opportunity for the requester to modify its request to satisfy the licensee’s concerns.​

(e) Handset locking prohibited. No licensee may disable features on handsets it provides to customers, to the extent such features are compliant with the licensee’s standards pursuant to paragraph (b) of this section, nor configure handsets it provides to prohibit use of such handsets on other providers’ networks.​

(f) Burden of proof. Once a complainant sets forth a prima facie case that the C Block licensee has refused to attach a device or application in violation of the requirements adopted in this section, the licensee shall have the burden of proof to demonstrate that it has adopted reasonable network standards and reasonably applied those standards in the complainant’s case. Where the licensee bases its network restrictions on industry-wide consensus standards, such	restrictions would be presumed reasonable.​

How to play it:

Call Verizon Tech Support. Ask for the encryption and verification software used to verify the Operating System is approved "by Verizon" so you could potentially take your device to another network. You may be told, as I was by a Tech Support Supervisor, that it's as simple as having your new carrier flash their software onto the phone and it's good to go. Of course, we know this bricks the device. When you are told no, you could then ask to be transferred to someone who can remove this software, or, you could end it there, your job is done.

Once you're told "No." you have a legitimate complaint to file with the FCC. The law states specifically "No licensee may disable features on handsets it provides to customers, to the	extent such features are compliant with the licensee’s standards pursuant to paragraph (b) of this section, nor configure handsets it provides to prohibit use of such handsets on other providers’ networks. The last part, in bold, is the noose you've just tied around Verizon's neck.

This will only work *if* you are told "No" by a Verizon Representative. As every call is logged by Verizon, you cannot lie about having been told no as their logged call may be used against them. You may ask them to note this in your account as well.

What to tell FCC:

You're allowed 1000 characters when you fill out the FCC complaint form. Lets do it with 690 characters:

How to tell the FCC:

https://esupport.fcc.gov/ccmsforms/form2000.action?form_type=2000F

With enough pressure, provided the FCC will enforce their own codes, we can effectively unlock *all* devices with 4g capability. Samsung, Motorola, Etc,.

(Mods, please feel free, as you see fit, to merge my other thread that is far less refined and was used as a brain storming session for the creation of this one. Thank you)