121–130 of 279 posts
This is fixed in iOS 12.3 [1] and macOS 10.14.5 [2], both released on May 13th. As Natalie noted on the ticket, turning off iMessage will also prevent the bug. [1]: https://support.apple.com/en-us/HT210118 [2]: https://support.apple.com/en-us/HT210119
Turning off iMessage to prevent the bug is like turning off a car to prevent to consume petrol.. what a solution
Earlier quoted context omitted.
The reasoning is that once a fix is out, by making it public then users can know about it and intentionally update their devices if they haven't yet.
Sounds good in theory. In reality, the vast majority of iPhone users are not aware that this bug exists and never will be. The best action for user safety is to wait until the period has elapsed or the exploit has been seen in the wild already. Alternatively, they could publish the gist of the exploit without providing enough detail to actually perform the exploit.
Earlier quoted context omitted.
Turning off iMessage to prevent the bug is like turning off a car to prevent to consume petrol.. what a solution
Where I live nobody uses iMessage so this sounds like a good workaround :P (Yes yes I know it’s been patched already...)
Yet another wrong use of the word bricked. Bricked means bricked and you can’t ever come back from that.
Since a restore works it cannot be called a brick though?
There’s nothing bricked about this. There are no levels of brickedness.
Yet another wrong use of the word bricked. Bricked means bricked and you can’t ever come back from that.
For example, if I pull out my EPROM writer, de-solder the chips, and update them almost no device is truly "bricked" by this definition. The only exceptions would be burned update fuses or similar physical damage. Making the definition itself extremely niche, to the point of being synonymous with "physically damaged/destroyed."
I myself stick to the broader "technologically as useful as a brick" definition. Which a boot-looping iPhone absolutely fits. The fact there are ways to recover it is neither here nor there.
I generally call what you're describing a "Hard Brick." But even those are sometimes recoverable via as I said chip re-programming.
Earlier quoted context omitted.
One of the comments on the bug has the answer: For testing purposes, there are three ways that I found to unbrick the device: 1) wipe the device with 'Find my iPhone' 2) put the device in recovery mode and update via iTunes (note that this will force an update to the latest version) 3) remove the SIM card and go out of Wifi range and wipe the device in the menu
Instead of wiping the phone, couldn’t you just disable iMessage once you habe removed the SIM card and are out of WiFi range?
This brings back old memories from hardening the sms/text parsers of feature phones of yesteryear. There it wasn’t entirely uncommon that when you sent a malformed sms-deliver PDU (e.g. text message) to the phone and crashed parser that tried to decode it, it took also the phone down before it could ack the message back to SMSC. Which of course meant that as soon as phone was turned on and it registered to network, t…