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:
I was told by a Verizon Wireless Representative that Verizon would not allow me to remove the software installed that verifies the device only runs "Verizon approved" software, and the encryption protecting it. As this explicitly limits my ability for a new carrier to provide their software on my device, for use on their network, I feel it is a direct violation of FCC code § 27.16(e). Any Operating System uploaded to my device not "Approved by Verizon" renders the device non-functional and requires the device be sent back to the manufacturer or Verizon for reapplication of "Verizon Approved Software" effectively restricting my ability to use my device on the network of my choice. Thank you.
Click to expand...
Click to collapse
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)
Wasn't there something about all the above is null if the company needs to lock it down to provide better service?
Sent from my SCH-I535 using Tapatalk 2
There was something that if they say it is for network security that is the loop hole they can use. But they have double standards of having some phones with unlocked bootloader not to mention allowing the developer edition which is the same exact phone just not locked down.
Sent from my SCH-I535 using xda app-developers app
Forgetfull said:
Wasn't there something about all the above is null if the company needs to lock it down to provide better service?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I think you're referring to the unlock request made by a Droid Razr user, which what you wrote was essentially Verizon's official response.
We're taking a different approach here, which asks the bootloader be unlocked, not just because, but for the ability to load a different carriers software on the device to switch said phone to a different carrier. A request, which has nothing to do with providing any service to the user, at all. This is the beauty in it.
Related
Completely out of curiosity...
why is it that iPhone users with At&T can Jailbreak then Unlock their phones via software hacks, but I have to either call up T-Mobile for some code, or pay some dodgy guy over ebay??
http://electronics.howstuffworks.com/how-to-tech/how-to-unlock-cell-phone3.htm
doesnt explain anything :S
Try this, more phones coming all the time.
Great way to root your android.../bit.ly/aa4jxJ
Sent from my Android for Telechips TCC8900 Evaluation Board (US) using XDA App
thanks but i was looking for Unlocking from Network providers, not rooting?
from the limited knowledge i have on the subject and the things ive picked up while owning an iphone:
the iphone started out being locked to the networks indefinitely. at&t, to this day i believe, didnt/dont provide unlocking of the iphone. the way regular unlocks work, ie by code, is that the imei of the phone is used with an algorithm to provide the code. the people who have this algorithm are either the phone manufacturer and/or the network provider.
tmobile may be able to generate the code themselves, or go direct to the manufacturers for the code. the ebay sellers pay for your specific code, and then sell it onto you, basically middle men.
however with the iphone, neither at&t nor apple wanted to assist in unlocking, so without access to the algorithm generated codes, the only other option was software hacks.
problems with iphone software unlocks are that they can be wiped off with a restore; when a baseband update is released in a new firmware update, it can take a while for an update software unlock is released; you can get signal problems (blacksn0w, ios4.0.2 on unlocked 3g). nowadays, uk carriers at least, unlock phones eg o2, with t&c of course.
all in all, id rather pay the £6 to the "dodgy guy" on ebay, than have a software unlock.
ah thanks for that!
There is a new FCC chairman and he wants carriers to "unlock" phones. The argument for bootloader and carrier lock are quite similar. The definition of unlock is at play. It is super easy to lobby them.
If you want to complain then write the fcc: http://www.fcc.gov/complaints
I tried to purchase a new Samsung Galaxy Note 3 Without a contract at full retail price. AT&T. I would like to modify the phone for a visual impairment application. AT&T has a phone unlock policy: https://www.att.com/deviceunlock/client/en_US/”
They have limited the unlock definition saying it does not apply to an “unlocked bootloader” which is necessary to modify the device. AT&T and Verizon are the only worldwide carriers with this practice. They have added custom software to permanently destroy the device if tampered with. They created a shadow policy on bootloaders:http://www.androidpolice.com/2013/0...tloaders-so-stop-asking-us-about-every-phone/.
The claim “To ensure a safe and consistent experience on your wireless device, we do not support unlocked bootloaders” is nonsense since they allow ANY GSM device on their network. Please add bootloaders explicitly to the FCC unlock policy.
sonicthoughts said:
There is a new FCC chairman and he wants carriers to "unlock" phones. The argument for bootloader and carrier lock are quite similar. The definition of unlock is at play. It is super easy to lobby them.
If you want to complain then write the fcc: http://www.fcc.gov/complaints
I tried to purchase a new Samsung Galaxy Note 3 Without a contract at full retail price. AT&T. I would like to modify the phone for a visual impairment application. AT&T has a phone unlock policy: https://www.att.com/deviceunlock/client/en_US/”
They have limited the unlock definition saying it does not apply to an “unlocked bootloader” which is necessary to modify the device. AT&T and Verizon are the only worldwide carriers with this practice. They have added custom software to permanently destroy the device if tampered with. They created a shadow policy on bootloaders:http://www.androidpolice.com/2013/0...tloaders-so-stop-asking-us-about-every-phone/.
The claim “To ensure a safe and consistent experience on your wireless device, we do not support unlocked bootloaders” is nonsense since they allow ANY GSM device on their network. Please add bootloaders explicitly to the FCC unlock policy.
Click to expand...
Click to collapse
You should mention specifically that T-Mobile and Sprint have their bootloaders unlocked and there have been no problems with inconsistent service. AT&T and Verizon are just abusing their power. Being the largest two carriers, they dictate to manufacturers to lock down the devices to force us not to tether anyway but through them and to use their "bloat apps". Any other reason they state they lock the devices down for is absurd and bs.
sonicthoughts said:
There is a new FCC chairman and he wants carriers to "unlock" phones. The argument for bootloader and carrier lock are quite similar. The definition of unlock is at play.
Click to expand...
Click to collapse
No, the FCC couldn't care less about our ability to modify our phones. It has zero to do with antitrust or consumer portability. Therefore, the FCC won't care.
No matter how you attempt to word it, it's not the same thing, doesn't do the same things, and in reality nobody cares except the XDA echo chamber.
sonicthoughts said:
There is a new FCC chairman and he wants carriers to "unlock" phones. The argument for bootloader and carrier lock are quite similar. The definition of unlock is at play. It is super easy to lobby them.
If you want to complain then write the fcc: http://www.fcc.gov/complaints
I tried to purchase a new Samsung Galaxy Note 3 Without a contract at full retail price. AT&T. I would like to modify the phone for a visual impairment application. AT&T has a phone unlock policy: https://www.att.com/deviceunlock/client/en_US/”
They have limited the unlock definition saying it does not apply to an “unlocked bootloader” which is necessary to modify the device. AT&T and Verizon are the only worldwide carriers with this practice. They have added custom software to permanently destroy the device if tampered with. They created a shadow policy on bootloaders:http://www.androidpolice.com/2013/0...tloaders-so-stop-asking-us-about-every-phone/.
The claim “To ensure a safe and consistent experience on your wireless device, we do not support unlocked bootloaders” is nonsense since they allow ANY GSM device on their network. Please add bootloaders explicitly to the FCC unlock policy.
Click to expand...
Click to collapse
the argument for forcing att/verizon to unlock phones and bootloaders falls flat when other companies(tmobile sprint) offer phones with unlocked bootloaders and unlocked for gsm use(tmobile-if you buy full price)
no one is forcing you to stick with att version, when there are other options, it sounds silly when its a gsm capable phone you're complaining about
FCC does not regulate this part of the industry nor do they regulate what a manufacturer or dealer puts on the phone as long as it does not violate FCC rules in the way it performs as a phone.
In short the FCC has no authority on the subject of bootloaders. End of thread..
http://www.droid-life.com/2014/10/31/nexus-6-working-on-verizon-out-of-the-box/
If it has been posted already please delete.
Sent from my SGH-M919 using XDA Free mobile app
idonthavename.7 said:
http://www.droid-life.com/2014/10/31/nexus-6-working-on-verizon-out-of-the-box/
If it has been posted already please delete.
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
Keep in mind that this was a review unit, likely from Motorola (or possibly Google). CDMA carriers (Verizon, Sprint, US Cellular, etc.) tend to whitelist IMEI numbers that are sent to them, along with those sent directly from the manufacturer (warranty replacements, etc.), and other contractual partners (such as Google Play). (The manufacturer and contractual partners are responsible for submitting the IMEI numbers to the carrier.) Thus, when an IMEI comes in from another carrier, they know it wasn't sold by them, directly from the manufacturer, or their contractual partners, meaning it was likely sold by a competing carrier, and can deny activation.
To be clear, the Nexus 6 may or may not work this way. We simply don't know. However, there has been enough historical evidence to be wary. GSM carriers don't tend to whitelist IMEI numbers like this, so usually aren't affected.
As a review unit, it's certainly a good sign that Verizon supports it out of the box, but ultimately it doesn't PROVE that buying one from, say, T-Mobile and trying to activate it with Verizon (or any other CDMA carrier) will similarly work
is there any way to get volte in samsung note 3 sm-9005 by flashing official roms if yes then pls friend post the tutorial it will be very kind of you
I want volte tooo
surajyadav98 said:
is there any way to get volte in samsung note 3 sm-9005 by flashing official roms if yes then pls friend post the tutorial it will be very kind of you
Click to expand...
Click to collapse
even i want it bro. have u got any way for it
prashantxpe said:
even i want it bro. have u got any way for it
Click to expand...
Click to collapse
Learn to search its the rules .
https://forum.xda-developers.com/search/forum/2494?query=volte
***voLTE, WiFi calling, Tmobile***
=======================================
(linked from XDA by David Ruddock)
T-Mobile Unofficially Speaks To Us About Band 12 LTE / VoLTE And Unlocked Smartphones,
And Yep It's Still Confusing
-----------------------------------
Yesterday, we published an article asking an open question: what is up with T-Mobile band 12 support being removed from some unlocked smartphones?
Today, T-Mobile contacted us to speak about said article. Unfortunately, T-Mobile was unwilling to provide any official on-record responses to our questions. But after a short discussion, I can provide you some information I have learned on background (journalist speak for "cannot be directly quoted or attributed to anyone"). First:
On T-Mobile, any device on its network with band 12 LTE data support must also support T-Mobile Voice over LTE services and E911.
The E911 part isn't particularly important in terms of the certification requirement - all phones sold in America are technically E911 compliant, because by law they have to be. The problem is that E911 compliance is inextricably linked to T-Mobile's VoLTE requirement for band 12. Without VoLTE support, a device on band 12 service would be unable to make phone calls of any kind if no other T-Mobile band was available (it will not know to fall back to AT&T roaming - the call will just flat-out fail), and that would include making 911 calls, meaning the device would for legal purposes likely be out of E911 compliance, and T-Mobile could get in trouble with the FCC. Not to mention, you could have somebody trying and failing to dial 911 in an emergency, which would of course be terrible. And yes, by removing band 12 support, you can make E911 work, because the phone then has no signal at all and knows to try to roam onto another compatible network (AT&T usually) to complete the call. This is both a safety and liability issue, and it is easy to understand where T-Mobile would be coming from in terms of concern about this - they do have something of a history with E911 debacles. Clearly this is a very real safety concern, and I do sympathize with T-Mobile in the sense that they obviously can't just sit here and do nothing about it. But there are practical concerns for OEMs here - adding T-Mobile VoLTE isn't just as easy as flipping a switch.
In order to obtain VoLTE compliance for band 12, phones must go through T-Mobile's rigorous network certification process (and yes, unlocked phones can go through this certification).
Speaking off the record to one major smartphone vendor, we have learned that there are very real costs and complexities associated with obtaining that certification, and it must be done on a device-by-device basis. Many phone OEMs, then, may simply choose to remove band 12 support from their unlocked smartphones sold in America. This could mean phones like the Alcatel OneTouch Idol 3 (4.7 and 5.5), the Huawei Ascend P8 Lite, the Huawei SnapTo, OnePlus 2, Moto X Style (aka Moto X 2015 PE), Moto X Play, HTC One M9 Unlocked and Developer Edition, Saygus V2, and various imported phones (ie, some global unlocked Sony or Samsung devices) or unlocked branded AT&T phone models may lose band 12 support in future software updates. The fact is, we don't know what will happen, or to which phones, or when. Some manufacturers may choose to get T-Mobile VoLTE certification (Motorola has hinted as much with the new Moto X 2015 PE), but many may also simply choose to quietly disable band 12 for T-Mobile in software updates. Motorola, as we know, has already done this with the Moto E.
It is not clear what action, if any, T-Mobile will take if a smartphone vendor refuses to remove band 12 data support from their device and also refuses to undergo the T-Mobile VoLTE certification process. (Ie, they want to keep B12 data but not bother with B12 VoLTE certification.)
This is basically the kicker. What will T-Mobile do if a vendor says "no way" to dropping band 12 data, but also doesn't want to go through the VoLTE certification process? We don't know. They might not do anything. But they might do something. Again, this is why speaking to T-Mobile about this situation was so frustrating. Not only we were unable to directly quote or attribute any of the information we were provided, but there was also no clarity as to what would happen in the event the band 12 situation comes to a head with an OEM that refuses to "play ball."
It seems unlikely that any OEM would refuse T-Mobile's request here, though, as most of them are also partnered with the company on T-Mobile-branded devices.
We have asked T-Mobile again for an on-record statement about this entire situation, because it would help clarify it immensely. As things stand now, T-Mobile is attempting to put the ball in the court of manufacturers. Which, to be fair, manufacturers do have a role to play here - they have to make the decision to drop band 12 or go through the T-Mobile certs for these unlocked band 12 devices. Or, potentially, just ignore T-Mobile's band 12 requirements entirely and see what happens. Unfortunately, as you might guess, most smartphone OEMs have zero desire to discuss upcoming software updates in detail, or to ever put their product in a situation where it is being highlighted for losing a feature. That makes our job here a difficult one.
We will update you on any more information we receive about this situation, including any response from T-Mobile or potentially-affected device manufacturers we have reached out to.
---------------------------------------------------------
surajyadav98 said:
is there any way to get volte in samsung note 3 sm-9005 by flashing official roms if yes then pls friend post the tutorial it will be very kind of you
Click to expand...
Click to collapse
Offical rom??? if your mean stock rom, yes it possible to have VoLTE, provided your network support!
I have a Samsung Galaxy S7 apparently originally a 930V. It purchased it from someone used in perfect condition, and it is running the Samsung stock AT&T firmware of 930U. The phone functions perfectly well, except for Wifi calling, HD Voice, and Number Sync with my Galaxy Gear S3 Frontier that I did purchase directly from AT&T. When I talked to the 'advanced' technical support, they looked up the IMEI of the phone and said, 'that IMEI is not shown as an AT&T branded phone as it is not in our database of devices sold by AT&T, therefore these services will not work.' Long story short, the Samsung Galaxy S7's are identical hardware, and it's running Samsung stock AT&T firmware. This means there is ZERO technical reason why these services won't work. They don't work simply because AT&T blocks them from working because the IMEI of my phone isn't in their database of phones they themselves have sold. So, they are literally blocking me from using services that I pay for because I didn't buy the phone from them, which is their way of trying to force me to purchase a phone from them. I filed a complaint with the FCC. They sent my complaint to AT&T, whereby I received an email from Misti Nations at the Office of the President for AT&T, who wanted to contact me to 'work towards a resolution.' Her definition of 'work towards a resolution' was to try to force me to buy a phone from them. Didn't try to debate at all on the merit of the complaint, didn't deny that there is zero technical reason it won't work, all she did was point to their terms of service agreement which says 'if you bring your own phone to AT&T, it is POSSIBLE that not all services will work correctly', which in her mind explains away my complaint. It does not. 'May not work' is far, far different than 'we will not allow to work.' So, I'm waiting to hear back from the FCC on this, just had the call with Misti this morning.
My opinion is we can't let carrier's block features simply because they don't like that the phone wasn't purchased from them. If they were allowing the services to attempt to function and they didn't, I wouldn't complain. I am PISSED because they are specifically preventing me from using services I am paying for, simply because they want to force me to buy a phone from them. We should NOT let AT&T (and others if they also follow this practice) to get away with either extortion, or pure laziness on their tech side (we don't want to allow it because who knows it MIGHT cause an issue, we're too lazy to check). So please, others in my boat that see this thread, also file a complaint with the FCC. Let's flood them and stop this extortionist practice by carriers!
No thanks: no evidence of "blocking" services or "forcing" purchases. You actually sound a bit nutz.
I have an original 930u on stock firmware. It lacks the software to make those features work along with all of the AT&T bloat. I believe the software for the true AT&T variant has and allows those options but it has not been able to be added to the U firmware.
Sent from my SM-G930U using Tapatalk
Other carriers do this all the time. I brought my ATT device to cricket and now I am not able to use wifi calling since it's not on their imei database to allow the feature to be turned on even though it would work no problem.
spasch said:
I have an original 930u on stock firmware. It lacks the software to make those features work along with all of the AT&T bloat. I believe the software for the true AT&T variant has and allows those options but it has not been able to be added to the U firmware.
Sent from my SM-G930U using Tapatalk
Click to expand...
Click to collapse
I have the same phone, and can't use it in Southamerica. I think it's a AT&T model. I'm not interested in updating software or anything, just any stock rom available that it would make it work? Moderator Edit: NO IMEI talk on XDA I can't even root the phone with odin.
First off, make sure you have the right G930U AT&T firmware, not the unbranded one. Second of all, you're flashing different firmware and expecting them to accommodate you; that's LOL-worthy.