[Verizon Samsung Galaxy S III] Thalinor:
We dealt with this on the Droid X and were forced to use Roms based off of Moto code; it sucked. We dealt with this on the DX2 and it took forever to get a port of CM7, even then it was not ideal and the device was twitchy.

If there is no way around it on this phone, I will be returning it and leaving Verizon. If I get cake I want to eat it; I don't want to sit back and watch all the other kids on the playground having fun while I get stuck inside locked in a cage.

Pseudo is not good enough. I told myself long ago I was done with encrypted devices and would never buy one again. I am sticking to what I said. I do however think there will be enough pressure on Verizon to get this fixed. I know its a long shot but I think we can get them to budge.

Here is the thing, for those of you who have been around long enough to remember the Motorola V710 and its locked down BT profiles, you will remember how that worked out in our favor. It took months of legal battles but in the end the courts forced Verizon to offer its customers the following options:

http://www.verizonwireless.com/b2c/footer/legalNotices/v710.jsp

In the end they had to refund customers the full price of the phone, including accessories, and then offer people the option to buy any replacement they wanted (w/o changing the persons contract), let the person change carriers w/o an ETF, or receive a credit on your cell phone bill.

If the same thing happens for this phone it will take months for a settlement. By then there will be quad core LTE devices. A free swap for one of these upgraded devices w/o loosing unlimited would be very nice. If there are enough waves we may be able to topple Verizons ship; its happened before and can happen again.

People need to call Verizon corporate and complain.

Verizon Corporate Office Headquarters:

140 West Street

New York, NY 10007

Corporate Phone Number: 1-212-395-1000

Corporate Fax Number: 1-212-571-1897

Unfortunately they have gotten wise to my "dial by name" voicemail trick contacting executives via VM after hours by entering their name into the VM system and being directed to the users VM to leave a message. It seems they have changed it so you can't use "dial by name" from an outside line and now just have a generic VM box for after hours calls. Still calling them during working hours or leaving the main box a VM message will defiantly help.

If we don't let them know we are not happy, we don't have a chance to fix the problem. If you have not had to deal with this on the DX/X2 (or another encrypted device) then you don't know how bad it really is trying to customize your device with this kind of lockdown. Seriously, not knocking the amazing work of devs here but its like putting a bandaid on a gunshot wound. A lot of devs know this which is why a few are posting things like "device is going back" instead of "lets do this!"

Think of it this way, if you get your legs blown off they can give you prosthetic legs to get you walking again, but its never going to be like when you had your real legs. Pseudo is not a substitute its a gimped workaround.

The only thing we have going for us is Verizons device is the only one that has this done to it; I don't think it can be hardware related like efuse and the rest of the crap Moto did to their phones. I could be wrong. I know this is not the correct terminology but I see this lockdown as more of a software firewall vs a hardware one; then again I could be completely wrong in the analogy. This is the first Samsung phone I have owned so I am ignorant on the subject other then what I have read over the past week.