Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
T-Mobile iPhone Users Seeing Frequent Random Restarts and Blue Screens
- Thread starter MacRumors
- Start date
- Sort by reaction score
It actually was reported in the past that blue screen of death is linked to the full flash storage memory on iOS device. Something related to the faulty flash chips which start to fall under such circumstances. I don't know although how T-Mobile could affect it and if it's the same issue at all. But in memory related issue blue screen of death was in the end followed by a red screen and that would be the literal physical death of a phone, it just won't start anymore. So seeing this blue screen I'd make a full backup. I've seen blue screen myself in the early days of iOS 8, but with some update Apple fixed something so it didn't appear since then.
I currently have a TMobile iPhone6 and ATT iPhone 5S purchased when previously residing in the US. I am now living in Australia and experienced the Blue Screen and subsequent reboot on the iPhone 6 recently (the iPhone 6 is still running with TMobile as the carrier). I have not directly updated the carrier settings.
Been happening on mine, but I assumed it was because of the beta. Downgraded and still happened.
Then I thought it was a hardware issue which is GREAT because I'm out of warranty... Hopefully it fixes soon.
Then I thought it was a hardware issue which is GREAT because I'm out of warranty... Hopefully it fixes soon.
Count me in. I was wondering why my finger unlock doesn't work all day. I finally watch it auto reboot. This blows.
IPhone 6 64GB. Tmobile USA in California.
IPhone 6 64GB. Tmobile USA in California.
Last edited:
Maybe it has to do with T-Mobile shutting down its legacy CDMA metro pcs spectrum a few days ago...
http://m.seekingalpha.com/news/2594235-t-mobile-turns-off-last-of-metropcs-cdma-nets
EDIT - It supposedly is to be repurposed as LTE spectrum. Seems very possible that a changeover may have not been tested thoroughly or not going as planned
http://m.seekingalpha.com/news/2594235-t-mobile-turns-off-last-of-metropcs-cdma-nets
EDIT - It supposedly is to be repurposed as LTE spectrum. Seems very possible that a changeover may have not been tested thoroughly or not going as planned
Last edited:
6 iPhones in our house, all on T-Mobile, in Silicon Valley Bay Area with No issues. 2 iPhone 6's 1 iPhone 5s and 2 iPhone 5C's. I received an carrier update on my 6 late yesterday so far so good.
A growing number of T-Mobile iPhone users are complaining about seeing frequent restarts and "blue screens of death" on their devices, a problem that seems to have begun very recently. MacRumors has received several complaints from readers, and there are also numerous reports of problems on Twitter, Facebook, and reddit.
Affected users are experiencing a split second blue screen that's followed by their devices restarting, and it appears most people who are seeing issues are T-Mobile customers that began having problems last night or this morning.
Known devices with problems include the iPhone 6 Plus, the iPhone 6, and the iPhone 5s, with restarts happening at 10 to 30 minute intervals. Multiple versions of iOS 8 appear to be affected, including iOS 8.1 and iOS 8.3.It is not clear if T-Mobile recently pushed a carrier update that's causing the problem, but a reddit user who spoke with T-Mobile's support staff said that he got the impression that T-Mobile believes a memory problem might be the cause of the restarts. "The sense I got from the technician is that a) they suspect memory problems, and b) they're getting a lot of calls about it," he wrote.
Some users have had success putting a stop to the restarts with a hard reset, and that's the solution that T-Mobile is recommending to customers who call in. If that doesn't work, T-Mobile is instructing customers to clear out their old text messages and do a factory restore via iTunes.
Article Link: T-Mobile iPhone Users Seeing Frequent Random Restarts
[URL='https://www.macrumors.com/2015/06/24/t-mobile-blue-screen-of-death-issue/']![]()
[/URL]A growing number of T-Mobile iPhone users are complaining about seeing frequent restarts and "blue screens of death" on their devices, a problem that seems to have begun very recently. MacRumors has received several complaints from readers, and there are also numerous reports of problems on Twitter, Facebook, and reddit.
Affected users are experiencing a split second blue screen that's followed by their devices restarting, and it appears most people who are seeing issues are T-Mobile customers that began having problems last night or this morning.
Known devices with problems include the iPhone 6 Plus, the iPhone 6, and the iPhone 5s, with restarts happening at 10 to 30 minute intervals. Multiple versions of iOS 8 appear to be affected, including iOS 8.1 and iOS 8.3.It is not clear if T-Mobile recently pushed a carrier update that's causing the problem, but a reddit user who spoke with T-Mobile's support staff said that he got the impression that T-Mobile believes a memory problem might be the cause of the restarts. "The sense I got from the technician is that a) they suspect memory problems, and b) they're getting a lot of calls about it," he wrote.
Some users have had success putting a stop to the restarts with a hard reset, and that's the solution that T-Mobile is recommending to customers who call in. If that doesn't work, T-Mobile is instructing customers to clear out their old text messages and do a factory restore via iTunes.
Article Link: T-Mobile iPhone Users Seeing Frequent Random Restarts and Blue Screens
Some of us already know we have MLC NAND, not TLC--mine was replaced for that issue, and being jailbroken means I was able to confirm beyond any doubt that the current phone is MLC.
It's extremely unlikely that anything T Mobile did would cause dozens or hundreds of TLC NAND chips to fail at the same time. Not to mention that it's also affecting phones that aren't related to the TLC issue at all. None of the phones prior to the 6 & 6+ used TLC NAND.
That something TMo did is triggering non-hardware related BSOD & bootloops is very plausible. That they're causing massive numbers of actual hardware failures? No. Not impossible, but close enough. I'd bet more on the solar flare activity being a problem before I bet on this being a TLC NAND issue.
I've had this going on for the past two days. Thought it was jailbreak related, but clearly it's T-Mobile.
T-mobile Chicagoland on an iPhone 5s. First happened whilst updating apps the other day, then nothing for a few days. Today, happened about 50 times, starting during the overnight hours.
I DID update the carrier settings a few days ago.
I went into DFA mode and restored, phone now restoring. It asked if I wanted to update the carrier settings, and I said NO. Awaiting completion of the restore. I will post my results.
I DID update the carrier settings a few days ago.
I went into DFA mode and restored, phone now restoring. It asked if I wanted to update the carrier settings, and I said NO. Awaiting completion of the restore. I will post my results.
The T-Mobile rep told me to put my phone into DFU mode and reinstall iOS 8.3 through iTunes. After telling the rep that I've done that twice today, I haven't heard back for 30 minutes. :-/
My phone has already blue screened twice during the restore process. I'm going to turn wifi calling off and see if that helps, per the earlier posts.
My phone has already blue screened twice during the restore process. I'm going to turn wifi calling off and see if that helps, per the earlier posts.
Yeah, that's great, except the main reason I use wifi calling on T-Mobile is because my office is in a dead spot for ALL the carriers. I also don't get T-Mobile signal in my house despite T-Mobile's coverage maps telling me I have excellent coverage in my area.
Not mad at you- just venting. :-/
Oh I hear ya. My town just got LTE a few months ago. I'm still trying to figure out where it's strongest. Their maps haven't been updated at all.
you can try putting the phone into airplane mode then reenable wifi. should allow for texts and calls to come thru over wifi calling while leaving the cell radio off. this seemed to help my gf's phone. could have been coincidence too, tho.
I've been getting a lot of random restarts on my 6 recently, but no blue screen. I'm on AT&T though.
Need to call Taylor Swift to fix this problem.
Had this happen a few times on iOS 9 beta 1 on an AT&T iPhone 6 -- didn't expect this would happen on a stable iOS 8 build.
I was wondering why this was happening to me several times today. I would pick up my 6 Plus and then it would tell me to input my passcode because the phone restarted, which I thought was very weird since I didn't restart my phone. I'm on T-Mobile.
I also notice the phone runs very warm, and if I use the system monitor app to watch what is going on, under RAM, it tells me it is using 875-940mb of the 1 gig of RAM. Phone still re-syncing after DFU / restore.
Wow, this happened to me today too and I just came across this article coincidentally. Actually had the BSOD occur while I was browsing through my mail around lunchtime. The phone restarted twice more within the next hour, but it hasn't done it again since. I just switched to T-Mobile literally last weekend and took a carrier settings update maybe 2 nights ago. My 64 GB 6 Plus was on AT&T previously.
I have iOS 8.3 public release, and Wi-Fi calling turned on. My wife has an iPhone 6 64GB (non-Plus) also on T-Mobile and has had no problems today. She does not have Wi-Fi calling turned on, so maybe that's related because I've seen it come up a number of times in this thread.
I have iOS 8.3 public release, and Wi-Fi calling turned on. My wife has an iPhone 6 64GB (non-Plus) also on T-Mobile and has had no problems today. She does not have Wi-Fi calling turned on, so maybe that's related because I've seen it come up a number of times in this thread.
I am traveling in Korea and using T-Mobile wifi to make calls and I started getting blue screens last night around 11 AM EST. It's probs safe to say that it's not the T-Mobile tower causing problems over here. Gonna try your suggestion.