Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
Thalinor
Old
(Last edited by Thalinor; 6th September 2012 at 05:47 AM.)
#1  
Thalinor's Avatar
Senior Member - OP
Thanks Meter 101
Posts: 110
Join Date: Sep 2010
Location: Connecticut
Default Verizon / Samsung Corporate Contact Log

Updated 09/6/12 http://forum.xda-developers.com/show...2&postcount=81


This is a combined log of my attempt to get answers from Verizon and Samsung regarding the encrypted bootloader. I currently have a ticket with level III tech support at Samsung. It took a huge dog and pony show to get this far and I have had several forum members contact me asking to pass along info and ask questions when I finally get a hold of the right people.

I posted most of this in another thread, but it not where it should have been so I am moving it for a mod so we can keep that other development thread clean. Its 8am EST and Samsung Level III should be open in three hours as they are not staffed 24/7 like Level II/I.


For the record Samsungs Tech Support phone number is 800-726-7864


Just remember the rep you talk to regardless of what their position in the company is had no say in the encrypting of the bootloader. Its not their fault Verizon screwed us, please keep that in mind if you call. Using 5c technical words will get you past Level I but level II seemed to be on point. It took some manipulative games to get the guy to admit there was even a level III department; at first he told me level II was the highest I could go in tech support. Will update with more info when I have something.

I am also considering contacting the firm that handled the Motorola V710 lawsuit against Verizon years ago. We won that one and anyone who wanted got to trade in their phone and accessories for a full refund, no ETF, and if they wanted could also get a new device w/o extending their contract. I hate lawyers and would rather cut off my pinky finger then deal with them but it may be the only option in the end. Its like Verizon delivered us cake, then shot our dog and walked away. So mentally exhausted dealing with this crap.

Lastly, I was able to get a hold of Verizon corporate and had a low level executive call me back. This was before the device was released and we knew the bootloader was encrypted. She told me to save her number, and I am glad I did because once we found out about the lockdown I called her back and left VM. Should hear back from her Monday.

Verizon's Corporate Contact Info.

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


Original Post:

Ok, just an update. Level III Samsung tech support is not 24/7 like Level II/I. I have a ticket in the system regarding the issue and its been forwarded to Level III.

They will be in tomorrow (Saturday) from 8am (PST) to 7pm (PST) and I have to call back to get a hold of someone in the Level III department. I will keep dragging this up the chain of command till I can get some answers. Level II once again confirmed what we already know, Verizon did mess with the phone. Level II said don't bother with Fastboot because were not getting in that way. I don't know if he was lying but he seemed to know exactly what I was talking about when I mentioned the odin/fastboot switch.

One more thing to note, I am not sure I believe him but he said that they sent the phones to Verizon, and its Verizon that did the messing around not Samsung. I find it hard to believe Verizon was able to do this without Samsung support.

I don't have high hopes of getting anything that will be able to help us out of Level III but I will try. They have also lodged a my customer complaint and supposedly I am going to be getting a call back from someone from their corporate office in consumer relations.

I wish I could help more on the technical side but my experience only takes me to the point where everyone else has gotten with fastboot. I am however quite the people person when it comes to making noise with corporations and will keep up the good fight with Verizon / Samsung Corporate.

If there is anything specific you want me to ask Level III send me a PM by tomorrow morning and I will address it with them when I call. I know enough that I should be able to at least hold a conversation with them on the subject but more ammo would be great. I would also be willing to conference call with a repeatable dev/mod when I call them so that you don't have to jump through the two hours of crap I just did to get this escalated.

Post 2: (A reply to a forum member asking for an update)

I asked them if there is a reason I can't get into fastboot and the guy said because Verizon has locked down the device. I asked him "how" and "why" but he was unable to provide me with an answer to both questions. He then referred me to Level III as he said they were the ones who could discuss how it was done. I asked him if there was a way around it through odin using .ops he went silent for a while and said he had no information to provide on the subject and just reiterated that Verizon has made changes to the device software and I would have to refer to them regarding those changes.

With regard to the "why" question he simply said that Samsung could not comment on carrier practices only that Verizon requested the lockdown and that the phones were sent to them first to have it applied. He made it sound like Samsung told them to go take a flying leap and Verizon went ahead and did it anyway. Again, were talking about a rep here so take it with a grain of salt.

I talked about the FCC's Block C agreement regarding carriers not locking devices but the rep said he did not have a comment on the subject as he was just tech support. Block C is probably the only legal course of action we have but despite the FCC saying they were going to enforce the rule, we all know how the FCC could give a crap.

I am going to flat out ask Level III to do the right thing and leak a file for us to fix the issue. I may be nuts but I am not delusional and have no real expectoration they will help. I am however going to do my best to get them to slip something that may help a dev find a solution. If I can get at least a small puzzle piece out of Level III it might be the crack in the dam we need to blow open the floodgates.





07/11/12 Samsung Level III blew me off yesterday as well saying they were still looking into the matter. I called again today and finally received an official reply. Samsung says they have no information exactly what Verizon has done to the phone, they do not know exactly what is and is not signed/encrypted, and they have no further information. I have submitted a complaint to the president of Samsung USA but thats as far as I could go with Samsung. They have closed my case and can not provide further information. I asked if they had an original system image before Verizon gimped the phone and they said "yes but we can not provide that to our customers per carrier agreement."

Lastly I was told that there is going to be a Verizon "Developer Edition" that you can buy directly from Samsung in the coming weeks. This is in "direct response to complaints filed by customers" according to Samsung and will be distributed and supported by Samsung directly. It will cost $600+ and basically be the same phone but w/o an signed/encrypted bootloader.

Off the record information from an unnamed outside source: Verizon is releasing a OTA update to patch the root exploit in the coming days. This OTA will break and prevent re-root as well as try and stop people from using the image off of the "Developer Edition" to mess with the "normal" Verizon Galaxy S3. I don't have specific details; sorry. Do not OTA unless you want to loose root and probably not get it back. Verizon is fk'ing pissed; I mean really pissed that we have root.

From what I am hearing, Verizon's "top %5 data abusers" are all typically rooted/romed. The whole point of locking this phone down was to mess with these unlimited data customers. Verizon started this war; let us end it and make them loath the day they decided to fk with the dev community.

Again, my case Support case has been closed with Samsung. We will get nothing further from them nor any direct help. My case with Verizon corporate is also closed; they said Samsung will offer a Developer model directly and if I wanted that kind of access I needed to talk to them not Verizon.

The lawyers still have not called me back. No shock.

Up until this point I have been angry; now I am pissed. This isn't over; not by a long shot.

Will update when I have more information.


07/17/12

Samsung "Office of the President" -

Phone 877-268-2121
eMail president@sta.samsung.com

FYI Samsung records phone conversations between the 4th minute and the 18th minute. Anything you say after minute 4 and before minute 18 "MAY" be recorded. I know that sounds like a strange window of recording, but its straight out of the mouth of a sympathetic to the cause tech support rep. Just had a great conversation with a guy, nothing is fixed of course but needless to say, there are people in Samsung that have been hearing rumors that the company is tired of carrier's crap and with in the next few years will be offering all Samsung headsets for a subsidized price, directly through Samsung. There will probably be trade-in specials, loyalty discounts, etc. I can't wait not to buy my devices directly through Verizon! Secondly, as of now (Verizon lies again) anything software related with this phone is coming from, programmed by, and completely influenced by Verizon. Samsung manufacturing does not touch the device or support updates after its in the hands of Verizon. The developer model is not Verizon approved, nor is Verizon happy its going to be sold [from what I am told] however per FCC open network regulations Verizon has to allow the device on the network. Updates for the developer model will be directly from Samsung.

I was able to get the Samsung Apps (store) sideloaded on my device BTW. Verizon requested it be removed which is why its not on the device pre-installed. S-Suggest is NOT the same thing as Samsung Apps. Will Write something up here on XDA later when I get a chance.

07/24/12

The Electronic Frontier Foundation called me back and said they need more info on Block C. I am out of town until next Monday and let them know I would get back to them in a few days. They also are finding a lawyer who will do it pro bono. Looks like this may actually make it to court.
The Following 25 Users Say Thank You to Thalinor For This Useful Post: [ Click to Expand ]
 
Thalinor
Old
(Last edited by Thalinor; 7th July 2012 at 02:33 PM.)
#2  
Thalinor's Avatar
Senior Member - OP
Thanks Meter 101
Posts: 110
Join Date: Sep 2010
Location: Connecticut
So we have root but we are still locked down unlike all other carriers. Basically this is going to turn into a Droid X situation and for those who know what I am talking about you know how bad this still sucks.

I am tired of this crap guys, and think with the amount of SG3 phones sold in the US and specifically Verizon, this is the time to strike back against all encrypted devices not just the GS3. We have dealt with this garbage long enough and now its time to end nonsense.

Kirtland and Packard, (310) 536-1000, 2361 Rosecrans Ave Ste 450, El Segundo, CA 90245

That's the law firm that won the huge case against Verizon over the Motorola v710 BT lockdown. I have left them a message asking if they will take this case too. In reality this one is going to vastly larger then the Moto case because of the number of users that have this device.

Please call them and let them know on the main VM that you too have been effected by this lockdown, or any lockdown in the US on any carrier. The more people who call the more likely they will take the case. Lots of people calling is how the guys over at Howard Forums were able to get the ball rolling on the v710, so let history repeat itself for the sake of every dev, phone enthusiast, and civil rights advocate.

ROM developers usually work off of donations and by encrypting this and other devices Verizon is stealing from these developers who's livelihood is phone software development. Software developers who want an open platform also have to deal with the hassle that Verizon and other carriers have put them through by locking down devices. If the personal computer was locked down like this when it was first created and sold to people we would never be where we were today technology wise. The crippling of our mobile devices needs to stop, and it needs to stop now.

Its time to take the fight to Verizon and hopefully end the lockdowns once and for all. If the lawfirm takes the case this is going to be winner takes all. This may be our best shot to end device lockdowns in the US once and for all.

I think the push we will make is going to be Block C. Normally Verizon could argue that they locked the device [against the FCC Block C mandate] because of network security. This is going to be hard for them to argue though when every other carrier in the US and internationally has not encrypted the device. It's a long shot, and its going to be up hill, but as far as I see it this is our best chance and the time to strike on this issue is now.

Samsung Level III opens in 30 min. Will update again soon.
The Following 2 Users Say Thank You to Thalinor For This Useful Post: [ Click to Expand ]
 
Thalinor
Old
#3  
Thalinor's Avatar
Senior Member - OP
Thanks Meter 101
Posts: 110
Join Date: Sep 2010
Location: Connecticut
Level III is not in on the weekends, so I was just told by the automated message I got when the guy transferred me to that department. ok... Not what they told me yesterday but ok.

So Monday at 8am PST it is, and that's also when Verizon corporate will be calling me back too as the past two calls they have made to me have been the ass crack of dawn. If I time it right I can conference the two in and let them try and point the finger at the other one, to each others faces. No more "That's what the manufacture wanted, go talk to them" vs "That's what the carrier wanted, talk to them" runaround bull****.

Anyway, no updates till Monday then. That gives me time to root.
The Following 9 Users Say Thank You to Thalinor For This Useful Post: [ Click to Expand ]
 
chill145
Old
#4  
Senior Member
Thanks Meter 35
Posts: 291
Join Date: Aug 2010
i'll be the first to say it but thank you


going above and beyond especially considering nobody asked you to do this. great work and i hope it leads to some results
 
dchurch85
Old
#5  
Junior Member
Thanks Meter 1
Posts: 21
Join Date: Jan 2009
Quote:
Originally Posted by chill145 View Post
i'll be the first to say it but thank you


going above and beyond especially considering nobody asked you to do this. great work and i hope it leads to some results
Yes thank you 100%, we are all in this together.
 
tekhna
Old
#6  
tekhna's Avatar
Senior Member
Thanks Meter 309
Posts: 1,154
Join Date: Dec 2007
Also please file FCC Consumer Complaints against Verizon for potentially violating the openness requirements of the Block C spectrum purchasing agreement.

https://esupport.fcc.gov/ccmsforms/f...orm_type=2000F
http://www.xda-developers.com/androi...e-bootloaders/

It's a long shot, but maybe worth it.
The Following 2 Users Say Thank You to tekhna For This Useful Post: [ Click to Expand ]
 
techno_hippyGuy
Old
#7  
Junior Member
Thanks Meter 4
Posts: 28
Join Date: Jul 2012
Have filed complaint with FCC and BBB, posted poor review on both Blue and White versons on VZW website, wall post ripping them apart on VZW facebook, poor reviews on every device site that will let me do so that I know of, personal contact with VZW reps filing complaints.

Any other avenues we can take?
 
tekhna
Old
#8  
tekhna's Avatar
Senior Member
Thanks Meter 309
Posts: 1,154
Join Date: Dec 2007
Here's what I wrote in my FCC complaint:


The new Samsung Galaxy SIII on Verizon Wireless has a locked and encrypted bootloader, which appears to violate the openness requirements that Verizon agreed to when it purchased Block C, pursuant to § 27.16 (b) of 47 CFR Ch. I (10–1–10 Edition) available here-- http://www.gpo.gov/fdsys/pkg/CFR-201...2-sec27-16.pdf

§ 27.16 (e) clearly states "Handset locking prohibited" except under certain circumstances previously delineated. The anti-consumer actions taken by Verizon impinge upon the free of use of devices by consumers, and potentially harms the livelihoods of developers, who may not be able to do their work on the device of their choice.
I would appreciate the FCC investigating and clarifying this situation.

Thank you,
The Following 2 Users Say Thank You to tekhna For This Useful Post: [ Click to Expand ]
 
techno_hippyGuy
Old
#9  
Junior Member
Thanks Meter 4
Posts: 28
Join Date: Jul 2012
Thinking further about it, with how prominent devices are in today's world, would various news providers not want to run this story as well?

I recommend tipping off any local newspaper and news station you have access to. Lets get this story out there~!
 
skennelly
Old
#10  
skennelly's Avatar
Senior Member
Thanks Meter 39
Posts: 203
Join Date: Dec 2010
Location: Quad Cities
Quote:
Originally Posted by Thalinor View Post
So we have root but we are still locked down unlike all other carriers. Basically this is going to turn into a Droid X situation and for those who know what I am talking about you know how bad this still sucks.

I am tired of this crap guys, and think with the amount of SG3 phones sold in the US and specifically Verizon, this is the time to strike back against all encrypted devices not just the GS3. We have dealt with this garbage long enough and now its time to end nonsense.

Kirtland and Packard, (310) 536-1000, 2361 Rosecrans Ave Ste 450, El Segundo, CA 90245

That's the law firm that won the huge case against Verizon over the Motorola v710 BT lockdown. I have left them a message asking if they will take this case too. In reality this one is going to vastly larger then the Moto case because of the number of users that have this device.
I know that the dev's are working there rear ends off, and I appreciate all their efforts. I am truly pulling for them and hope that they can get the bootloader figured out. I'm not an expert, but in my opinion the ROMs on the DX didn't compare to a fully unlocked device and I'd prefer not to have to suffer through 2+ years of touchwiz.

Thalinor,

I agree that this maybe turning into the Droid X. As a droid x owner, waiting and watching for 18 months to see VZW and Motorola dump on us, I don't think we'll get anywhere with them. There was a huge effort on the DX with petitions, phone calls, emails, twitter, and FB posts.

Just a thought, but what about petitioning the law firm to take up this case. We are not going to get anywhere from VZW's or Samsung's pity for us. If this bootloader is truly encrypted, and if it is anything like the DX, the only way we will get this device completely unlocked is through a legal obligation on VZW's part. I think our energy would be better spent with the Attorneys who stand to profit from this case rather than burning our energy on VZW and Samsung who probably don't give a crap. I would think that the law-firm would have some interest in this (maybe?):
Attached Thumbnails
Click image for larger version

Name:	Ci0gY.jpg
Views:	1147
Size:	33.8 KB
ID:	1185585  


SCH-I535

 
Post Reply+
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Go to top of page...