News for hackers. Stuff that matters.
Re:iMessage purgatory by uptown on Tuesday May 13, 2014 @03:39PM (#7740182)
This site has a solution:

1. Reset your Apple ID password and do not log back in on your device(s)

2. Send a text to 48369 with the word STOP

It won’t happen immediately but over a 12-hour period, you should start receiving texts on your Android device that are sent from iPhone users.

http://www.techrepublic.com/article/how-to-keep-receiving-sm...

Re:iMessage purgatory by bradfa on Tuesday May 13, 2014 @03:43PM (#7740217)
Official Apple knowledge base info: http://support.apple.com/kb/TS5185
Re:iMessage purgatory by Scorpion on Tuesday May 13, 2014 @03:46PM (#7740236)
I think it's important to note that the Apple KB explicitly states that the steps outlined in the parent comment and article do not work.
Re:iMessage purgatory by toddn on Tuesday May 13, 2014 @04:03PM (#7740352)
Which conflicts with http://support.apple.com/kb/HT5538 (under Unlink a phone number).
Re:iMessage purgatory by benjarrell on Tuesday May 13, 2014 @04:04PM (#7740363)
What that doesn't say is that when you call, they will tell you that a support incident will cost $30.
Re:iMessage purgatory by powdahound on Tuesday May 13, 2014 @03:46PM (#7740242)
I did all this a few weeks ago but still had to wait a few weeks for my friends' iPhones to realize my number was no longer iMessage enabled. During that time they all had to "Resend as SMS" on their messages to me.

We all ended up on Google Hangouts in the end (the iOS app is nice!)

Re:iMessage purgatory by johsoe on Tuesday May 13, 2014 @03:53PM (#7740293)
"Performing these tasks won't deregister iMessage" from: http://support.apple.com/kb/TS5185
Re:iMessage purgatory by w-ll on Tuesday May 13, 2014 @10:25PM (#7741879)
What is the point of that section then?
Re:iMessage purgatory by mikestew on Tuesday May 13, 2014 @11:57PM (#7742111)
Because the steps in that section keep getting passed around as possible fixes. Some of them are mentioned in this very thread. Sadly, it's been my experience that the fix Apple does suggest doesn't work reliably (works for some, not for others), either.

EDIT: holy crap, as toddn points out above, apparently that section is also to contradict the bad information that is passed around in Apple's own KB articles: http://support.apple.com/kb/HT5538