PfSense 2.3 and Huawei E8372 - Making it Work

AndrewZ

my Huawei E8372h-153 is not responding to AT^SETPORT? command. It throws ERROR only, so I cannot change the mode.

The following command is used to unlock some AT-commands, but result depends on the current firmware version loaded

AT^DATALOCK="OEM code"

I can try to generate a code for you if you will PM me an output of

AT^NVRDEX=50502,0,128 and AT^NVRDEX=50503,0,128

I do not own such a modem myself, so I can only try.

Xamaba

AT^NVRDEX=50502,0,128 and AT^NVRDEX=50503,0,128

I will setup a fresh install of 2.3 on a spare machine to test.

AndrewZ

@Xamaba:

I will setup a fresh install of 2.3 on a spare machine to test.

No need. For modem preparation you will need any computer running any terminal program.

devianceluka

@AndrewZ:

my Huawei E8372h-153 is not responding to AT^SETPORT? command. It throws ERROR only, so I cannot change the mode.

The following command is used to unlock some AT-commands, but result depends on the current firmware version loaded
AT^DATALOCK="OEM code"
I can try to generate a code for you if you will PM me an output of
AT^NVRDEX=50502,0,128 and AT^NVRDEX=50503,0,128
I do not own such a modem myself, so I can only try.

Send:AT^DATALOCK="OEM CODE"

Recieve: ERROR

Send:AT^DATALOCK?

Recieve: ^DATALOCK:1
Recieve: OK

Send:AT^NVRDEX=50502,0,128

Recieve: ERROR

Send:AT^NVRDEX=50503,0,128

Recieve: ERROR

Please reply as soon as possible, I'm waiting for you!

AndrewZ

@devianceluka:

Send:AT^NVRDEX=50503,0,128

Recieve: ERROR

This means that your particular modem is blocking access to this command as well. Without this information I have no idea how to generate the OEM code.
As I mentioned earlier, result depends on the firmware the modem is running. Please post the firmware version you're running (available from ATI command), just for our information.

devianceluka

@AndrewZ:

@devianceluka:
Send:AT^NVRDEX=50503,0,128

Recieve: ERROR
This means that your particular modem is blocking access to this command as well. Without this information I have no idea how to generate the OEM code.
As I mentioned earlier, result depends on the firmware the modem is running. Please post the firmware version you're running (available from ATI command), just for our information.


Recieve: Manufacturer: huawei
Recieve: Model: E8372
Recieve: Revision: 21.313.11.01.1241
Recieve: IMEI: xxx
Recieve: +GCAP: +CGSM,+DS,+ES
Recieve: OK

I finally got excited when I saw you could do it. Now I'm back to the starting point. :-(

AndrewZ

@devianceluka:


Recieve: Manufacturer: huawei
Recieve: Model: E8372
Recieve: Revision: 21.313.11.01.1241

As far as I know people were successful with datalock unlock on 21.xxx.99.xx.xx firmware.
I suggest to try changing the fw.

devianceluka

@AndrewZ:

@devianceluka:
Recieve: Manufacturer: huawei
Recieve: Model: E8372
Recieve: Revision: 21.313.11.01.1241
As far as I know people were successful with datalock unlock on 21.xxx.99.xx.xx firmware.
I suggest to try changing the fw.

What I do not fully understand is this:

for DATALOCK="OEM code", one should input OEM code from AT^NVRDEX command correct? So it's the NVRDEX command that is not working.
all I need is OEM code? With this code and DATALOCK command - I unlock other AT commands?

What if I write a small script that bruteforces OEM code in DATALOCK command?

Thanks for still sticking here and helping. I really appreciate it!

AndrewZ

@devianceluka:

for DATALOCK="OEM code", one should input OEM code from AT^NVRDEX command correct? So it's the NVRDEX command that is not working.

all I need is OEM code? With this code and DATALOCK command - I unlock other AT commands?

1. The output of AT^NVRDEX command is used to generate an OEM code by a special tool.
2. Generally - yes. Potentially one can reset or change the OEM code, but this requires ^NVWREX command being working.

devianceluka

@AndrewZ:

@devianceluka:

for DATALOCK="OEM code", one should input OEM code from AT^NVRDEX command correct? So it's the NVRDEX command that is not working.

all I need is OEM code? With this code and DATALOCK command - I unlock other AT commands?

1. The output of AT^NVRDEX command is used to generate an OEM code by a special tool.
2. Generally - yes. Potentially one can reset or change the OEM code, but this requires ^NVWREX command being working.

Andrew, how sure are you that AT^DATALOCK has a 8 digit code in it? My script, that tried every possible combination from 99999999 to 00000000 just finished and every single combination throws ERROR. Can you please help me on what to do next?

AndrewZ

I know that some commands are locked in some fw versions. I suppose that with particular 'bad' fw version the modem may just refuse the right code. I suggest to load the generic (non-operator, not branded) firmware.

devianceluka

@AndrewZ:

I know that some commands are locked in some fw versions. I suppose that with particular 'bad' fw version the modem may just refuse the right code. I suggest to load the generic (non-operator, not branded) firmware.

Good news, long story short: I got the OEM code and I get "OK" when I enter it with AT^DATALOCK.
But bad news is, that:
"
AT^SETPORT? = Recieve: ^SETPORT:A1,A2;A3,A2
"
AT^SETPORT=?
AT^SETPORT="A1,A2;1,2,3"
AT^SETPORT="A1,A2;A3,A2"
AT^U2DIAG=0
" = all throw ERROR

What now?

AndrewZ

I can only repeat what was said earlier:

I do not own such a modem myself, so I can only try to help basing on my previous experience with the similar modems.
I know that some commands are locked in some fw versions. I suggest to load the generic (non-operator, not branded) firmware. No guarantee it will help though.

And as always - please mention the firmware version used in all [un]success stories.

el-quique

It works on e3131 . Thank you

The only thing to work I had to modify the file lte.cfg

from
MessageContent="55534243123456780000000000000a1106200000000000010000000000000$

to
MessageContent="55534243123456780000000000000a11062000000000000100000000000000"

:)

Xamaba

Thank you I noticed the string was clipped when I pasted it.

@el-quique:

It works on e3131 . Thank you

The only thing to work I had to modify the file lte.cfg

from
MessageContent="55534243123456780000000000000a1106200000000000010000000000000$

to
MessageContent="55534243123456780000000000000a11062000000000000100000000000000"

:)