[Magisk] estofjlw:
It is one of those nasty little secrets . . .

[MENTION=4667597]Didgeridoohan[/MENTION]

It is either that or the ROM APN settings and radios have stopped working and in that case there would still be likely an LTE signal served up.

I am a network engineer and I once worked at NYNEX - and I know what the cell phone system and recent software is capable of. Carriers today are all sharing towers - but the Networks computers then split off and manage traffic negotiating initial connect and hand-off across the towers based on the software the carrier has installed and the polices it uses and MVNO's etc

I will first re-flash the custom ROM later and see if it will negotiate and be served LTE later after a few days.

It is not the SIM because it works and is served LTE on three other devices - it gets signal bars but no LTE. on this affected one device only.

Verizon and Visible play this trick also - as does Sprint. Visible has it right in their terms of service that they can monitor the apps on your phone because of their Visible app and deny access to the network for the applications you have installed - and Magisk could not stop it and would be seen using this Trojan horse app.

It is illegal to bar phone service but not LTE and data - so the device gets signal BARS and will make and receive calls - but you will get no data - no internet - and are never served an IP even with low band 1 or 2 G

That is what the FCC recently said it would not do - consider broadband - or data a part of their jurisdiction

If it were the ROM - there would still be an LTE signal immediately served along with the signal BARS. I put that same SIM in any other device and LTE is served up right away and the Internet works I put another SIM - which is working - in that device and once again no LTE signal is served up.

IMEI's get blacklist blocked without notice for unlocked bootloaders flat out on some Carriers and on others if they cause problems. The carriers never tell you because technically it is illegal - even though it is in their terms of service it is still against the law by FCC and in California - by state law. So they play like - "did I do that" - and ask you to bring in the phone for inspection or warranty swap.

There is a published block list for unpaid debts on the device / account - and / or stolen devices. But the unpublished block list is for rooted and discovered unlocked modified devices, and the block list sometimes clears after 72 hours - and sometimes it becomes a permanent blacklist for the IMEI - you do not know which and nor will they tell you - because as said it is technically illegal because an "unlocked" device cannot be barred from the network - and especially in California the net neutrality forbid it. It is a grey area that they do no have to let the device on the network if it is modified.

The good news is the unlocked bootloader block may clear at some carriers if the device tries to negotiate again later and then has a locked bootloader and stock ROM of the latest software version and a matching build prop file

Because I discovered my Magisk hide was not enabled - it is likely someone looked at the device manually and saw the ro.build.fingerprint did not match a device which has Android 10 on it stock. In short an IMEI for a Moto G7 Power when Android 10 is not rolled out as the upgrade yet on that device.

Right now they cannot really tell if a bootloader is unlocked AND the phone is rooted if Magisk is working right - though as you pointed out in the future that software may come back on line - being used by Google - who will then report it to the carrier as a compromised modified device. and the close relationship is they will block it.

So if the basic integrity passes on boot - the carrier will not look unless multiple boots are happening and the ro.build.ffingerprint is changing each time - and they CAN read it - but just usually have no need to unless the network alerts them by IP's changing from constant reboots - like from trying to get the CTS Profile to pass.

I have seen more than few guys flash a ROM and this happens and they have no clue - and I have told them flash it back stock, lock the bootloader and try later in a few days - and most of the time they device starts worming again as a stock device, and one of two have taken it back to trade in under warranty - only later to find motorola reports to the carrier it has no warranty as the bootloader code was served to unlock it which voided the warranty

When I re-flash I will use wifi to get safety net to pass - first and then try only ONE time to see if LTE gets served up after about 5 days down the road. I think the Android 10 will be a flag on an Android 9 device however until the official OTA update to Android happens around June or so, and then an ro.build.fingerprint for ocean 10 exists. . Right now my version 9 phone is back working again - it just has a bad display and I am waiting on the replacement part to arrive from China - but it is working for what I need.