- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I bought an iPhone 5 from Ebay and I put my old sim card in it. I can send text messages, but I can't send iMessages. I went to the settings and looked for a reason why and in the phone setting my number says unknown. How can I fix this? I've tried taking the sim card out and putting it back in, and I have tried putting it on airplane mode and then off again and then went back to phone settings (that was suggested on another forum) but nothing happened. Any ideas are greatly appreciated. (:
PS, I would take it to a Verizon store, but the closest one to me is over an hour away.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How about an Apple store? Any close by?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No need to take your device to a store baldwin96, we can help you right here. Let's find out what is going on to get your iPhone 5 working. First, a few questions. Did you go through the full activation process of switching over the device either online via My Verizon or over the phone? Do you know which carrier the device was set up for originally? Please provide some additional details so we can assist further.
ErinW_VZW
Follow us on Twitter @VZWSupport If my response answered your question please click the "Correct Answer" button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I went through the process but on my Verizon my device didn't change. I've gone through that process several times to try to fix that. The person I bought the phone from said it was originally through Verizon.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did Verizon ever reply back to help you? It appears this is an ongoing issue as I have the same issue. I just noticed this is dated back last summer! But how is it that they have not fixed this issue moving forward?