NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MH7150-100EUS (M7) – Has anyone successfully activated a carrier eSIM? (Plus Poland / Europe)
Hello everyone, I am trying to activate a Plus Poland (Plus na Kartę) eSIM on my NETGEAR Nighthawk M7 (MH7150-100EUS). Router information Model: MH7150-100EUS Software Version: 2.12 Purchased i...
Update (after NETGEAR Support recommendations):
I would like to share an update in case it helps other MH7150 users.
Following NETGEAR Support recommendations, I performed:
- Full factory reset
- Fresh router configuration (no backup restored)
- New carrier-issued eSIM generated by Plus Poland
- Internet connectivity confirmed
- Latest available firmware (2.12)
- OTA reports no newer firmware available
The behaviour remains reproducible.
The router:
- successfully reads the QR code,
- contacts the SM-DP+ server,
- starts downloading the eSIM profile,
- reaches the final installation stage,
- then fails.
Originally the router reported Error Code 1.
After generating a completely new eSIM profile from the carrier and repeating the test after the factory reset, the router now reports Error Code 15.
Both eSIM QR codes use the same SM-DP+ server:
pkt.prod.ondemandconnectivity.com
NETGEAR Support has been informed and I have requested escalation to the firmware/eSIM engineering team.
If anyone has successfully activated a carrier-issued eSIM (not NETGEAR Marketplace eSIM) on the MH7150, I would really appreciate knowing:
- firmware version
- country
- mobile operator
- whether activation was done via QR code
Thank you.
Even a confirmation that a carrier-issued eSIM works on your MH7150 would be very valuable.
Update – new Plus eSIM tested on firmware 02.24
Another test has now been completed using a newly issued Plus Poland eSIM profile on the MH7150 running the new firmware 02.24.
Unfortunately, the problem is still reproducible.
The test was performed after restarting both the MH7150 and the phone. The activation failed again, and I submitted a new Instabug report immediately after reproducing the issue, including a short screen recording of the complete activation attempt.