Related
If the mango update is being released to developers early, does that mean people who have unlocked their phones will be able to receive this update?
If this is not the case, then if a device is unlocked, can a user pay the $99 unlocking fee in order to have a developer unlocked device?
yes. pay 99$ and u will get it sooner.
Everyone will have it early.........lol......
Sent from my SGH-i917 using XDA Windows Phone 7 App
i've only heard it for emus in may. the rumor that devs get it first is a bit presumptuous...
domineus said:
i've only heard it for emus in may. the rumor that devs get it first is a bit presumptuous...
Click to expand...
Click to collapse
Well, it came from the horses mouth - Brandon Watson. Although, Joe Belfiore said there were no plans to this effect. Question is who we believe, Brandon who is in charge of developers or Joe who is VP for the entire platform.
Brandon also said 4 months ago that ms will make sideloading possible for all. I dont believe him. Probably developer unlocked devices will get mango like 1 day before the official release of mango, which btw will most likely be 100000 weeks before all other will get it through their carriers.
diboze said:
Brandon also said 4 months ago that ms will make sideloading possible for all. I dont believe him. Probably developer unlocked devices will get mango like 1 day before the official release of mango, which btw will most likely be 100000 weeks before all other will get it through their carriers.
Click to expand...
Click to collapse
Please show me where exactly he said this. I think you're paraphrasing incorrectly.
emigrating said:
Well, it came from the horses mouth - Brandon Watson. Although, Joe Belfiore said there were no plans to this effect. Question is who we believe, Brandon who is in charge of developers or Joe who is VP for the entire platform.
Click to expand...
Click to collapse
Joe...definitely Joe
domineus said:
Joe...definitely Joe
Click to expand...
Click to collapse
You mean the guy who, during US launch, said "Copy'n'paste is coming very very soon"? ;D
I dunno. I'm inclined to go with Brandon on this one. There has been whispers for quite some time already and I know other "features" I've discussed with certain team-members are actually on their way now, even though Joe said otherwise.
We will see what happens I guess. I'm not expecting it to be rolled out simultaneously with the tool update though, but definitely before public release.
emigrating said:
You mean the guy who, during US launch, said "Copy'n'paste is coming very very soon"? ;D
I dunno. I'm inclined to go with Brandon on this one. There has been whispers for quite some time already and I know other "features" I've discussed with certain team-members are actually on their way now, even though Joe said otherwise.
We will see what happens I guess. I'm not expecting it to be rolled out simultaneously with the tool update though, but definitely before public release.
Click to expand...
Click to collapse
very very soon is relative man relative! darn you einstein
but seriously I'm still waiting for a solution for sideloading that brandon stated in february sometime...that's all I have to say about that =)
who said that when
source please?
gkoonjul said:
source please?
Click to expand...
Click to collapse
feb ppcgeeks podcast
its on zune marketplace
Joe has expanded his answer a little. Basically he said they are working on it but hasn't planned (scheduled) it as of yet.
This is much more in-line with Brandon so I reckon we will get a developers image during the summer.
emigrating said:
Please show me where exactly he said this. I think you're paraphrasing incorrectly.
Click to expand...
Click to collapse
Earlier today, we were contacted by Brandon Watson, Director of Developer Experience for Windows Phone 7, to discuss the ChevronWP7 unlocking tool.
Through this discussion, we established a mutual understanding of our intent to enable homebrew opportunities and to open the Windows Phone 7 platform for broader access to developers and users.
To pursue these goals with Microsoft’s support, Brandon Watson has agreed to engage in futher discussions with us about officially facilitating homebrew development on WP7.
Dec 1st
http://www.chevronwp7.com/post/2057541126/pursuing-the-future-of-homebrew-on-windows-phone-7
and now tell me what has happend in this "further" discussion. Yes exactly nothing. No access to needed APIs, no officially supported homebrew, no update progress. Its just hot air coming out of his mouth...
diboze said:
Earlier today, we were contacted by Brandon Watson, Director of Developer Experience for Windows Phone 7, to discuss the ChevronWP7 unlocking tool.
Through this discussion, we established a mutual understanding of our intent to enable homebrew opportunities and to open the Windows Phone 7 platform for broader access to developers and users.
To pursue these goals with Microsoft’s support, Brandon Watson has agreed to engage in futher discussions with us about officially facilitating homebrew development on WP7.
Dec 1st
http://www.chevronwp7.com/post/2057541126/pursuing-the-future-of-homebrew-on-windows-phone-7
and now tell me what has happend in this "further" discussion. Yes exactly nothing. No access to needed APIs, no officially supported homebrew, no update progress. Its just hot air coming out of his mouth...
Click to expand...
Click to collapse
Like I said, you were paraphrasing it worng. Nowhere did he say that "ms will make sideloading possible for all". He said they agreed to engage in further discussions about facilitating homebrew development on WP7 - something they have done.
No access to needed APIs? You do realize they announced some 1500+ new APIs during MIX11, right? Tools are coming next month. As for homebrew development, well either you pay the $99 (or you get a free code from someone who can provide them - there are plenty around) or you wait until ManGo when there will very likely be some more news to share in regards to this. Did you really expect them to roll out a homebrew solution with NoDo?
they can announce a lot. they also said nodo would come "early 2011", when did it arrive..ah yes, it was the 2Q of 2011.
Moreover I have no problem with not having a free option for unlocking. I can unlock my phone anytime with my dev acc sponsored by dreamspark.
Its just that you cant believe them anymore. We have to wait 1y to get wp7 to where the other mobile OS are.
Like I said, you were paraphrasing it worng. Nowhere did he say that "ms will make sideloading possible for all". He said they agreed to engage in further discussions about facilitating homebrew development on WP7 - something they have done.
Click to expand...
Click to collapse
Its easy to say that now, but at that time it had to sound like they are working on something.
Did you really expect them to roll out a homebrew solution with NoDo?
Click to expand...
Click to collapse
I expected them to give the user more freedom. Phone and appwise. Then after nodo was not given...I just wanted the update...now I just want them to shut up. My hopes now are with hackers to open up the plattform and deliver some needed features. But even they arent interested in the OS anymore :'(
I wasn't very happy about the NoDo delays either, but it was released Q1. As unfortunate as the delays were I truly do think it was a one time thing. Any future updates should roll out on the date they tell us - bar operator testing of course, but since I'm on a unbranded device this is of no concern to me personally.
Sources tell me Mango will not be a year after launch, but we will see what happens there. In either case I never expected a large update before August 2011 anyways. What I did expect were lots and lots of smaller updates being rolled out with bugfixes - and this is an area they still have to work on, but Mango in the fall is right on schedule if you ask me.
To be honest, I never believed they would come up with an alternative to Chevron when the hole the tool used was closed. You may have thought so, but there was never any indication made that this would be the case.
As for hackers not being interested anymore. Are you living under a rock? DFT is working on a HSPL for the HTC line of devices and we have community sourced APIs opening up pretty much anything you could want the device to do.
Sure, I can understand where you're coming from - but at the same time I do think they are trying very hard to become more transparent. Can't really ask for more than that.
Even if developers do get priority, im sure someone will help the rest of us, so im not worries and dont care!
As for hackers not being interested anymore. Are you living under a rock? DFT is working on a HSPL for the HTC line of devices and we have community sourced APIs opening up pretty much anything you could want the device to do
Click to expand...
Click to collapse
.
They just opened up what should have already been there
It was not ment as an criticism towards the devs. I love what they do here. But they just dont have enough options to make the apps we users want.
To be honest, I never believed they would come up with an alternative to Chevron when the hole the tool used was closed. You may have thought so, but there was never any indication made that this would be the case.
Click to expand...
Click to collapse
And now there is no indication that they will give developers priority on mango? So what makes you think, that they will "deliver" this time?
diboze said:
.
And now there is no indication that they will give developers priority on mango? So what makes you think, that they will "deliver" this time?
Click to expand...
Click to collapse
There is indications. Brandon Watson has said we are working on it. Joe Belfiore said "no plans" which was apparently taken out of context enough for him to expand his answer days after saying basically the same as Brandon.
Sure, it might be more smoke and empty promises, but these people saying this compares very well with what they (and other senior team members) have said in the past - things which were now presented at MIX11.
Found this story on Gizmodo... Original link is http://feeds.gawker.com/~r/gizmodo/full/~3/zUciXU6yUzc/htc-will-unlock-the-bootloaders-on-its-android-devices
HTC finally gets it. The Taiwanese company will no longer lock the bootloaders on its Android devices. Rooting and flashing will be available to all. This news comes straight from CEO Peter Chou who made the following statement,
"There has been overwhelmingly customer feedback that people want access to open bootloaders on HTC phones. I want you to know that we've listened. Today, I'm confirming we will no longer be locking the bootloaders on our devices. Thanks for your passion, support and patience," Peter Chou, CEO of HTC
about bloody time too, lets hope moto follow suit, so when are they going to unlock current phones?
Hey guys, instead of only filling complaints with the FCC/Verizon, we should also be pursuing Samsung. I already went ahead and sent out a message on their contact site. It isn't a direct letter to a CEO or anything like that, but, one would believe that enough attention will get a letter slipped through the cracks.
Remember, use tact, type grammatically correct, and be extremely respectful. They may "work for us", and we may "own the product", but without them directly breaking a law, we have no reason to get out of line.
For those of you who have yet to file a complaint with the FCC, might as well spend the time doing that as well in the same sitting.
Here is the letter I sent, as well as the link to their form.
https://contactus.samsung.com/custo...MailQuestionProduct.jsp?SITE_ID=1&titleCode=1
Sir or Ma'am,
I am writing today in regards to the issue with the locked bootloader on the Verizon SCH-i535. In many regards this is one of the greatest phones I have ever used, I also have the Verizon Nexus device. My issue, along with thousands of other Verizon subscribers, is that we would like the capability to unlock the device for free use.
Verizon was just recently fined for not allowing certain apps like tethering to be used on the network by the FCC. I know this doesn't hold any relevance much to the bootloader, however, it seems as if with Verizon being the only network requiring such locks that there must be some other underlying decision. Manufacturers like HTC have taken measures to allow unlocking of their devices on Verizon with their HTC Developers portal. This may only be a personal, or small community opinion, but I believe the device would sell significantly better, at least among the knowledgeable developers/modders, if it was unlocked, or unlock-able.
There have been several petitions past around, as well as dozens of e-mails, tweets, and the like to try and understand why we are being forced to be locked down unlike the other carriers. It doesn't seem appropriate that the Galaxy Nexus should be capable of being unlocked, while this device cannot. How does locking one device prevent harming the "integrity" of the network? If this were truly an issue, I would assume any and every device would be locked before they were even introduced to the network, as well, other carriers would follow suit.
In a side note, many willing customers have been awaiting the "Developer Edition" device. We are all aware that there really is not difference between this device and ours, aside from being capable of unlocking. So, how can there be 2 of the same devices on the same network, yet the device we hold cannot be unlocked? It really seems as if you guys are trying to work FOR us, the customer, while Verizon is working against all of us.
In the end, really I am just another loyal customer curious as to if/when we could see a utility that would give us the capability of unlocking out device to use at our liking? We are all well aware that it may void our warranty, but in our eyes the benefit outweighs the risk.
I would like to ask politely if my concern be passed along to all of those that may be concerned, specifically Samsung Mobile US CEO and such.
Thank you all for your time, I look forward to a response.
Respectfully,
Andrew Lemacks
Click to expand...
Click to collapse
I will do the same with your template. Thank you sir
No problem. This tactic has worked on HTC devices, I would assume Samsung should follow suit. Although, Samsung has less to lose.
Very nice letter, hopefully you can get a response or have your letter be passed along to somebody who can say something that doesn't sound like automated message.
Will do. Thank you!
Sent mine.
JetBlue said:
Very nice letter, hopefully you can get a response or have your letter be passed along to somebody who can say something that doesn't sound like automated message.
Click to expand...
Click to collapse
Realized auto-correct isn't automatically correct after re-reading it, lol. *out* instead of *our*
duxup said:
Will do. Thank you!
Click to expand...
Click to collapse
detta123 said:
Sent mine.
Click to expand...
Click to collapse
Awesome, the more the better.
Anyone who hasn't seen, you may want to follow up with using EDNYLaw's template for filing your complaint in about the best manner possible. He couldn't make it any easier! When they FCC gets flooded with complaints like that, it's a lot harder to look the other way as you shred what look like "legal" documents. Take the time people. http://forum.xda-developers.com/showthread.php?t=1820634&page=8
Good luck!
No need for luck.
Already sent the FCC complaint, not just did this as well.
Awesome, let's continue the push everyone!
Edit: tapatalk thinks I'm on a nexus, lol.
Sent from my Galaxy Nexus using Tapatalk 2
Looks like I got my reply.
Code:
Dear Chris,
Thank you for your inquiry about your Samsung Galaxy S® III (Verizon)(SCH-I535) and we understand that you're having concern with the locked bootloader of the phone.
We also understand that you're requesting to have the option to unlocked the bootloader of the phone, instead of purchasing a Verizon's Developers Edition Galaxy S3 phone.
We apologize for any inconvenience this may have caused you. We appreciate hearing from our customers, as your comments are vital for us to continue improving our products, as well as our business.
There is no configurable option on the handset to unlock the Bootloader, as this may affect the software of the phone and also can cause unstable performace. The phone was designed manufactured to the specifications of Verizon Wireless for whom they are produced. We will forward your feedback request to the appropriate parties for further review and consideration.
Do you have more questions regarding Samsung Mobile Phones and Accessories? For 24 hour information and assistance, we offer our new FAQ/ARS System - Automated Response System at http://www.samsung.com/support.
Thank you for your continued interest in Samsung products.
Sincerely,
Victor
Technical Support
I haven't even received a standard reply yet. I didn't even get an automated response stating they got my inquiry. I may need to resubmit, unless this means they are actually reading what we say and replying in kind.
ddggttff3 said:
Looks like I got my reply.
Code:
Dear Chris,
Thank you for your inquiry about your Samsung Galaxy S® III (Verizon)(SCH-I535) and we understand that you're having concern with the locked bootloader of the phone.
We also understand that you're requesting to have the option to unlocked the bootloader of the phone, instead of purchasing a Verizon's Developers Edition Galaxy S3 phone.
We apologize for any inconvenience this may have caused you. We appreciate hearing from our customers, as your comments are vital for us to continue improving our products, as well as our business.
There is no configurable option on the handset to unlock the Bootloader, as this may affect the software of the phone and also can cause unstable performace. The phone was designed manufactured to the specifications of Verizon Wireless for whom they are produced. We will forward your feedback request to the appropriate parties for further review and consideration.
Do you have more questions regarding Samsung Mobile Phones and Accessories? For 24 hour information and assistance, we offer our new FAQ/ARS System - Automated Response System at http://www.samsung.com/support.
Thank you for your continued interest in Samsung products.
Sincerely,
Victor
Technical Support
Click to expand...
Click to collapse
AtLemacks said:
I haven't even received a standard reply yet. I didn't even get an automated response stating they got my inquiry. I may need to resubmit, unless this means they are actually reading what we say and replying in kind.
Click to expand...
Click to collapse
I never got a confirmation email from sending the message, but that showed up in my inbox today, so im guessing they are reading them one by one.
ddggttff3 said:
I never got a confirmation email from sending the message, but that showed up in my inbox today, so im guessing they are reading them one by one.
Click to expand...
Click to collapse
Well that is a good sign! Here's to hoping I get something good this weekend!
AtLemacks said:
Remember, use tact, type grammatically correct, and be extremely respectful. They may "work for us", and we may "own the product", but without them directly breaking a law, we have no reason to get out of line.
Click to expand...
Click to collapse
This. This! 1,000 times this!
The fastest way to get any communication to a company round-filed is to be disrespectful, to not meticulously grammar-check your writing (seriously, have at least one other person check it for you before sending), and to resort to foul language of any sort (even milder stuff like "damn", "hell", etc can give your letter an offputting tone).
As AtLemacks said, they're not breaking the law, and they've done this under the direction of Verizon. As crappy as Samsung can be in the software arena, they are not ultimately to blame for this (though they could bear some culpability for not pushing back).
So please, check your writing, have someone else read it, read it again, put it down and go to bed for the night, then read it again when you get up in the morning before you send it out.
I got a response from Samsung today and I just had to post it here. My emotions as I initially saw that I had this but then started, and completed, reading it: :victory: -> ->:rofl: -> :crying:. I have not altered ANY of this email including the names. As you read it, keep in mind my letter was extremely polite and grammatically correct...and my name is NOT Rick.
Dear Rick,
Thank you for your inquiry. I see that that you have question of unlock the bootloader so you can customize the phone.
As of now We still do not have updates about that, and as of now verizon lock the bootloader.But if we have update about unlocking the bootloader will be posting it to the website so please do visit our website(www.samsung.com/us).
At your earliest convenience, please call Samsung Customer Support by phone at our toll free number 1-800-726-7864. Please choose the following options by pressing 1 – Customer, 2 – Tablet, and then 3 – Wi-Fi Galaxy Tablet.
We appreciate your continued interest in Samsung products.
Sincerely,
Claire
Technical Support
I got the good ole generic reply back too, that it has been forwarded. Now, if there is any weight to the statement, lets keep the push going and fill up a few e-mail inbox's!
Do you think there will be a root exploit for 2.20 soon and if so when do you think it will be available?
I hope there's some devs willing to work on it. It's a relatively new software version. We all gotta have some patience. I'd really like to get CM10 up and running on the HOX. Works great on my Nexus 7.
thephased said:
I hope there's some devs willing to work on it. It's a relatively new software version. We all gotta have some patience. I'd really like to get CM10 up and running on the HOX. Works great on my Nexus 7.
Click to expand...
Click to collapse
I know, I actually emailed htc saying something like "we pay for these phone with our money we should be able to do what we want to do with them." and here is what they said: "I understand that you have some concerns regarding the bootloader unlock on the HTC One X and I would be more than happy to assist you with information!
HTC is committed to listening to users and delivering customer satisfaction. Since announcing our commitment to unlockable bootloaders, HTC has worked to enable our customers to unlock the bootloader on more than 45 devices over the past six months. In some cases, however, restrictions prevent certain devices from participating in our bootloader unlocking program. Rest assured, HTC is committed to assisting developers in unlocking bootloaders for HTC devices and we'll continue to unlock additional devices in the future."
I personally would love to be able to unlock the AT&T HOX through the htcdev website that would be awesome!
mmmatt312 said:
I know, I actually emailed htc saying something like "we pay for these phone with our money we should be able to do what we want to do with them." and here is what they said: "I understand that you have some concerns regarding the bootloader unlock on the HTC One X and I would be more than happy to assist you with information!
HTC is committed to listening to users and delivering customer satisfaction. Since announcing our commitment to unlockable bootloaders, HTC has worked to enable our customers to unlock the bootloader on more than 45 devices over the past six months. In some cases, however, restrictions prevent certain devices from participating in our bootloader unlocking program. Rest assured, HTC is committed to assisting developers in unlocking bootloaders for HTC devices and we'll continue to unlock additional devices in the future."
I personally would love to be able to unlock the AT&T HOX through the htcdev website that would be awesome!
Click to expand...
Click to collapse
Unfortunately, the carriers have the upper hand when it comes to bootloaders and whether they allow them to be unlocked. It could be a while, if ever, until HTC adds the AT&T HOX to their supported unlockable devices. I'll take an unofficial method instead if that's what's available.But yeah, it would be great if it happened officially.
asking when root will be available is like asking a dev when his rom is going to be updated. rest assured it will happen eventually, but the devs that do this do it in there spare time when not at work or with family, and most of the time end up doing all for free and risking there own devices. so the answer is it will come but only when it ready.
When you find the exploit
Sent from my HTC One X using Tapatalk 2
Get your hopes up for the 4th.
http://forum.xda-developers.com/showthread.php?t=1832921
Sent from my HTC One XL using Tapatalk 2
superchilpil said:
When you find the exploit
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Lol.
Those are the kindest remarks I've ever seen to a thread like this being posted. Is anybody going to say how ignorant of a question that is to ask? Mods please move this thread to the ESP forums for our psychics evaluate.
18th.abn said:
Those are the kindest remarks I've ever seen to a thread like this being posted. Is anybody going to say how ignorant of a question that is to ask? Mods please move this thread to the ESP forums for our psychics evaluate.
Click to expand...
Click to collapse
All the jerks bought S3's.
Sent from my HTC One XL using Tapatalk 2
I know that Dan found an exploit, I have a feeling this is part of why nobody seems to be complaining to AT&T about the locked bootloader, but the problem is that it isn't a permanent fix, granted we have the ability to disable automated updates, etc. My problem is that AT&T is going to lock all devices from here on out, simply because we allowed them too.
So what can we do?
AnthomX said:
So what can we do?
Click to expand...
Click to collapse
Don't give AT&T your business? I know the locked bootloader issue incenses the Android modding community, but the vast majority of consumers don't know and don't care. AT&T is practically the government, and they don't care either. It's frustrating, but if you don't like it please vote with your dollars.
burhanistan said:
Don't give AT&T your business? I know the locked bootloader issue incenses the Android modding community, but the vast majority of consumers don't know and don't care. AT&T is practically the government, and they don't care either. It's frustrating, but if you don't like it please vote with your dollars.
Click to expand...
Click to collapse
I can agree with that, my only complaint is the small majority of us that notice the lock. Speaking with our money in this case isn't going to make much of a point. There simply isn't enough of us to make them take a hit in their margins. So my guess is that in this instance, it is, what it is, for us? I know AT&T provides us (me and family) the best service in terms of voice/data.
That is just disappointing, because other carriers will follow behind it.
AnthomX said:
I know that Dan found an exploit, I have a feeling this is part of why nobody seems to be complaining to AT&T about the locked bootloader, but the problem is that it isn't a permanent fix, granted we have the ability to disable automated updates, etc. My problem is that AT&T is going to lock all devices from here on out, simply because we allowed them too.
So what can we do?
Click to expand...
Click to collapse
Right now there isn't many legal avenues in favor of the consumer concerning the access to unlocked devices. Congress has given the carriers most of the deciding power over what extent the end-user may manipulate the software on the device. After a petition gained enough friction and reached the White House, the executive branch has agreed consumers deserve the right to invoke their will over devices sold to them without criminal liability, there has yet been any legislative change regarding the matter.
Ultimately, what we can do is multi-faceted to get the attention of carriers [AT&T] to cave to our demands:
1: We can vote with our money by refusing to purchase devices distributed by them, citing their abuse of power over devices sold to consumers -- leaving us no freedom to do as we please with merchandise we contractually own.
2: We can appeal to authority by raising the issue to a federal level to be examined by either higher courts, consumer affairs, Better Business Bureau, or writing your congressman.
3: Start an online petition and hope it gains enough traction to put AT&T and other carriers in a negative light publically on the national stage.
These options work well with numbers and have a better chance of success when done in conjunction with one another. The armchair approach has very little chance of success and often doesn't even merit a reply by way of spokesperson.
AnthomX said:
I can agree with that, my only complaint is the small majority of us that notice the lock. Speaking with our money in this case isn't going to make much of a point. There simply isn't enough of us to make them take a hit in their margins. So my guess is that in this instance, it is, what it is, for us? I know AT&T provides us (me and family) the best service in terms of voice/data.
That is just disappointing, because other carriers will follow behind it.
Click to expand...
Click to collapse
I agree, but to play devil's advocate, I can see why AT&T would want to lock down devices. I imagine since they've been selling Android devices they've had to process tons of RMAs on devices that were bricked by amateurs installing the wrong ROMs. That may well amount to a minuscule hit in their bloated profit margin, but a corporation tends to do whatever it can to prevent dollars from leaking out. If the locked bootloader prevents the casual ROM flasher from bricking a new S4, then they view that as success. I don't know if that's why they did it, though.
The other side to that, of course, that an unlocked bootloader makes it easy to restore a bricked device back to stock. I'd like to see AT&T and other carriers reach out to the dev community more and have some provisions for installing alternate ROMs and OSes on the devices. I'd also like them to just sell me bandwidth and not interfere with content or operating systems, but I won't hold my breath!
antde201 said:
Right now there isn't many legal avenues in favor of the consumer concerning the access to unlocked devices.
Click to expand...
Click to collapse
burhanistan said:
I agree, but to play devil's advocate,
Click to expand...
Click to collapse
AGREED very much Burhanistan, I know that is a hit for AT&T, but you know, they could offer repair services at a decent rate that could fix these bad flashes, as most of the time only a JTAG is needed. Which leads into support and encouragement for the Android communities. But, one can dream. They are more about that profit margin than a profit margin AND great customer service.
Antde, I am looking at starting a petition, maybe gain some traction there? Who knows, but I think you are right, in the end, AT&T doesn't want our business, and I am ok with that. Unfortunately it will be a headache similar to swapping from Apple after using them for so many years. Time to bust out the aspirin I guess. We will see.
Becasue carriers dont care about what we think about locked bootloaders.At the end of the day this device is making millions for them think about it to them it doesnt make a difference.I myself work for a carrier in the U.S and trust me to them what ever rants and complaints we post mean squat....
Anyways its going to be unlocked soon when the VZW releases so whatever I dont even get why we should make such a big deal locked bootloaders always get hacked ...
burhanistan said:
I agree, but to play devil's advocate, I can see why AT&T would want to lock down devices. I imagine since they've been selling Android devices they've had to process tons of RMAs on devices that were bricked by amateurs installing the wrong ROMs. That may well amount to a minuscule hit in their bloated profit margin, but a corporation tends to do whatever it can to prevent dollars from leaking out. If the locked bootloader prevents the casual ROM flasher from bricking a new S4, then they view that as success. I don't know if that's why they did it, though.
The other side to that, of course, that an unlocked bootloader makes it easy to restore a bricked device back to stock. I'd like to see AT&T and other carriers reach out to the dev community more and have some provisions for installing alternate ROMs and OSes on the devices. I'd also like them to just sell me bandwidth and not interfere with content or operating systems, but I won't hold my breath!
Click to expand...
Click to collapse
There's more to a carrier's decision to lock down a device's bootloader than just pure spite and asserting their control. Carriers are also charged with mobile security, protection of their assets (bandwidth), and again security.
An unlocked bootloader theoretically opens the floodgates to a plethora of security threats to both the device and information stored and/or shared therein. Google and their partners are pushing mobile security to both stay relevant in the mobile OS market and to appeal to other markets where they may have been previously overlooked, such as defense and business.
You also have to consider the possibility of unregulated mobile tethering which falls under the umbrella of loss prevention to any business.
Lastly, as you and others have mentioned, the possibility of insurance claims due to bricked devices. Though I'd argue that this area doesn't pose much risk to the carrier directly as you void your warranty as soon as you flash a custom ROM.
So with all of these facets together, you'd see how it would be a no brainer to a corporation to purchase the secure version of an OEM device. Especially if you've chosen to adopt a subsidized device. The contract you sign is subject to whatever terms they produce and if you do not agree, you're free to stay with your current device and leave when your contract expires. I don't care for this sentiment, but it's the reality they have procured.
I think they did it to fight back against tethering.
ATT getting phone manufacturers to lock their phones started a while back. IIRC the first big uproar was for the HTC Vivid. IMHO it's for security and ATT keeping their big accounts. BB ruled for so long because of security. iPhones are the same way. Companies want a secure device. Moto (one of the main ones that market to business use) has always had the stingiest bootloaders regardless of carrier.
poofyhairguy said:
I think they did it to fight back against tethering.
Click to expand...
Click to collapse
Ya because that really stopped us from tethering... Oh wait..