All replies
-
According to this page:
Samsung Mobile Security
the Samsung S9 is supposed to be getting monthly Android security updates from Samsung. And if you want to know how important that this is to you, click on the "Details" tab and you'll see the long list of security fixes for each month.
From this, I'm concluding that T-Mobile is the bottleneck for these updates getting to us, since T-Mobile is supposed to be getting monthly updates from Samsung. So where are they?
Not sure what I'm going to do at this point. I like my Samsung S9 and I like T-Mobile, but I really don't like this situation.
-
I feel your pain. I have a Galaxy Note 8 and not only have I not received Oreo, I haven't received a security update since January! If you check Android's security update page, it shows that Samsung does roll out monthly updates, so I think T-Mobile is to blame. This is really frustrating and I recommend getting your phone unlocked - straight from the Samsung website. At least then you get the update when Samsung rolls it out and not T-Mobile.
-
I’ve got about 20 days before I can unlock my phone, but it that looks like the right answer at the moment. Funny thing, I pre-ordered an unlocked S9 directly from Samsung, then cancelled it to get a T-Mobile S9 because I read that the unlocked phones didn’t get updated. Now I’m seeing the exact opposite. So it goes...
I’m going to do my due diligence and then decide where to go from there.
Thanks.
-
-
Hi mrdoh,
The Samsung S9 was released on March 16, so the S9 wouldn't receive a February or March security update because the launch occurred after the security releases. The release software should have those security vulnerabilities covered in the version at launch. The April security update was just released by Samsung on April 2, I believe. From there it takes up to two weeks to turn around the security patch due to optimizing the OS build for on network performance based on carrier settings. Unless some flaw is discovered (which happens) and it is kicked back to Samsung, I suspect you'll see the first security update for the S9 in the next week or so. You'll be able to track when the security patch becomes available for the S9 here: Software updates: Samsung Galaxy S9
Hi Themax123,
I have the Note8, and it has been receiving regular updates. Oreo was pushed from T-Mobile to Note8 users on April 2. Since you're replying on April 7, I suspect you have your automatic software updates turned off. I recommend you turn them on. You won't get a notification that a new software update is available with it turned off. Unless you remember to go in and do a manual check around the 15th of every month you're not going to know when updates are available. You can find the Note8 software version release history for the T-Mobile Note8 here: Software updates: Samsung Galaxy Note8.
-
Okay, here are my expectations for monthly Android security updates...by the way, my last phone was a Pixel, so I know how and when these updates are delivered. Monthly. When I got my S9, there was an update waiting which I applied. My S9 is now at Feb. 1 security update level as a result of applying that update. There should also be a security updated dated Mar. 1 and Apr. 1. Neither of these has been delivered. It may be early for the update dated "Apr. 1", but it is late for the update dated "Mar. 1".
I did look into this on the web in the Samsung security updates pages and found that Samsung has skipped 2 months of security updates following the one that was dated Feb. 1 (security updates for January). Which would be the Android security updates for February and March. If Samsung doesn't pass along the monthly Android security updates, then we don't see them (of course).
My hope is that Samsung has not gone to a quarterly update model. My research showed before I bought the S9, that they were committed to monthly security updates. I'm not sure that seeing quarterly updates would have stopped me from buying the S9, since I was looking for both "bezel-less" and band 71 support, which is the S9...I didn't want the LG V30. But I would have known what I was getting into up front, which is a good thing.
-
Hey there mrdoh,
I wanted to follow up with you regarding software updates for your S9. I did some more research for you. I was wrong in my assumption that the March security pack was included in the launch software. I have good news though! The March security pack was approved last night, my team updated our content which is live now in the S9 and S9+ spaces. We are launching the March security update tonight around 10 PM PT. Depending on the amount of customers with devices it may take a while for the system to push the OTA out to everyone, so be patient if you don't get it right away.
On the topic of Software Updates across all the carriers, AT&T launched their March security update on 3/31, Verizon and Sprint haven't launched theirs yet. In case you want to verify my sources, I got them directly from those carriers. Here are the links if you're interested:
Verizon - Samsung Galaxy S9 Software Update | Verizon Wireless
The S9 and S9+ are on Samsung's monthly updates list so your concern about quarterly updates should get resolved. It looks like everyone is behind. I know we have plans to catch up as rapidly as possible here at T-Mobile. Looks like it's a race! I know I'm betting T-Mobile wins. We have a pretty awesome team working on this stuff, and we take our customers security very seriously.
We appreciate you here at T-Mobile. Let us know if there are any other concerns we can help with.
-
Well, thanks very much for the update! Much appreciated. Like the news about monthly updates, makes me happy *smile*.
Thanks again!
-
Sorry, but the "whataboutism" of this post is too much. I don't care about what Verizon and Sprint, or any other carrier has or hasn't done. I care about T-Mobile and what updates I'm going to get from them. As far as I'm concerned, it's May. Pixels and even the Essential Phone, a phone that has no affiliation with Google, has the May security patch, and the S9/+ status on T-Mobile is that the March patch has been pulled due to issues with the update.
So, like I said, it's now May, and T-Mobile S9s are stuck on the February security patch, going on 3 months old at this point.
Samsung promised monthly security updates for the flagship phones, S9 included. We're 3 months late and no one to answer for it. Neither Samsung, nor T-Mobile. I want information on how we can get faster updates.
And please don't give me stock answers like "we need to test updates" or "talk to samsung." There's always an answer to fixing these problems, and if that means T-Mobile or Samsung needs to take a monetary hit to achieve the things that were originally promised *before* people bought these devices, then that's what you have to do.
-
Okay, almost the end of May, and my T-Mobile Samsung S9 phone still has the "March 1" updates.
How about "April 1"? Is that ever coming? I'm pretty frustrated at this point. Samsung promises monthly updates, T-Mobile (see tmo_nic posting above) promises that the updates are coming.
So when are they coming? Can't wait until the next generation (3) of Pixel phones comes out, looks like i may well be going there. Google delivers their Android security updates monthly as they promise. Samsung and T-Mobile seem to be big on promises, short on delivery.
-
-
-
-
Well its June 7th and we are STILL on the February security patch T-Mobile. Reading the responses from the moderators just makes me laugh. Verizon got the patch for May. Is it time to leave you guys and take the 4 lines I pay for every month along with me because by keeping us in the dark about any serious issue preventing your customers from receiving security patches with a major flagship device leaves very little room for trust and you've already lost my respect At this point in time we deserve a detailed explanation of what has clearly went wrong. No more scripted excuses. This is very bad.
-
Agreed, this very bad. Sad to hear that Verizon is doing better, I guess that’s where I belong, too. Been checking every day for a security update from T-Mobile...I’ve read about the many fixed security exploits in the updates that we’re missing. I’ll be looking into other cellular providers. Disappointing! Especially since I got the S9 specifically because of band 71 coverage. An expensive mistake on my part.
-
What did the tmo_nic guy say about a 2 week turnaround with Samsung? It's almost the middle of June and the S9 and S9+ are on February security patches. I noticed they abandoned this "answered" question once the May and June comments started sprouting up. TMobile and Samsung are so lucky most people are ignorant when it comes to how important these patches are. It's in the news now though.
-
Hi Landeus,
Who's abandoned the post? Not this guy...
It's important to get these things right. I don't know what the hang up is, but if every carrier in the US holds updates for months it's a pretty strong indicator that something very important was discovered and is being scrutinized thoroughly. This is the most popular selling device in the world, which stands to impact the most people if something happens.
We appreciate your patience, and understanding.
-
Then, as the interface between us and Samsung (who refuses to give us information), it's up to T-Mobile to push for these things for us. It's not good enough to just throw your hands up and feign ignorance.
>We appreciate your patients, and understanding.
And we appreciate a bit of proofreading.
-
I agree, T-Mobile owes it to their customers to get these updates to us, and to keep us informed about what's going on if there are problems. Especially as far behind as T-Mobile has been all along. You can help your customers be more patient if they're informed and know that they're waiting for a reason, not just because T-Mobile doesn't intend to pass along any more updates. Without communication from T-Mobile, there's no difference to the user between T-Mobile just not feeling like passing along the updates, or there actually being a reason why they're not doing that. At this point, I'm not feeling that T-Mobile gives a fig about these updates. I do.
I have read that Verizon (at least) is able to pass along the updates for the S9, so this isn't "all carriers". And I hate to read that Verizon users are getting updates, while all that we're getting is silence in lieu of updates. Don't know if I've said it here, but the Pixel 3 or the next round of iPhones are going to get all of my attention. And if T-Mobile doesn't deliver the updates for the Pixel 3 (assuming that they don't come directly from Google), then no more T-Mobile, as well.
I really like the S9, and T-Mobile is okay in general, too, but I'd like both a lot better if I felt that I had a secure phone. Lots of security exploits in the Samsung bulletins that go along with these updates...
Personally, I'll keep trying to communicate my dissatisfaction with T-Mobile about this, but I'll only do that for so long. Then I'll take my business elsewhere.
-
Hi Mr. Doh,
I appreciate your more professional approach to the conversation. We don't just throw our hands up and wave 'em like we just don't care.
T-Mobile isn't going to produce a sub-par product. If other carriers wish to do so that is their prerogative. We also aren't going to advertise why updates aren't being rolled out as the result is making those who shall not be named aware of additional things to exploit that they may not have been aware of previously. In this case, as in many others in life, a lack of information keeps people safer. I know that's not the answer you want to hear, but, we're going to operate from the position of having the responsibility of needing to protect millions of people (because we do).
We appreciate your patience, and understanding.
-
That's a pretty poor defense. You don't have to give any *details* of what the update is delayed, a simple "we're working on it, but there was a flaw discovered that needs to be addressed" would definitely suffice with trying to appease customers. Hiding behind "security" doesn't help anyone.
-
I have gone back to using my iPhone 8...I didn't mention that, but I feel that the security updates are put out for a reason, and if I'm not getting them, then I'm not using that phone. Pretty close to being a quarter behind at this point, which is worse than I'm willing to live with.
As has been said, you don't have to discuss the specific issues when communicating, just that you're still working on it, and a possible ETA if one's available. For example, if you've encountered a boot loop when an update is applied that is tough to fix, you can say that, that doesn't tell a hacker anything that they can use. I agree that you don't want to discuss specifics with security issues, but for heaven's sake, once Samsung issues their bulletin with all the vulnerabilities that are fixed, you could say that the cat's out of the bag. And a hacker can find out what the security update level of a T-Mobile S9 is pretty easily.
Anyways, I don't find "security by obscurity" to be the issue here, it's more like allowing customers to make informed decisions about their futures. If you don't keep us informed, we'll wander off, I guarantee it *smile*. May do that anyways, but one might stay around longer if there's an end in sight.
-
I do understand where you're coming from MrDoh. There have been extenuating circumstances that have prevented the security updates from rolling out as advertised. When I first engaged with you the solution seemed very imminent. I was also under the impression I would receive notifications, so I focused on other things. I was unaware responses were being sent to the dreaded pit of despair. As it turns out, additional things were found, and it's been delayed... ALOT. I would have engaged sooner had I realized. My apologies. I've changed my notification preferences to make sure things I engage on are no longer routed to the pit. Let's not blame the Support team. They're incredible people. I'm working to give better communication around Software Updates. This large wrinkle has given us some things we need to figure out.
At this point, I'm a bit hesitant to provide much more than, "We are very aware of how critical this is and we are working on it as quickly as possible." I've set a calendar reminder to check back on 6/15. Hopefully I'll have an update.
-
Thank you nic for at least saying as much as your allowed to say. The short "we will be with you as soon as Haiti freezes over so keep on checking the update website to see that it hasn't changed " you know, stuff that T-Mobile and Samsung love to throw at us because we're morons... (btw, everyone making comments here who doesnt work for T-Mobile is a very informed, very concerned, and highly intelligent individual in regards to understanding soke degree of software development, the securiry patches, software updates, etc... which is the main reason short answers are extreamely insulting...) so thanks. However, similar to a comment someone else on here said about dumping Tmobile and leaving, I'm right there with them. Say by some miracle we get a security update (say mid June) after waiting so long and we do not begin to receive *monthly* updates, I'm gone along with the $200+ I shove into T-mobile's enormous mouth every month. All 4 lines plus the watch (5 lines?) will be dropped and I will go some to anyone else whom during the same time period managed to get regular monthly updates. I will happily pay off any EIP and drop tmo like a stone. The atrocious new T-Mobile app alone is enough for me to consider leaving lol. It tells me something about what might be in charge of software development and that's scary. I hope our security isn't being sacrificed due to some issue with the new bands nobody is using anyway yet. Smh in shame.
-
You're welcome, Landeus.
I really appreciate you and Mr. Doh forging that delicate balance between frustration and communication. It's very helpful. We have a strong Support team on these forums, and they're incredible. However, we also have a lot of other people paying attention. Most prefer to lurk but some of us are a little more comfortable on a forum. I think some of the more difficult responses are a barrier to entry for most, because let's face it, this is very public. Hopefully over time people will realize T-Mobile is truly different than other carriers. I think they'd be surprised if they were aware who in the company leverage this Support community to drive improvement and amplify issues on the regular. So coming full circle, thanks! Your approach is to be applauded. I hope more follow your lead. It helps.
As for people jumping ship, I hope not. I also hope my participation (or gap in) hasn't irritating an open wound. I completely admit I dropped the ball in my follow up. I won't make that mistake again. Hopefully, most of you can forgive my 'live & learn' moment. I, and others, do listen to how Software Updates are going across all OEMs. We leverage your voices to emphasize the impact these things have. If you can't hang around, and you need to jump to protect yourself and the three other users on your account, I understand. I might not like it, but, I get it. As of right now I'll be checking back on Friday, and setting a regular touch base going forward.
TTYS!
-
tmo_nic, apppreciate your sincerity and re-dedication to keeping us poor users informed *smile*. Hopefully there will be news in a couple of days, and hoping that it will be good news, as well.
Hang in there, we're all counting on you *smile*.
-
By jumping ship, i meant in my case moving over the the iPhone X. Don't get me wrong i love T-mobile as a whole. You have great prices and JOD is something i would never give up by switching to another carrier. But pros of the iPhone are there is little to no intervention in regards to software updates. And Apple is very forth coming in informing about updates. I mean look how far out we are from iOS 12 and thats an update iPhone users can expect in September not 6-12 months after release. Its not just a T-Mobile issue Samsung treats the US like crap in regards to software be it unlocked or carrier. But i do believe that words have no impact on an outcome for this particular issue of MIA updates. When T-mobile stops selling Samsung products to people because they hear how badly the support is, Samsung will listen because nothing gets attention more then the topic of making money lol. So i apologize my other response was in fact harsh but please consider how we feel on the consumer side of this wall.
-
-
-
-
-
-
-
-
-
-
Ok well first off T-Mobile Support RUDE AF . Secondly do you realize WE paid or are paying for a phone ergo a service FROM T-Mobile? The "I Don't Know Whats Wrong" is utter garbage. It's BEEN 61 DAYS since the march patch was pulled. If there is a problem so severe that they can not seem to correct it with any builds that have been compiled then T-Mobile needs to be forth coming with such information. You are treating your customers as if we are moronic little white snowflakes. Tell us the truth so WE can make an informed decision weather to give up hope and find a new phone/carrier or tell us that there is something in the works. If we don't get anything by the end of June we should just pull the plug on this nightmare and move on.
-
Btw: Just got finished talking with Samsung... again... and they told me that they released a patch to all carriers and it will be pushed to us in batches. ASAP! This was not the usual response. ( yes, I'm hounding them as well, and with more hatred than with you T-Mobile)
I asked what the baseband was and it was
LOL...
G965USQU1ARBI which BTW is the AT&T baseband with the February patch! I told them that and they said " well it will be G965USQU1ARC6 for T-Mobile". I LITERALLY had to explain to Samsung that the baseband they were referencing is the one we had released and then put on "hold" back in April. They have no clue!!! So T-Mobile, I don't have much faith in believing a patch is on the way, I think you're in the dark, or perhaps both companies are insane. AT&T and T-Mobile are the only 2 major GSM networks in the US that I'm aware of and both of them have these US Snapdragon variants with some kind of impossible to fix issue, 132 days since the Feb patch released, I'm done here. I'm selling this piece of trash to someone dumb enough to buy it. It's in perfect condition so I should have no problem. Cheers! And good luck!
-
After a career in the software industry, my experience is that most anything can be fixed via software (other than exploding batteries, of course), given the right team working on it. While I'm not using the S9 at the moment, I'm not ready to dump it quite yet, a carrier change might be in order, though. My wife's on Verizon, I can join her for about $20/month. As a result of your posting, I will take a serious look at what other carriers are doing with their S9. The fact that Samsung has released the bulletins for the Android updates through the June one tells me that T-Mobile has some catch-up to do, not that it's impossible to do, not yet. I've learned not to panic about these things, I'll do that later on *smile*.
But each to their own. I do like the iPhone 8. Bought it when it came out, at least partly because I knew that Apple would support it, and it's fast and comfortable. Then bought the S9 when it came out for the larger screen on an iPhone sized phone. And the promise of the monthly Android updates that I got on the Nexus 6P and Pixel phones that I had. Every month directly from Google, around the 5th of the month *smile*. Oh yeah, and band 71 on the S9, an investment in T-Mobile on my part.
Anyways, I'm planning to exercise some patience while enjoying using the iPhone. I'll panic later on *smile*.
Update: Verizon has the 5/1/2018 update available for the S9. So at this point, it seems that Verizon is doing a better job of supporting the S9. T-Mobile can do it, too, if they really work on it.
-
-
I'll just leave this here
Samsung Galaxy S9+ Software Update | Verizon Wireless
Even if T-Mobile wants to play catch-up and releases the June patch, this does not absolve anything. We need *consistent* *monthly* security patches.
-
Well that's a punch in the gut..... Two updates in like a week.
-
Just google searching " samsung galaxy s9 security patch " I found 3 new articles written today about this issue alone. Shameful.
-
Looks like Verizon is the place for a Samsung S9 owner to be. Too bad.
-
-
-
-
I just got off the phone with Samsung. I'm being told by their senior tech (basically, the guy next to the girl I spoke to) and they told me I would have to contact Google because they have no control over the updates which is a lie. So if you were hoping to get an update on June 16th ... Samsung says they don't have anything for us. They are waiting for Google. Maybe just another bad couple of lying reps that are clueless but there's no way I'm contacting google LOL!!! T-Mobile, out with it. Tired of the blame game circle. This one was so ridiculous that I'm sending it in to any and every person who wrote an article about this issue. They could get away with it pre-project treble but this year they are gonna really get it hard.
-
This guy wrote a very good article that's simple and to the point...and they keep coming!!! 3 new articles today alone that I've seen! Unfortunately he doesn't mention that the Unlocked S9+ also hasn't received any security updates either. I can't wait til this goes mainstream. Too many articles to ignore this year due to companies like Samsung who think Project Treble isn't important and expect us to believe it's Googles fault they aren't on the ball. Sammy is gonna be center stage for the public shaming and I CAN'T WAIT!!! LOL!!!
https://wccftech.com/unlocked-samsung-galaxy-s9-hasnt-received-a-single-security-patch-since-its-release-in-the-us/amp/ -
Just look at a simple search on google now...
-
1 of 1 people found this helpful
To those following this thread:
We won't be rolling it out over the weekend. Given the history, I'm sure you can all understand our desire to have all hands on deck. However, pending nothing new pops up in testing all security patches will be caught up through June, soon.
A couple of house cleaning items.
First: We don't open up downloading for everyone getting the update in one sitting. We don't want to black screen of death, or boot loop, millions of users all at the same time if something slips by. The amount allowed each day is dependent on several factors, but we typically see around 5% push (Auto Update) and allow up to around 5% pull (Manual Software Download) day one and increase allotment as we go. If our content here on Support says an update is available, but you can't pull it down, chances are the daily allotment has been reached. Try back the next day. Mmk? After a couple days of 'no news is good news' the flood gates open and everyone is brought into the light.
Second: We typically launch the updates very early in the morning. That way those of you who receive Auto Updates get the update while you're sleeping and there's little impact. This is a pretty typical practice used by others like Windows, Xbox, Play Station, etc. If you don't have Auto Updates turned on, and you wake up at 9 am PT, chances are those on the East Coast gobbled up the Manual Update slots for the day. Please don't ask how the system prioritizes 'push' updates. I don't know. So... Either be awake at 2-3 am PT and spam the manual download option, or turn on auto updates and try each day once it's available. Not having auto update turned on reduces your chances of getting it sooner since you aren't available for the push event. I hope that makes sense.
-
That's great to hear thanks for giving us a bit of hope. I hope nothing stops this rollout!
-
I've been lurking on this, and every other Galaxy S9 update thread I could find, and registered just to say THANK YOU, THANK YOU, THANK YOU, tmo_nic! You don't know how much those of us that have been seeking information and answers on the lack of S9 updates appreciates your transparency and willingness to actively communicate with customers! Your posts, and all the follow up you have provided is greatly appreciated!
I'm also glad, (as I'm sure others here are too) to hear that barring any major catastrophes the June update shouldn't be too far away.
Thanks again!
-
Curious Nic, now was that post supposed to mean that there IS an update getting released this week, that maybe this time around its looking like a release is underway, or was it just a means of pacifying us? With an unlocked variant I don't even know if I'm able to get any update from you regardless. However, if Samsung is really going by some rule that once all of the carriers have certified/approved an update only then will those of us with unlocked variants will get updated, it puts us one step closer to getting something. Since all we are asking for are security patches and the only two major GSM carriers ar still stuck on February patches while the CDMA variants are doing fine, it has me thinking something is wrong with these phones on networks that are primarily GSM. We would all be on the same variants as Europe with the Exxynos chips (all of which are getting updated) if it weren't for the CDMA carriers here. Correct me if I'm wrong. After reading this...
... I can't help but wonder what is wrong with our phones.
-
>it has me thinking something is wrong with these phones
I have the same feeling. Looks like something prevent updates and Samsung just can't find how to fix it.
-
Once after it's been 6 months and no updates, Samsung will have to come clean with it and it won't be pretty. Yeah, it took a while on the CDMA networks but they have updates now. Snapdragon variant was made for them so that makes sense. Exxynos variants seem to be doing fine in GSM-ville planet earth. So It makes no sense at all unless you consider a hardware issue in the U/U1 variants. Bootloops in April, a temporary hold for 2 months on Tmobile, it smells broken. Samsung has some crazy long threads on this problem. They really have no answer either. They're hiding something and either tmobile or At&t need to force them to come clean. Murphys law here.
-
-
-
Alcms razor I meant lol
-
Think of it this way, At&t doesn't have to worry about newly acquired bands, nothing special. These phones are made to support bloat etc... it's the fact that Samsung is playing dumb, tmobile and At&t both have to have their best teams on this and nothing has come out... before pushing us an update thats a patchwork of bandaids and boogers, if they have any soul at all, they'll out Samsung. Expect something fun in the news. Over and out.
-
I really don't care about the patches anymore for this phone, I don't expect them. I'll use another phone. What I want now is Samsung getting forced to answer. Ok, now I'm done.
-
"We won't be rolling it out over the weekend. Given the history, I'm sure you can all understand our desire to have all hands on deck. However, pending nothing new pops up in testing all security patches will be caught up through June, soon."
I think we were trolled lol. The S8/S8+ got June this week so I'm thinking this is what he was referring too lmao.
-
This is funny. Here is an example of how people out there get really misinformed about a firmware release just because they don't know how important a single odd digit is when looking at a the baseband... tell me if you spot the discrepancies LOL!
Hint: There's a 5 where a 6 should be if the article were true..., but there's a 9 where an 8 should be because the article is wrong!
See it? lol , smh.
-
-
Yeah it was just to shut us up for a while. Time to get back to it. Samsung just told me again that the updates go direct from Google to the carriers. I don't believe anything they say either , But if they have been sending updates to T-Mobile and T-Mobile along with AT&T are unable to get these phones working, we need to know something. I want to know so I can sell this phone, So that I'm not walking around with a device riddled security holes. Samsung, Google, T-Mobile, AT&T, whoever they've all had ample time to get these devices up-to-date but apparently because of some kind of flaw, these devices cannot be updated.
-
Hi Everyone,
Tonight at 10 p.m. PT the update will roll out. We're in the process of updating our content to reflect that both the S9 and S9+ June security patch.
In response to the previous comment, Landeus, I don't placate or pacify people. I was serious when I said it was coming. Just needed to hold my tongue for a day or two longer while we confirmed testing.
Best regard, all.
-
Are you sure the update sizes listed on the S9+ page are correct? Seems like a very small jump from RC6 -> RF4 (175.56MB) on the S9+. Where as the jump from RC6 -> RF4 (561.75MB) on the S9 is so big?
-
Yep, I'm sure. Checked a couple times to be sure. Doesn't happen often, but it does happen.
-
Are you able to provide details as to what was updated on both the S9 and S9+. On my S9, received the 748.77 MB update (RBG to RF4). It's got to be more than just security updates at that size??
Cheers
-
-
-
Finally, the update was released and already installed....
BUT..... the update messed the camera app. When switching the modes, you can hear the camera sounds of switching the aperture or the second camera. The slow mode option displays the camera/screen completely dark....
Great job again Samsung / Tmobile. Another update that will be placed on hold
-
Sorry to say, but, it appears to be just you so far Bluefire25.
Basic troubleshooting after a security update is to perform a Wipe Cache Partition (least invasive solution) which has an incredibly high success rate of resolving issues. If that doesn't work then a Master Reset (most invasive) will increase your success rate. Some times the update gets corrupted during download and requires an exchange (Very rare - but it has happened).
The typical reason these issues impact people intermittently is existing Apps store file locations or names (cached) to speed up their boot sequence. When those files move, change names, etc. as a result of the update the Cache is looking for something that either moved, or doesn't exist any more. These cache issues don't always prevent the device from booting depending on whether they are critical to device boot. Wiping the Cache Partition / Master Reset will force the device to dump the old data, find the new data, and cache it again.
I'm not saying there's isn't a problem, but, my S9 and S9+ are working, I've checked with several others who have the devices with various third party software who all got the update without issue. In addition, we have a method for issues to be sent up the chain internally. No reported issues at this time. If after those troubleshooting steps you still have an issue please call for further support.
-
Will those of us with the unlocked US versions get this update too and if so when?
-
I never got the update because, like you, mine is unlocked. So... I used Odin. It’s the only way and Inteust XDA about as much as I trust T-Mobile and way more than Samsung. Samsung, they’re a hot mess. They have the worst customer service and honestly, other than the nice build and screen on this S9+, the camera is way over hyped (I literally prefer my 4 year old LG to this when it comes to pictures), the software and support has been atrocious. My last Samsung ever. Maybe now that the main 4 carriers have updated at least once, I think, perhaps in a few weeks to a month there will be an update for the unlocked. Cheers!
-
Hi, how did you find a download for the SM-G965u1. All I saw was for the cellular network, not specifically US unlocked. Did the update go smoothly using Odin and does everything still work like it should? I do have the S9+. This is my first Samsung Phone and it will be my last...……...
-
I went to Updato and found the ARBG baseband firmware that would've been the T-Mobile version of what my SM-G965U1 was running. It might have been the release version since Samsung did send out an update with the same baseband and same February patch early on that fixed some bug with the camera i think. Well, anyway, I got Odin from XDA and replaced the SM-G965U1 firmware with the SM-G965U (TMB). It actually changed made the model number a U and not s U1 which I didnt expect. Thinking I had done the trick, I tried OTA to see if anything would come show up... nothing did, I don't know why or if it will ever work. So next I hooked the phone up to Smartswitch and finally I saw the "update available" message show up on my laptop. I let Smartswitch do its thing and I now have ARF4 with the June patch. Yay! Now I will say there was one anomaly that I can't explain. The first attempt with Smartswitch might have failed for some reason, I wasn't paying attention. After I thought it was finished, I looked and the update never happened lol. So, I reconnected the phone and tried a 2nd time and it went through without a hitch. There does appear to be a couple differences between the U and U1 versions but nothing major. I don't know if this means I'll have to use Smartswitchfor every update or not. The way I look at it is that, if possible, and that's a big "if", I'll probably go back to the original FW whenever Samskunk ever gets around to gracing us with their precious and immaculate 1st ever update for the abandoned US unlocked variants. I didn't want to download the FW from Updato but they appear to have a good reputation if XDA recommends them. Sammobile is who I would've used but now you have to make a free account and the downloar will take a day to just download... unless you pay. Um, no thanks lol. Good luck if you try it. I've done worse things on my lifetime. Also, it made me feel a little better about the whole thing considering the update from Smartswitch was gigantic. I wanna say as big as the entire firmware. Can't remember though. If you do it and catch that update size, can you hit me back? Thanks!!!... and hope it helps.
-
Hi, thanks for the info. Do you get the T-Mobile bloatware when you switched to the U from the U1? Does your Voice Mail still work like before? I read one of the XDA's for the S9+ could break the voicemail and it would change the bootloader version to where you couldn't go back to stock once you go that route.
-
Well visual voicemail (T-Mobile's app) never worked 100% right for me on this phone. I would get "can't reach server" messages, but I can get messages. Maybe you know what I mean?. Its the same now. Wifi calling works fine, I didn't see any bloatware. I had a few T-Mobile apps that i put on there beforehand (vvmail, tmo account app, digits, tuesday app). I don't know about the bootloader version but I did read the same thing. I won't know unless I either try (which might brick it). I think it has something to do with version 1 gets changed to v2 or something. I wish i could be more help but its a risk. Eventually I intend to sell this thing anyway, so I couldn't care less lol. Most people just text, post pictures on social media, and play with facebook, no concern about software, patches, etc... I can't tell you how many times someone will ask me to show them how to do something on their phone and I always look at the notifications bar and see a pending update. Every time. No joke. If the phone works and its pretty with no scratches, its as good as it is old. I'll see if i can find out the boooader version. You got me curious now.
-
It looks like it would break Caller ID so you would need to subscribe to their service along with the bootloader issue where you cannot got back to stock.
-
-
-
-
-
-
-
-
-
-
Finally the update today on my unlocked Samsung Galaxy S9+ to version G965U1UES2ARF4. It was 351.18MB in size and the first update since February 2018. Improved security and possible improvements for device stability and new and / or enhanced features and performance. So far, no issues with testing.
