- Mar 16, 2010
- 880
- 25
- 0
So this weekend, I had a somewhat nightmarish phone scenario. I have a stock, never rooted T-Mobile S8+. Like everyone else, I received the update to Oreo on Saturday morning. Long story short, the update ruined my phone (caused an infinite bootloop, with no access to recovery). Called Samsung, they sent me to Best Buy (the Samsung experience kiosk) to reflash the firmware. The people at Best Buy ended up flashing an international firmware onto my phone.
After 3 hours there, they sent me to Samsung 837 in NYC. There, the reps for Samsung were incredulous at how badly best buy handled the situation. They ended up flashing stock, T-Mobile firmware onto my device, and all seemed well.
Currently, however, when I check for update, my phone says it is up to date. My colleague at work has the same device on T-Mobile. He checked for update right in front of me, and the phone instantly started downloading Oreo.
Is it possible that, while reflashing my firmware, Samsung somehow messed up? Does anyone have any suggestions as to how to force the OTA update to hit my phone? I am currently on Nougat, with the February 2018 security update.
Thanks!
After 3 hours there, they sent me to Samsung 837 in NYC. There, the reps for Samsung were incredulous at how badly best buy handled the situation. They ended up flashing stock, T-Mobile firmware onto my device, and all seemed well.
Currently, however, when I check for update, my phone says it is up to date. My colleague at work has the same device on T-Mobile. He checked for update right in front of me, and the phone instantly started downloading Oreo.
Is it possible that, while reflashing my firmware, Samsung somehow messed up? Does anyone have any suggestions as to how to force the OTA update to hit my phone? I am currently on Nougat, with the February 2018 security update.
Thanks!
Facebook
Twitter
Instagram