3 ms·

Band 13 is Verizon's 700Mhz LTE band, and is the core of Verizon's coverage. Band 4 (2.1Ghz downlink from tower, 1.7Ghz uplink from phone) would be nice for spe

Band 13 is Verizon's 700Mhz LTE band, and is the core of Verizon's coverage. Band 4 (2.1Ghz downlink from tower, 1.7Ghz uplink from phone) would be nice for speed, but isn't strictly necessary to build something that has LTE. The only major sticking point with this is Verizon has a nasty habit of letting non-approved devices (like this) run for a few weeks, then suddenly bricking them without any notice. This module meanwhile will work on all of T-Mobile's bands and all of AT&T's commonly deployed bands: https://www.aliexpress.com/item/EC25-AF-Mini-Pcie-CAT4-Wireless-Module-LTE-Module-4G-Module-EC25-B2-B4-B12-B14/32920349180.html https://www.aliexpress.com/item/EC25-AF-Mini-Pcie-CAT4-Wirel... Neither T-Mobile or AT&T will brick your unapproved device, unlike Verizon.

squarefoot 8y ago
Can you be more specific about that bricking? Although I'm in Europe, so no Verizon over here, it still concerns me that a carrier can render a communication device inoperable.
- naraic0o 8y ago
  I imagine he means they blacklist the IMEI, rendering the device useless in the country (if there’s only one carrier that supports the device’s band).
  - squarefoot 8y ago
    Ah ok, I thought they would mess remotely with the cards FTDI style [1], turning them into paperweights. [1] https://www.zdnet.com/article/ftdi-admits-to-bricking-innocent-users-chips-in-silent-update/ https://www.zdnet.com/article/ftdi-admits-to-bricking-innoce...
    - StudentStuff 8y ago
      Verizon picks up that the IMEI of the device on the line is different than the one that is on file for your line, attempts to update it, and in the process of doing so breaks service on your line. You can swap over to a working Verizon supported device and swap back, but it could be hours to weeks later when you get this issue occurring again.
- blackflame7000 8y ago
  AT&T completely bricked SM-T337A trying to root. I should have read more carefully but every other version of that tablet is rootable except AT&Ts. Attempting to root with my version results in an endless bootloop with no way to restore because they havent released a signed version of their kernel to restore to. Obviously this is outside the ToS but my point is to elucidate that they protect their devices from modification to the low level baseband aggressively

squarefoot 8y ago

Can you be more specific about that bricking? Although I'm in Europe, so no Verizon over here, it still concerns me that a carrier can render a communication device inoperable.

naraic0o 8y ago
I imagine he means they blacklist the IMEI, rendering the device useless in the country (if there’s only one carrier that supports the device’s band).
- squarefoot 8y ago
  Ah ok, I thought they would mess remotely with the cards FTDI style [1], turning them into paperweights. [1] https://www.zdnet.com/article/ftdi-admits-to-bricking-innocent-users-chips-in-silent-update/ https://www.zdnet.com/article/ftdi-admits-to-bricking-innoce...
  - StudentStuff 8y ago
    Verizon picks up that the IMEI of the device on the line is different than the one that is on file for your line, attempts to update it, and in the process of doing so breaks service on your line. You can swap over to a working Verizon supported device and swap back, but it could be hours to weeks later when you get this issue occurring again.
blackflame7000 8y ago
AT&T completely bricked SM-T337A trying to root. I should have read more carefully but every other version of that tablet is rootable except AT&Ts. Attempting to root with my version results in an endless bootloop with no way to restore because they havent released a signed version of their kernel to restore to. Obviously this is outside the ToS but my point is to elucidate that they protect their devices from modification to the low level baseband aggressively