na7q

Android Specialist
  • Content count

    3,114
  • Joined

  • Last visited

  • Days Won

    75

na7q last won the day on December 4 2015

na7q had the most liked content!

About na7q

  • Rank
    Amazing... Enough Said
  • Birthday September 1

Profile Information

  • Gender
    Not Telling
  • Location
    Uhmerica

More Info

  • Device
    Nexus 6 (AT&T)
  • Google Talk
    mike.ph4
  • Google Plus
    117490729411959897180

Recent Profile Visitors

3,094 profile views
  1. give me the tv!
  2. I wonder what the reason behind that is?
  3. Absolutely possible one the Moto X 2014. One of the best phones for doing it.
  4. Get anything but Samsuck and you'll be okay. Go with a Nexus, or a Moto, or even an LG for something similar to Samsuck with out the crapiness of TouchWizzzz.
  5. I can confirm it works in US Cellular. I have also locked it on to Verizon (which I haven't been able to do recently, so roaming on them may be out of the game). I need to test it out though. As for AT&T I haven't been able to get it to roam on that. Otherwise I can confrim that is works on USCC as I use them daily with Fi. Since the 6.0 update, it will no longer show it's roaming when not on Sprint or T-Mobile. And even if you select the most expensive plan, you only pay for what you use aside from the first payment. And I pause because you literally pay by the hour for active service.
  6. Why don't they work. That's teh question.
  7. Samsuck devices never used to display the correct band. It's probably not correct. Especially if the FCC didn't approve the device to use it. You don't need it and it's useless. It's a waste of a network and its resources. (: Hopefully it's never implemented. It's just going to cause problems. Should support all the basics. Considering it's a "world" phone. Aka LTE/GSM/CDMA phone. Shouldn't have any problems with it as expected. Devices are instant. Newer Moto devices do work on every band they are capable of. Covering the majority of the bands the big networks use. So not sure what you're getting at. Samsuck devices are the opposite however. Enjoy the dead horse lol. Cause that's all USCC is.
  8. Been a problem since 6.0 I heard.
  9. Technically no, but theoretically yes, but only if you can make USCC believe it's a Nexus or iPhone.
  10. Nexus 6 from Amazon or eBay. Can't beat the price for the device. Samsuck is not the way to go. It's disgusting to say the least and shouldn't be classified as Android.
  11. my friends, in the end nothing workscode 00000000 or 000000 or 123456 does not remove the blocking network. Maybe this is the varinat 1 on 10,000 when is not possible to unlock. Every device is unlockable. You just haven't taken proper steps to getting it unlocked. In the future. DON'T buy an international phone and you won't have a problem. You'd still have a chance of having this problem even if you purchased it from Moto directly. The problem is you buying a phone not made to be used in your country.
  12. Probably a SIM issue. I have AT&T and used this phone on it for a while. I also used it on T-Mobile for a couple days. And US Cellular for like a month.
  13. They're cheap as shit compared to the international versions, that's why. A USCC Galaxy S4 is like $50 used, a GSM unlocked one is like $130. I disagree partially. While yes, a USCC vs GSM unlocked is cheaper. That's an ignorant reason to choose a device that doesn't support GSM. Also, since you can buy a USCC and GSM unlocked Moto X for the the same price, it doesn't make sense to do it. No logic found. He could probably call in and get the MSL/SPC code for CDMA reprogramming but the SIM-lock code(NCK) is a separate mechanism from that(the codes are different) and I doubt USCC has that info If locked by USCC/Motorola, all he has to do is call in. If he flashed a T-Mobile ROM/Modem that could have messed with the EFS folder(If Motos have one) and SIM locked it.(T-Mobile locks their phones) I once flashed a Yemen modem to a R970, completely nuked the baseband and IMEI and I never got it working again. It's possible that through his ignorance he's permanently locked his phone, dunno for sure though. Definitely isn't caused by this. I've never heard or seen T-Mobile locking phones by default but probably changed recently. I'm sure it has nothing to do with the ROM.