Skip to main content

Can you activate a Moto G on Sprint?

Question: Can you activate a Moto G (3rd gen) on Sprint?

Answer: No.

TLDR: Don't use Sprint.


Having the unfortunateness of accidentally dropping and mostly obliterating a perfectly functional Nexus 5, my housemate was in need of a replacement ASAP. With solid specs and an amazing price tag (a mere $220) a Moto G (3rd gen) was high on my list of replacements. Considering the 2015 Nexus devices hadn't even been announced yet, it was pretty much the only option in that size range.

Moto was quick to ship and we skipped off to the Sprint store Moto G in hand to get it added to the existing service plan. I mean really, how hard could adding a phone be? Sadly it was all downhill from there...

Walking into Sprint there were a couple of people being helped or waiting to be helped but overly not very busy. Initially the service rep thought we wanted to transfer photos, data, etc from one device to another and said she could help us. After describing several times that we simply wanted the plan stop working on one phone and start working on another phone she finally understood but continued to deny being able to help. Instead insisting that we had to contact a Sprint call center.

They dial us in on one of the in-store phones and we end up on hold for a while...eventually a rep answers. The reps first response was also that we should be using the website, followed shortly by the device wasn't supported and more hold muzak. After a bit another story employee came to check on us, after describing yet again what we were attempting, she directed us to hang up and that she could take care of it in-store. On the computer. The single computer. The single computer already in use helping another customer.

Instead of standing around twiddling our thumbs waiting for the single computer to free up, we had a lightbulb moment. A once in a lifetime lightbulb moment. We went to the Sprint website on my phone to try and initiate the transfer there. Well...that turned out to not be such a lightbulb moment. Wow is the website not mobile optimized, full of weird errors that didn't make any sense, and just plain slow. Just to complete login we had to wait 5+ minutes for an OTP to get emailed.

To top it all off the website brickwalled at an "invalid IMEI" error.

The single working Sprint computer still wasn't available so we poked our heads into the Best Buy mobile store just around the corner. This was probably the real lightbulb moment because they were currently lording over an empty store so we jumped right in finding a solution. Unfortunately "invalid IMEI" was a persistent bugger that apparently is caused by a device not being in Sprint's database of blessed numbers.

My housemate had had enough by now so a few minutes later her number was ported to AT&T who was more than happy to activate on her sweet, sweet Moto G.

There is  a reason T-Mobile has overtaken Sprint as the number 3 provider in the US. On an unrelated note Project Fi support is fantastic and prompt.

Comments

Popular posts from this blog

Sync is currently experiencing problems

Update : I now recommend you install Google Chrome  and  disable  the built in Browser as it supports encrypting all synced data. After picking up a gorgeous  Galaxy Nexus yesterday I was running into an issue where my browser data wasn't syncing to the phone. After a little Googling I found this is commonly caused by having all of my synced Chrome data encrypted instead of the default of only encrypting the passwords. These are the steps I went through to get my dat syncing again without losing any of it. The exact error I was getting was "Sync is currently experiencing problems. It will be back shortly." In Google Chrome open the personal stuff settings page by clicking this link or by opening the wrench menu, and click on "signed in with example@gmail.com".  Hit "disconnect your Google Account" to temporarily disable syncing from your browser. Visit the Google Dashboard and "Stop sync and delete data from Google". I waite

A month of Flutter: a look back

Originally published on bendyworks.com . This is it. 31 blog posts in 31 days. Writing  a month of flutter  has been a ton of work but also lots of fun and a good learning experience. I really appreciate how supportive and and positive everyone as been. Publishing experience For the series I've been posting on  bendyworks.com ,  DEV ,  my personal blog , and  Medium . After publishing to these sites, I would put the Bendyworks link on  Twitter ,  Reddit , and the  Flutter Study Group Slack . Posting to DEV was easy as they use Markdown just like the Bendworks blog. DEV also has built in support for a  series of posts  so it's easy to read the entire series. I did have to manually upload any embedded images. DEV also has a number of  liquid tags  for embedding things like GitHub issues that I didn't make as much use of as I should have. Blogger is rich text so it was easy to copy/paste the rendered posts. This would hotlink all the images though so I had to rem

A month of Flutter: the real hero animation

Originally published on bendyworks.com . For the last post before the month's wrap up tomorrow, I wanted to do something more fun: use a  hero animation between the home page list and the individual post page. When I first implemented the  Hero  animation it never worked going back from a  PostPage  to the  HomePage . The reason was that  HomePage  would get rerendered and that would  generate new fake posts . So I moved the fake data generation up a level to  MyApp  and pass it into  HomePage . This is more realistic as going to the  HomePage  shouldn't request the  Post s every time. HomePage ( title: 'Birb' , posts: _loadPosts ( context ), ) The  PostPage  implementation is a simple  StatelessWidget  that takes  Post  and renders a  PostItem . This will become more complex as things like comments and likes are implemented but works for now. class PostPage extends StatelessWidget { const PostPage ({ Key key , @required this