Database Info

AT&T and Samsungs explanation about failed updates

I just spoke with the Android dept at AT&T who where I spoke to a gentleman named Jeremy Everson. After he informed me that I was the 6th caller he had had in the past 3 hours about the failing updates...he called Samsung on a 3-way conversation with me.
Here's what I found out. If you DO NOT HAVE GPS, EMAIL OR MMS PROBLEMS...THEN THE UPDATE MAY BRICK YOUR PHONE. THIS IS ATT AND SAMSUNGS RESPONSIBILITY AND THEY ARE GOING TO FIX IT.
AT&T IS WORKING DILIGENTLY WITH SAMSUNG AND MR. EVERSON INFORMED ME THAT THEY ARE FRUSTRATED AT THE BLURRY COMMUNICATION WITH SAMSUNG OVER THIS UPDATE.
All in all...there are no answers yet as to why this update isnt working...but we know that it is causing problems.
Basically, what that tells me is stop resetting, odin-ing, unrooting, and reflashing...it is a problem on Samsungs end...not your device.

fiendiish said:
I just spoke with the Android dept at AT&T who where I spoke to a gentleman named Jeremy Everson. After he informed me that I was the 6th caller he had had in the past 3 hours about the failing updates...he called Samsung on a 3-way conversation with me.
Here's what I found out. If you DO NOT HAVE GPS, EMAIL OR MMS PROBLEMS...THEN THE UPDATE MAY BRICK YOUR PHONE. THIS IS ATT AND SAMSUNGS RESPONSIBILITY AND THEY ARE GOING TO FIX IT.
AT&T IS WORKING DILIGENTLY WITH SAMSUNG AND MR. EVERSON INFORMED ME THAT THEY ARE FRUSTRATED AT THE BLURRY COMMUNICATION WITH SAMSUNG OVER THIS UPDATE.
All in all...there are no answers yet as to why this update isnt working...but we know that it is causing problems.
Basically, what that tells me is stop resetting, odin-ing, unrooting, and reflashing...it is a problem on Samsungs end...not your device.
Click to expand...
Click to collapse
That doesn't help those of us with completely bricked phones...

qwertyaas said:
That doesn't help those of us with completely bricked phones...
Click to expand...
Click to collapse
Contact Samsung 1800 726 7864. That's the number I was given by AT&T to call. Or, take your phone to an AT&T store. You did nothing to brick your device. This is their issue.

We have the choice to not do the update, right? I think I read that from another thread somewhere, but I just wanted to double check. I haven't received a notification from AT&T yet about the update, but when I do, I don't think I want to go through with it seeing how there are a lot of issues with the update.

"AT&T does not provide technical support for the Samsung Captivate update and makes no warranties, express, implied or statutory, as to the content within this solution; such content is provided "as is" and with all faults, and your use of the content is at your own risk. "
this is a mess

Oh mannnn...after reading your painful story with AT&T & Samsung...all I want to say to those people is "F*** YOU!!".
WTH have you guys been doing for 2 months???
You have spent 2 months to come up with the phone bricker not the problem fixer???
I really want to switch to Android world but it seems starting with Samsung is one hell bad idea of mine. Maybe I should wait for the phones from other makers.

well... at least they're aware that there is an issue

Well.. if you think about it, as soon as we rooted our units.. there goes AT&T's responsibility.

That's the thing I noticed the most about AT&T, they are pros are shifting to blame to anyone but themselves.
If you're under the 30 day return policy return it ASAP, No hesitation, talk to a manager if necessary.
For those over 30 days hope for the best, make AT&T and Samsung aware of your issue.

I just got off the phone with AT&T they are sending me a new phone. Spent about 45 minutes on the phone doing through all of test they do to try and get the update. The tech I talked to is actually overnighting me a new phone. I had to agree to the terms that there is no physical damage or liquid damage. There is none.
I claimed my GPS failes to aquire a viable signal. Network tower triangulation is not acceptable. I waited passed the 30 days for this update that was promised and I can no longer get.
I have used ODIN in the past and believe something with it is causing the problem. Before I ever used odin I had a backup made of my entire phone with just a root.
Tried to use ODIN and restore my previous ROM with no luck still failing at 50%. I have removed all traces of lagfix, root, roms and still can not get the update to take. I even swapped out the SIM card at the store. All of it failed so the tech had them rush me a new phone.

thehavock18 said:
I just got off the phone with AT&T they are sending me a new phone. Spent about 45 minutes on the phone doing through all of test they do to try and get the update. The tech I talked to is actually overnighting me a new phone. I had to agree to the terms that there is no physical damage or liquid damage. There is none.
I claimed my GPS failes to aquire a viable signal. Network tower triangulation is not acceptable. I waited passed the 30 days for this update that was promised and I can no longer get.
I have used ODIN in the past and believe something with it is causing the problem. Before I ever used odin I had a backup made of my entire phone with just a root.
Tried to use ODIN and restore my previous ROM with no luck still failing at 50%. I have removed all traces of lagfix, root, roms and still can not get the update to take. I even swapped out the SIM card at the store. All of it failed so the tech had them rush me a new phone.
Click to expand...
Click to collapse
Wow, so anyone getting this phone should really just wait for the phones that are pre-installed with this update already.
Sounds like Ill have to wait a few months then.
Thanks for the info.

fiendiish said:
Contact Samsung 1800 726 7864. That's the number I was given by AT&T to call. Or, take your phone to an AT&T store. You did nothing to brick your device. This is their issue.
Click to expand...
Click to collapse
I was within my 30 days so they gave me a new Captivate. Sadly, I haven't had a chance to back up my old phone so everything is gone from there.
For some reason, the AT&T employee said this uses my only 'exchange' in terms of warranty. I didn't even bother to argue as that makes no sense - how is replacing a bricked phone (that was bricked on an AT&T update) 'exchanging' the phone [as in being able to exchange to a different phone].

orlandoxpolice said:
"AT&T does not provide technical support for the Samsung Captivate update and makes no warranties, express, implied or statutory, as to the content within this solution; such content is provided "as is" and with all faults, and your use of the content is at your own risk. "
this is a mess
Click to expand...
Click to collapse
I would think that one could argue successfully to get a new phone regardless, because this update is being pushed to the phone and not voluntarily download (by some), I woke up to a message that the device had fail to connect to the server (thank god) for the update. but if they're updating your phone without your approval then they (whomever is pushing the update) can't absolve themselves of responsibility. unless my not reading the EULA leads to it saying something like, we can do what we want when we want and you can suck it!

fiendiish said:
Here's what I found out. If you DO NOT HAVE GPS, EMAIL OR MMS PROBLEMS...THEN THE UPDATE MAY BRICK YOUR PHONE. THIS IS ATT AND SAMSUNGS RESPONSIBILITY AND THEY ARE GOING TO FIX IT.
Click to expand...
Click to collapse
Not sure if that's true. I have GPS issues (Even outside on a clear night it took more than five minutes for me to get a lock). My phone is bricked.
A new one is on the way. Should be here tomorrow.

Downgrading after new update? Also warranty and root/unlock questions

As a preface, I got the ATT one x a few days ago, so far I'm really happy with it, but would like to get rid of a bunch of the bloatware and want to get root.
So this morning I woke up to the update message. Now I read up on it the night before on these forums that I should wait to update if I want to root/etc, so naturally I don't want to update quite yet. But here's the problem. The message popped up so fast that I could barely read the message. My thumb must have been right above the accept button, since the message disappeared almost instantly and the process started up. I exited it as far as possible, and it seemed to work. I used apps on the phone, and everything seemed fine. As soon as I locked the phone again, it decided to reboot, initiating the update, all on its own. Even a forced power-off wouldn't stop the wheels turning. And now I feel like an idiot. So is there any way/what is the best way to downgrade or reverse the update?
TL;DR: I accidentally updated the new update, is there, and or what is the best way to downgrade so I can eventually root?
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
I know that with enough time I could find some of these answers on the forums, but because they are so lively, it's hard to keep track and sift through the forums for information. Thanks for your time and thank you in advance for your help.

In regards to the root on the update there is no way to downgrade or root given your situation at this time but hopefully one of the talented people here on xda wil find a new exploit like they did for the 1.85
As far as warranty goes someone else will.have to let you know.
Sent from my Nocturnalized Beast

same boat
I am in exactly the same boat. I didn't check the MD5 on a download of CR4.5 and it completed wiped my phone (SD Card as well). I was away from my laptop and had to wait days to get it back online. When I finally got it up and running, I was rooting through the one click and in checking the update, it updated to 2.20. So now I'm stuck.
I have my previous unlock token, but I'm not sure if that will do me any good. I don't want to do much until a new RUU becomes available.
misiek93 said:
As a preface, I got the ATT one x a few days ago, so far I'm really happy with it, but would like to get rid of a bunch of the bloatware and want to get root.
So this morning I woke up to the update message. Now I read up on it the night before on these forums that I should wait to update if I want to root/etc, so naturally I don't want to update quite yet. But here's the problem. The message popped up so fast that I could barely read the message. My thumb must have been right above the accept button, since the message disappeared almost instantly and the process started up. I exited it as far as possible, and it seemed to work. I used apps on the phone, and everything seemed fine. As soon as I locked the phone again, it decided to reboot, initiating the update, all on its own. Even a forced power-off wouldn't stop the wheels turning. And now I feel like an idiot. So is there any way/what is the best way to downgrade or reverse the update?
TL;DR: I accidentally updated the new update, is there, and or what is the best way to downgrade so I can eventually root?
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
I know that with enough time I could find some of these answers on the forums, but because they are so lively, it's hard to keep track and sift through the forums for information. Thanks for your time and thank you in advance for your help.
Click to expand...
Click to collapse

BB2DX said:
I am in exactly the same boat. I didn't check the MD5 on a download of CR4.5 and it completed wiped my phone (SD Card as well). I was away from my laptop and had to wait days to get it back online. When I finally got it up and running, I was rooting through the one click and in checking the update, it updated to 2.20. So now I'm stuck.
I have my previous unlock token, but I'm not sure if that will do me any good. I don't want to do much until a new RUU becomes available.
Click to expand...
Click to collapse
The ruu is out for the 2.20 on the HTC dev site
If you already have your unlock token you should be fine just run through the steps to unlock then root. Your still stuck with the new hboot so your previous nandroids will no longer work and you can no longer flash boot images from recovery.
Sent from my Nocturnalized Beast

misiek93 said:
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
Click to expand...
Click to collapse
Consensus seems to be that a warranty return to AT&T, they don't normally check for bootloader unlock at all. Technically, they can check, and void your warranty. But to this point, they don't seem to be. This is probably your safest bet. But that warranty is only one year.
Based on various reports by XDA users HTC seems to be much more strict about enforcing their own warranty terms. I would suggest going through AT&T rather than HTC.
For your AmEx warranty, I think that would be handled by AmEx (not AT&T). You should probably check through them, and see what the warranty terms our (might be handled by a 3rd party?). I think only someone that has had experience with the AmEx process could say for sure what would happen in this case. So maybe somebody will chime in.

redpoint73 said:
Consensus seems to be that a warranty return to AT&T, they don't normally check for bootloader unlock at all. Technically, they can check, and void your warranty. But to this point, they don't seem to be. This is probably your safest bet. But that warranty is only one year.
Based on various reports by XDA users HTC seems to be much more strict about enforcing their own warranty terms. I would suggest going through AT&T rather than HTC.
For your AmEx warranty, I think that would be handled by AmEx (not AT&T). You should probably check through them, and see what the warranty terms our (might be handled by a 3rd party?). I think only someone that has had experience with the AmEx process could say for sure what would happen in this case. So maybe somebody will chime in.
Click to expand...
Click to collapse
Amex is extremely lax. All they want is a copy of the original warranty and require doing the work at an authorized repair shop. Then they reimburse you, no questions asked.

GroovyGeek said:
Amex is extremely lax. All they want is a copy of the original warranty and require doing the work at an authorized repair shop. Then they reimburse you, no questions asked.
Click to expand...
Click to collapse
I kinda figured as much. They aren't in the business of fixing phones, so I guessed they either just farmed it out to a 3rd party company, or just paid up pretty easily. Credit cards (especially AmEx) also often cover things like lost luggage, travel insurance (cancelled flights, etc.) and I don't imagine they go through much hassle confirming that kind of thing either. They must figure that the extra business gained from offering their services (and yearly fees) outweighs the payouts they have to make.
Thanks for clarifying with your personal experience, probably useful to the OP.

[Q] Fido RAZR HD Jelly Bean Update ?

I recently picked up the phone but however had to send it to repair due to a constant rebooting issue (which much to my dismay i discovered a fix just a day after sending it). I believe it was sent to Future Tel and they re flashed my phone with a different version of ICS then my previous version. While I did not think much of this at the time it has recently become apparent that the current Jelly Bean roll out is only heading to phones with the system version 492002. However my phone is on 49003. Will my phone ever receive the ICS update and is Rogers/Fido aware of this? Is there any way be able to receive ICS without having to flash on new software and change system files. I have contacted Motorola support but they have not gotten back to me. I am very happy with the phone, however i would very much appreciate the new update. Any and all help is appreciated. Thanks.

genboxboy said:
I recently picked up the phone but however had to send it to repair due to a constant rebooting issue (which much to my dismay i discovered a fix just a day after sending it). I believe it was sent to Future Tel and they re flashed my phone with a different version of ICS then my previous version. While I did not think much of this at the time it has recently become apparent that the current Jelly Bean roll out is only heading to phones with the system version 492002. However my phone is on 49003. Will my phone ever receive the ICS update and is Rogers/Fido aware of this? Is there any way be able to receive ICS without having to flash on new software and change system files. I have contacted Motorola support but they have not gotten back to me. I am very happy with the phone, however i would very much appreciate the new update. Any and all help is appreciated. Thanks.
Click to expand...
Click to collapse
You're not the first person to report this issue... I believe the wrong firmware was loaded in the Motorola download program for a long time.
I just made a tutorial for this, maybe you want to try it out?
http://forum.xda-developers.com/showthread.php?p=38765124
Let me know how it works!
PS the firmware file you're looking for is here : http://sbf.droid-developers.org/van...12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
Rogers and Fido use the same firmware, but the phone is able to adapt based on which SIM is installed.

Thanks for the help. Quick question though, will flashing new software on make me loose my warranty and also does it require root access ? I have a feeling a gut feeling that i may brick my phone during this as this was the reason i had to send it to repair in the first place .
I recently wrote to Motorola about this and they responded with "Thanks for reaching out to Motorola. I have reviewed your e-mail, and I am ready to help. I apologize for the delay and any inconveniences you're experiencing. Please note that Motorola stands behind our products by offering one year warranty from the date of purchase. This warranty does not cover physical or liquid damage. Based on your email, we recommend sending the phone to Motorola to be reflash with the Jelly Bean software update. Please drop the phone along with a copy of the proof of purchase off at your local service carrier store, so that it can be shipped to Motorola centre for repair , and return within 5-7 business days from when we receive it. If the phone is determined to have suffered physical or liquid damage and deemed not repairable, it will be shipped back to you unrepaired." along with a bunch of other info on getting my phone to repair. I will probably just wait a bit to make my decision. Thanks anyways.

genboxboy said:
Thanks for the help. Quick question though, will flashing new software on make me loose my warranty and also does it require root access ? I have a feeling a gut feeling that i may brick my phone during this as this was the reason i had to send it to repair in the first place .
I recently wrote to Motorola about this and they responded with "Thanks for reaching out to Motorola. I have reviewed your e-mail, and I am ready to help. I apologize for the delay and any inconveniences you're experiencing. Please note that Motorola stands behind our products by offering one year warranty from the date of purchase. This warranty does not cover physical or liquid damage. Based on your email, we recommend sending the phone to Motorola to be reflash with the Jelly Bean software update. Please drop the phone along with a copy of the proof of purchase off at your local service carrier store, so that it can be shipped to Motorola centre for repair , and return within 5-7 business days from when we receive it. If the phone is determined to have suffered physical or liquid damage and deemed not repairable, it will be shipped back to you unrepaired." along with a bunch of other info on getting my phone to repair. I will probably just wait a bit to make my decision. Thanks anyways.
Click to expand...
Click to collapse
My tutorial doesn't require root, and will not void the warranty on your phone, in fact it is almost the same process that Motorola uses when repairing your phone. If you have any questions, please let me know.
Sent from my Nexus 7 using Tapatalk HD

Unlocking bootloader status??

It this something that the experts will eventually be able to do on the Galasxy III and 4.3 ?? It's a Verizon phone, BTW.
I went down to the V store to demand they put it back since the 4.3 upgrade broke so many things and they refused. Claimed that it was not possible. I replied "BS, you and I both know that if V wanted to do it, it'd be done in a second. V just doesn't WANT to do it".
I know you guys are working on it, just wondering if it will actually be "do-able".
V blamed it all on Samsung and washed their hand of it. That leaves another thought.
Is it really Sammy's fault and if so, would another phone manufacturer may be more "accommodating" to those of us that might want to mod our device?? I really don't want/need a custom ROM, just put it back to 4.1 stock.
Right now I'm pretty PO'ed at Verizon. Supposedly they were forced by the US Feds to NOT block WIFI tethering on "data limited" plans. However, the guy at the V store pretty much just laughed in my face, even though I have a 2GB limit.
Boowho??

Small Update Is Out

It does not change ver. from 4.1.2

what does this updatedo?
What does this update do? Does it affect my root? Thanks!

It is notifying me too. Since I have twrp and root on stock jelly bean, how can I update if helpful, or turn off update notification?
Chad
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

AFwarbird said:
It is notifying me too. Since I have twrp and root on stock jelly bean, how can I update if helpful, or turn off update notification?
Chad
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Started getting the notification yesterday, but I'm also on stock Jelly Bean 4.1.2 and TWRP. I was able to stop the notifications by freezing "AT&T Sofware Update" with Titanium Backup, but I'd also like to know if there's anything here worth the trouble of trying to get it installed.

I just had a chat session with a Samsung official, and she said it's news to them. I told her that I am on I727UCMC1, and she said that my device is up to date. The small update AT&T is pushing must be something to do with AT&T.
Unless it updates my camera features, I'm not even bothering with it, and will keep AT&T Update frozen.
I'm pretty sure I'd have to backup everything, revert to stock UCMC1, cross my fingers and toes that it still doesn't brick my phone, and hope it still can be rooted the way I did before.

It sure would be nice if there was some sort of explanation as to what is being updated. I have looked all over and not found anything anywhere else that mentions this update to I727UCNJ1. I got the number from this an at&t website I would post the link but can't. It is only 12mb so probably not worth a bunch of trouble but I wish I knew what it is trying to update.

Paranoid?
Me too. Mine is original stock, but I upgraded the Android OS last year to 4.1.2 via Samsung Kies. However, mine is unlocked, and I can't help but be suspicious that AT&T is "updating" to do something that is to their benefit and not ours (i.e. relocking the phone?, spyware, etc.?), so it would be nice to have some details of what/why this unexpected update, before blindly agreeing to it. So, if anyone know what this update is all about, please share with us. Thanks very much!

My money's on an update that locks the phone down. What else would AT&T possibly do with a three-year-old platform that isn't making them any new money at this point?

I chatted with an AT&T representative yesterday, and all I could get out of her was that the update had to do with new features to the O/S. That's all the information that she could find, and couldn't tell me any specifics about what features were being updated.
I am about to go to an S5 or S5 Active soon, and I might just revert to stock to check it out.
It's pretty fishy though that neither Samsung, or AT&T has, or wants to divulge in any, information on exactly what it's going to do.
---------- Post added at 07:29 PM ---------- Previous post was at 07:26 PM ----------
As far as it locking your device back down, I have yet to flash, or install anything that has re-locked my phone. I guess it's possible. The only thing I'm worried about is losing root, and not being able to get it back with the last way that's available.

I see it's now listed on the AT&T eSupport website No details, just "Android OS Enhancements".
I don't have enough posts on this forum to be permitted to publish a link, but you can find it by Googling "AT&T Update to Skyrocket", and the eSupport link should be near the top of the results.

AT&T is taking the same tack as Verizon, and locking everything down. Even the mid to low end phones. So, I wouldn't be surprised if this is a way to lock older phones.
On the other hand, it really may be final bug fixes - a sort of final service pack. I wish I trusted them to give it a try.

I reverted back to stock I727UCMC1 using Odin v1.85, updated OTA to I727UCNJ1, flashed TWRP custom recovery, got root back, but I am not sure if I am still unlocked or not. I tried *#7465625# on the dialer, but the code does nothing.
Anyone know of another code to check the unlock status?

Thanks very much for your feedback. I've always just put a SIM card from another carrier into my phone. Even if it is not an active SIM, your phone should still tell you whether or not it is locked.

24fan4life said:
I reverted back to stock I727UCMC1 using Odin v1.85, updated OTA to I727UCNJ1, flashed TWRP custom recovery, got root back, but I am not sure if I am still unlocked or not. I tried *#7465625# on the dialer, but the code does nothing.
Anyone know of another code to check the unlock status?
Click to expand...
Click to collapse
unless u restored a previous efs partition that was locked to a carrier then u will remain unlocked, afaik no one lost their unlocked sim by restoring or flashing any firmwares, to read more about the sim lock or to unlock the sim read this http://forum.xda-developers.com/showthread.php?t=2638037
as for firmwares locking down the phone its referring to the way root is acheived not to the sim carrier lock

T.J. Bender said:
My money's on an update that locks the phone down. What else would AT&T possibly do with a three-year-old platform that isn't making them any new money at this point?
Click to expand...
Click to collapse
i hope you are joking, because if not then then you're insane. no offense intended.

Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices. Several devices started out unlocked, like the S2, and became locked by OTA updates. The S3, Note 2, etc.
IOW, I wouldn't put it past them, especially if Samsung wasn't aware of the update. On the flip side, the S2 is no longer even for sale, and I have to wonder how many are left in active service.

Clarification?
lingowistico said:
i hope you are joking, because if not then then you're insane. no offense intended.
Click to expand...
Click to collapse
Thanks, that was very helpful! Seriously though, as a senior member of this forum, perhaps you might have some constructive comments on this subject? After all, we're sitting here with phones (the I-727 SII Skyrocket is an oldie, but goodie!) that are trying to push an unanticipated OTA update on us, in a very suspicious manner. We hope it's just a bug fix, but don't trust the carrier (AT&T) to be doing this, unless they have some ulterior motive. The benefit of your substantial experience would be appreciated. Thanks in advance for any insight you can offer us.
Regards,
Ron M.
jshamlet said:
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices. Several devices started out unlocked, like the S2, and became locked by OTA updates. The S3, Note 2, etc.
IOW, I wouldn't put it past them, especially if Samsung wasn't aware of the update. On the flip side, the S2 is no longer even for sale, and I have to wonder how many are left in active service.
Click to expand...
Click to collapse
Thank you for your insight, it was TRULY helpful! As a relative newbie, I just want to clarify our terms. When you use the term "unlocked", I deduce you are referring to a phone that has been rooted and is running a different platform - is that correct? In my case, I am NOT rooted and simply running the original crappy stock platform, but my phone is "unlocked" in the traditional sense, in that I can use it with different sims from different carriers throughout the world, rather than being "locked" to AT&T. So, for those of us who are not as technically advanced, could you please clarify? For me, if this OTA update doesn't prevent me from continuing to use other sims from other carriers, then I don't know what the downside would be, unless they're just adding more spyware and bloatware to their already intrusive system? I look forward to your comments.
Regards,
Ron M.

jshamlet said:
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices.
Click to expand...
Click to collapse
I thought T.J. Bender was talking about simlock since he didn't mention the bootloader. :silly:
At&t sure isn't making life easy for you.. I'd still be proudly rocking a skyrocket too if I didn't lose it :angel:

I only messed with my Skyrocket for an hour or so after accepting the OTA update, before starting up my new S 5 Active.
The only thing that I really noticed, was they took the AT&T phone setup app off of it, since it is no longer in use by AT&T. There may have been more that I didn't notice, but only running it a couple hours, I couldn't tell. I even checked the camera thinking they might have finally snuck some new features into it, but no dice.

lingowistico said:
i hope you are joking, because if not then then you're insane. no offense intended.
Click to expand...
Click to collapse
How does suggesting that AT&T would lock a bootloader make me insane?
Sent from my totally badass HTC One m8 using Tapatalk