Jump to content


S4GRU Member
  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Kearney

  • Rank
    Member Level: Digital

Profile Information

  • Phones/Devices
    Note 5 sprint
  • Gender
  • Location
  • Here for...
    4G Information
  1. I'm building modemmanager into openwrt if anyone wants my build. It does mwan3 with multiple modems in load balancing perfectly. You can even do a true IP bridge/passthrough with it. No need for reconnection scripts or anything. Plug and play. I also cross compiled the modemmanager luci protocol. Just click it and a drop down window appears with all the apns in have pre added in for as many carriers I could find. It doesn't disconnect like rooter does either. Here is my build for the 3526 but I can build for any router you want. Just choose the mobile data protocol in the wan. Plus you can use the libqmi flash tool right on the router to flash your modem. You will see me as user "westrem" on many of these forums and sites. I'm also a mod on ltehacks. https://www.dropbox.com/s/ssxgepdzo8pn68r/openwrt-ramips-mt7621-zbt-wg3526-16M-squashfs-sysupgrade.bin?dl=0
  2. I'm using this firmware on the mc7455 just fine. The firmware does not mess up the ability to issue at commands. The method in which you flash could put the modem into a different usbcomp which you then need to fix. This only happens when using windows to flash the modem. Use linux instead. A ubuntu boot usb works great if you dont want to install linux. Boot into the "try ubuntu" then use the libqmi firmware update tool and you're done.
  3. You extracted the 1.05 firmware correct? Then just clicked the one single .exe while the modem is plugged in.
  4. You must extract the 1.05 firmware and run the .exe and let it finish, then one click flash the 1.05 firmware then let it come back up. Then one click flash 1.07 twice. Daniel's ubuntu method did not work for mine. I had to do it with windows.
  5. I also had mine get stuck in qdloader. If you haven't gotten it fixed let me know. I have a procedure that unbricks them.
  6. The newest generic firmware for the em7565 is what I'm using. So your em7455 was physically messed up? Using a different em7565 fixed the issue?
  7. Anyone having issues with 3xCA with the em7565? Mine used to work great, then 3 days ago nothing but packet losses once the 3rd carrier kicks in. If I keep it at on 2xca all is well.
  8. I tried to edit my last post to include a quote I found on the forum that relates to this but I think I messed up the edit.
  9. Sorry for the misinformation then. My mistake. I've tried multiple sim cards out of phones using the x.ispsn apn on my LTE modem and it never assigns an ipv4 address. Are you sure it's not just a local ipv4 address assigned by the phone and tunneled over ipv6? I found this while digging around in another forum. " Sign In MOTO E™ 4th Gen / MOTO E™ 4th Gen Plus 1 … 4 5 6 7 Next All Topics Previous Next Reply Topic options Albany889 Punch Card Message 41 of 61 Re: Moto E4/E4 Plus Issues on Sprint ‎11-30-2017 02:42 PM It is possible that sprint variant E4 has a different and optimized setting of APN. 0 Kudos Reply lenovoma Punch Card Message 42 of 61 Re: Moto E4/E4 Plus Issues on Sprint ‎11-30-2017 02:53 PM- edited‎11-30-2017 03:05 PM It could be APN (not accessible with Sprint's configuration menu, but reports say if you insert another GSM network SIM you can poke it). However, the only setting that could be "wrong" would be "APN protocol." The options are: "IPv4", "IPv4/IPv6", "IPv6." APN's might be stored on SIM. Where did you guys get your SIM's, from Sprint, or Boost/Twigby? It could also be broken 464XLAT (NAT46) in the Moto OS itself. 0 Kudos Reply jp0213x Punch Card Message 43 of 61 Re: Moto E4/E4 Plus Issues on Sprint ‎11-30-2017 02:55 PM This is my first unlocked phone on sprint and I found out first hand they will not help and will point you back to the manufacture. I'm not in a hurry to purchase a replacement phone for now, but this problem was a real deal breaker for me. Rule of thumb for me is to test any new phone I get right away and make sure it does everything my older does. I am not back to my rooted s4 cyogenmod until the problem is address or keep an eye out for another phone. I would like the s8 active but refusing to pay that kind of money for a phone when the e4 plus does the same thing for cheap. 0 Kudos Reply jp0213x Punch Card Message 44 of 61 Re: Moto E4/E4 Plus Issues on Sprint ‎11-30-2017 02:57 PM My sim card was from a sprint store, a coporate store. The 3rd party sprint stores are clueless. 0 Kudos Reply Albany889 Punch Card Message 45 of 61 Re: Moto E4/E4 Plus Issues on Sprint ‎11-30-2017 06:17 PM My sim card was from Sprint.com. It can be considered as an official card from Sprint. But if I remember correctly, my IMEI was recognized as iPhone 8/8 plus at some point when purchasing or activating the sim card. 0 Kudos Reply lenovoma Punch Card Message 46 of 61 Re: Moto E4/E4 Plus Issues on Sprint ‎12-01-2017 10:33 PM I did some further testing and my conclusion is the following: 1. Sprint is pushing us a network profile that is ipv6 only, ipv4 is completely disabled en route from the phone to the Sprint network, although they do implement a NAT64 on their end so as to allow reaching the ipv4 network on the other side. You can see this in effect if you open up a browser and type in an address like www . google . com, where it works, but if you type in its one of its many corresponding ipv4 ip addresses, for example, 172 . 217 . 13 . 228, it does not work. Even in a browser. This tells us that the only reason any app works at all with ipv4 on Sprint is because they are going through Sprint's translating DNS server. 2. The Moto E4 is broken, having either not included or not started the Android built-in CLAT service (client 4-to-6 translation) on the phone. Normally this service, part of native Android since Jelly Bean according to Wikipedia, would allow apps that require ipv4 literals to be able to route on an ipv6 only network by creating a fake ipv6 address. It is a combination of these two that result in our phones not working on Sprint. People have had issues on T-Mobile in the past on other phones as well when they switched over to ipv6, but at least T-Mobile lets you put in APN settings to force it to ipv4, Sprint does not, as Sprint insists on provisioning all your connection settings over-the-air. What would be a very interesting test to try is to get a T-Mobile SIM and set the APN settings to ipv6 only, and see if the unlocked Moto E4 can route packets to ipv4 literal addresses (or equivalently if all the streaming apps work). If that does not work either, then we know the Moto software has a broken implementation of 464XLAT. I suspect it does not work. As for phones that have no problem on Sprint, either they have the correct software, or Sprint is sending them profiles with ipv4 enabled as they are "legacy" phones. The good news is that eventually, the apps will get updated and work over ipv6. They have to do that for iOS already, but they may be dragging their feet on Android. The bad news is I suspect neither Sprint nor Motorola is interested in solving this problem."
  10. X.ispsn is ipv6 only. No ipv4. On phones using this apn 3g takes care of ipv4 and lte takes the ipv6.
  11. Nothing to share really unless you wanted a specific build for your router from my linux build machine. I use a netgear nighthawk r7800 and an em7565. Stable openwrt 18.01 is on 4.14 kernel and supports qmi with raw ip just fine. Also you didn't ruin that em7565 you tried to flash. You need to first update to an intermediate firmware (1.05.xx.xx) then flash the newest firmware(1.09.xx.xx) twice in a row and it will work just fine. You may need to fix your impref back to "GENERIC" before you reflash as well.
  12. I'm using a em7565 and recieve 3xCA just great in Kansas City. I cross compiled modemmanager onto openwrt snapshot running 4.14 kernel and use qmi. I didn't like the rooter package. Too much scripts for stuff I didn't need. I also wanted to be able to bridge the lan and wan for ip passthrough and it was not possible with rooter. Modemmanager does it just fine. It seems you must lock band 41 to get 3xCA or else you only receive 1 band of 41. EMM state: Registered RRC state: RRC Connected Normal Service IMS reg state: No Srv PCC RxM RSSl: -62 PCC RxD RSSl: -65 SCCI RxM RSSl: -77 SCCI RxD RSSl: -79 SCC2 RxM RSSl: -77 SCC2 RxD RSSl: -80 Tx Power: RSRQ (dB): -l0.8 PCC RxM RSRP: -95 PCC RxD RSRP: -97 SCCI RxM RSRP: -96 SCCI RxD RSRP: -99 SCC2 RxM RSRP: -95 SCC2 RxD RSRP: -98 2639(9785) Cell ID: 04d4be33 (81051 187) TAC:
  13. Does the apn settings change anything? R.ispn between n.ispn? Thats another difference
  14. The only difference i see is my note 5 does have an ipv6 adress and the ZTE pocket wifi does not. Its turned off. I turned it on but it goes back off. Im on the most current software. I have to put it in lte only mode to even get it to try to connect to the same tower as my note 5. The note 5 will grab 2 download channels and work perfect. The ZTE will only grab one, say conected but have no internet at all. If i aim my external mimo at a further away tower the ZTE will grab 2 seperate cell id's and then grab 2 seperate download channels and work. But its a terrible signal and it wants to drop to band 25 or 26. Does same cell id carrier aggregation only work with an ipv6? Thats the only thing i can think of.
  15. Ok. I have a note 5 that i can set in a window and get great speeds. Its on band 41 and has 2 matching cell id's and 2 download channels. Everything works perfect. Now i have a ZTE pocket wifi also sprint lte plus. I set it in the same window but can only get one cell and no conection. Its like it wont grab the secondary cell. Here is whats weird. My phone while driving around always has matching primary and secondary cell id's with 2 downloading channels. My ZTE pocket wifi will only get carrier aggregation when the 2 cell id's are different. And its never as fast as my phone. I dont get it. I set up a mimo antenna to the ZTE pocket wifi and aimed at the tower my phone gets band 41 w/CA and still even with better rsrp it only connects to one cell and has no conection. I aim the mimo to another tower further away and get 2 seperate cell id's on band 41 with terrible rsrp and get decent speeds but it wants to jump back to bands 25 and 26 after a while. Does the ZTE pocket wifi not have true carrier aggregation?
  • Create New...