May have some luck on OpenWRT/LEDE forums, since the MX60(W) is supported. But yeah, if you're getting absolutely nothing on the serial console, then not sure there's any sort of recovery option besides JTAG.  Supposedly JTAG is enabled on the board, and it looks like the 16 pin JTAG that the 4xx PowerPC chips use, so may have some luck messing around with OpenOCD or other JTAG tools.   But yeah, unless you're really bored and want to mess around just for the fun of it, probably better to just grab a cheap one from eBay.   Though now I'm curious enough I'm tempted to see if I can find an old MX60 I swear we had laying around, I want to know if it's actually recoverable from JTAG. 🙂 ... View more

We've been using this app for a few years to enable users to access the WiFi Settings menu: https://play.google.com/store/apps/details?id=org.logpedia.wifi ... View more

The GPS issue is likely the same one I've had a ticket logged for since Aug 2019, so I expect it will never be fixed (though they have tried a few times this year with SM app updates).  The workaround on our TC25s was to go into Settings -> Security & Location -> Location Mode and change it to High Accuracy.   Edit: Sorry!  I read my notes wrong initially, and put the wrong mode at first.  What you want is High Accuracy mode, Device Only mode is the default mode and that's where the problem is.  Meraki MDM doesn't seem to have a way to enable High Accuracy mode automatically, and the SM app throws an exception behind the scenes when the phone is in Device Only.  From the reading I've done on accessing GPS data through Android, it should be trivially easy for Meraki to detect the current location mode and correctly request the data depending on the mode, but so far the new versions I've tested didn't fix it.   Also, you can tell it's working correctly if you get the "location pin" showing up in the status bar when you run the Meraki SM app. ... View more

Interesting, I've been fighting with the MS authenticator app not working properly on iOS devices for ages, and never thought to disconnect from WiFi and try 4G.  But we've had the same thing, can OAuth login fine on the phone, get the Authenticator popup and hit approve, but then it never goes any the further in the settings.  Just sits with the moving dots on the MS login page.  I had to go back to app passwords so users could keep using the builin Mail app.  They always said it worked fine for a couple months, but then randomly stopped working.  Now that I think about it, in every case that it stopped working, they were in the office connected to WiFi.  I remember that even when I first set them up with MFA, it would often take a handul of tries before it would actually continue correctly.   And today I've been fighting with OAuth login on my Android phone, similar problem.  Runs through account setup and I can login fine at the MS login page, but hangs on "Getting account info" after the MFA popup.  I just put my phone on 4G, and it went straight through first try and email is working fine.   4G is with the same ISP over same network, so I don't think it's an ISP specific issue.  I don't have any filtering on this SSID, either.   I might have to investigate further and see if this actually is WiFi related, which seems bizarre. ... View more

I logged a ticket regarding the IP vs GPS location a few weeks back, and was told it's broken on Android 8.x. That matches up with what I've noticed, none of our 8.1 devices can report location by GPS. I did not get a timeframe for a fix. ... View more