Cylarcy
Posts: 11
Joined: Fri Oct 05, 2012 11:50 pm

Huawei E303 Error PIN

Tue Jun 07, 2016 7:27 am

hi all,

i am using Raspbian Jessie on Rpi3 and a USB hub.

i have downloaded sakis3g and i use the switch modem to change the stick to a 3g stick.

Now it shows as Bus 001 Device 012: ID 12d1:1c05 Huawei Technologies Co., Ltd. E173s 3G broadband stick (modem on)

when i try to connect with sakis it gives me an error:

Modem responded "ERROR" while checking for PIN.

I also defined the pin code in /etc.sakis3g.conf but still the same error.

I followed all guides found on the internet for switching the modem but its always the same result.

The debug output from sakis is :

[07247] [07:26:46] Modem did not report a name.
[07247] [07:26:46] Unknown command "STAGE1".
[07247] [07:26:46] Using default PINCHECK.
[07247] [07:26:46] Command "PINCHECK" refers to AT commands: 'AT+CPIN?' OK
[07247] [07:26:46] Will send PINCHECK commands to tty /dev/ttyUSB0: "" '\pAT' OK 'AT+CPIN?' OK '\pAT' OK
[07247] [07:26:46] We are root already. Proceeding.
[07247] [07:26:46] Device /dev/ttyUSB0 is not busy.
[07247] [07:26:48] Got response from tty:

[07247] [07:26:48] Got "ERROR" while checking modem on /dev/ttyUSB0 for PIN requirement.
[07247] [07:26:48] Error: Modem responded "ERROR" while checking for PIN.
[07247] [07:26:59] Error: Failed to connect.

Strange fact is when i dont use the hub it doesnt work at all probably because of lack of power.

Note: It used to work fine on Rasbian Wheezy.

any tips?

jayakarthigeyan
Posts: 1
Joined: Wed Jul 13, 2016 1:11 pm

Re: Huawei E303 Error PIN

Wed Jul 13, 2016 1:17 pm

Hi,

How did you get your Huawei E303 to be recognized first on your pi3. Its not showing up at all even in the lsusb. It shows up sometimes and goes away after some time. I tried giving it an external USB hub with power supply also but same issue. It works fine with Raspbian Wheezy on Pi 3, but doesn't work with Jessie on Pi 3. Any leads for me to make my E303 usb dongle to get recognized and work on Raspbian Jessie?

Return to “Troubleshooting”