Netgear M7 pro unable to connect 5G in S.KOREA

It is working here in Taiwan for nr5g service, with FW NTGX75_10.03.22.01, PRI 2.11, running NSA

"lteBandInfo": [  {		
		"isPcc": true,
		"sccId": 0,
		"sccState": 0,
		"band":7,		
		"channel":"3050",	
		"phyCid": "445",
		"dlBandwidth": "20MHz",
		"sccUlCaEnabled": "false",
		"sccUlChannel": 0,
		"sccUlBandwidth": "0"
	},{}],


	"nr5gBandInfo": [  {		
		"isPcc": true,
		"sccId": 0,
		"sccState": 0,
		"band":78,		
		"channel":"630912",	
		"phyCid": "120",
		"dlBandwidth": "90MHz",
		"sccUlCaEnabled": "false",
		"sccUlChannel": 0,
		"sccUlBandwidth": "0"
	},{}],
		

JohnPeng 
I have sent you a personal message. Please review it.

Unlike Taiwanese friend, my Model.json shows that my M7 Pro is not receiving any NR 5G signals at all. What could be the issue?

As far as I know, Taiwan and Korea use the same 5G band (N78) and LTE in NSA mode.

I appreciate your help.

W1lliam 

Thanks for your message.

As far as I know, telecom providers in Taiwan and Korea offer almost the same 5G (N78) + LTE 5G NSA service, but my Model.json is not detecting any NR 5G (N78) signals at all.

Is yours also the Unlocked AT&T version of the M7 Pro? Could you also share your software version?

And would it be possible for you to share the full Model.json file?

Thanks in advance!

Since I have changed my role in the company, I have forwarded your issue to our internal team. Someone will contact you later to help with your case.

Thanks

John

YoungJo here is the model.json from my device, MR7400-1A1NAS with FW NTGX75_10.03.22.01. There might be some settings that leads to NR5G not working in S.Korea, ran into that situation with MR6450-100EUS here before, till Netgear updated FW to support.

YoungJo Netgear will fix that, just the matter of time. It was 2-3 months for generic model, this AT&T SKU might take longer as it is not running in USA in ATT network.

---

W1lliam wrote:

YoungJo Netgear will fix that, just the matter of time. It was 2-3 months for generic model, this AT&T SKU might take longer as it is not running in USA in ATT network.

---

from experience, ATT mobile hotspots have to be in ATT network running an ATT SIM for it to get OTA updates, unless a firmware file is provided for a manual upload. not sure if that has changed.

rcpax I did the first OTA upgrade here, it was buggy on very first FW and then fixes some bugs in current FW, so I assume ATT is unblocking OTA for non-ATT network/sim for this particular model.

W1lliam 

I agree.

As soon as I received the device in Korea, a firmware update was performed.

When I quickly compared the Model.json file you provided, W1lliam, with mine, I noticed that I only have 0: All and 1: LTE All under BandRegion, while you have 2: Full Bands.

Did you modify this yourself? Or did it appear after an update?

I'll take a closer look and ask you about the differences.

that's good to hear. I have a used MR6500, I'll see if it picks up the latest FW.

YoungJo I have added one band option manually all the supported bands

Full Bands was added to Band Region Options

And set active band region to this new added option

But these does not help to resolve your problem I guess.

W1lliam 

Thanks for your quick reply.

But I can’t see the image.

Did you add the Band options via AT commands through Telnet? And did you select them using the Netgear Mobile App?
If that's the case, I did the same thing, but as you said, it didn't work. 😭

YoungJo Yes, adding band region option with AT commands, also specifying which band region as default. It does not allow you to pick up available band region options from Web interface, not sure about App. It is working here with default settings, so your problem should not has dependency with this band region options.

W1lliam 

Could you let me know how you set index 2 as the default after adding the Band Region option?

In my case, I can't select it through the Web UI, but when using the Netgear Mobile App, I can see and select the added Band Region.

However, since index 0: All already includes all available bands, including NR78 NSA, it does seem like the issue is unrelated to the Band Region option, as you mentioned.

JohnPeng 
Hi John,
Could you let me know when I can expect to hear from your colleague who is handling this issue?
Thanks in advance!