[HansAnders]

Hi Dragonbender,

I got it working by inserting some delay in the udev rule:

Code: Select all

# Huawei E3372-325

ACTION!="add", GOTO="modeswitch_rules_end"
SUBSYSTEM!="usb", GOTO="modeswitch_rules_end"

# All known install partitions are on interface 0
ATTRS{bInterfaceNumber}!="00", GOTO="modeswitch_rules_end"

# only storage class devices are handled; negative
# filtering here would exclude some quirky devices
ATTRS{bDeviceClass}=="e0", GOTO="modeswitch_rules_begin"
ATTRS{bInterfaceClass}=="e0", GOTO="modeswitch_rules_begin"

GOTO="modeswitch_rules_end"

LABEL="modeswitch_rules_begin"

ATTRS{idVendor}=="3566", ATTRS{idProduct}=="2001", RUN+="/usr/bin/at -M -f /root/modeswitch.sh now"

LABEL="modeswitch_rules_end"

modeswitch.sh :

Code: Select all

#!/usr/bin/sh

/sbin/usb_modeswitch -v 3566 -p 2001 -W -R -w 400
/sbin/usb_modeswitch -v 3566 -p 2001 -W -R

I have a PI3 running bullseye.
Maybe you have to adjust the (at) delay a bit for a PI4.
Hope this works for you too!
Better than a MOSFET ....

Hans

[Pacjukajtys]

Hi,

Has anyone managed to get the modem to run on RPI4?
I have a working modem with hot plugging. But when I restart RPI4, the modem can't catch the signal.

[sam_em]

Hi, thanks for all your input, works fine with Rasp 4 Bullseye. However, i need to get it to work on Raspberry Pi Os 10 (Buster), i've tried everything but nothing seems to work, sometimes i even get an IP but the Brovi never seems to care.. anyone suceeded working with Buster? Thanks!

[ernstp]

There's a new firmware update out called something something SP19 something. It seems to have enabled an additional USB endpoint with cdc_ether support.

[ThoLag]

With the above tipps, I've managed to get a stable connection for about 48 hours, thanks a lot to everyone!
The stick then disconnects from the internet without any reason, it's just a hint on the first page "internet disconnected" until it's being powered off.

- Did anyone experience the same issue and found a solution?
- Did anyone ever receive an update to this stick's software?
(I use Hardware CL5E3372M, 3.0.2.61 - H057SP7C983 seems to be the latest online update while 3.0.2.62 seems to be available elsewhere...)

[Pexeus]

I normally never do this but ive been stuck on this for 3 days and so heres the way:

The problem is, the stick needs the modeswitch right after it registers, thats why it works on replug, but not on boot.
So you need a service that starts early in the boot process and waits for the stick to register to the system.

I got it working with this service:

Code: Select all

[Unit]
Description=Stick
DefaultDependencies=no
Before=local-fs.target

[Service]
ExecStart=/usr/local/bin/stick_startup.sh

[Install]
WantedBy=sysinit.target

and this script:

Code: Select all

#!/bin/bash

while true; do
    echo "checking devices..."

    if [[ $(lsusb -d 3566:2001) ]]; then
        echo "Huawei E3372-325 detected. Performing mode switch..."
        /sbin/usb_modeswitch -v 3566 -p 2001 -W -R -w 400
        /sbin/usb_modeswitch -v 3566 -p 2001 -W -R
        echo "Mode switch completed."
        break
    fi
    sleep 1  # Wait for 1 second before checking again
done

[BuGgZzY]

Hi,

I'm trying now for about one week to get my setup up and running and had no luck. What I need is:
- connect by wvdial
- reconnect internet connection on restart
- read SMS with smstools, because I want to trigger events on sms (like reboot)
- optional: sens SMS

Hardware/Software:
- Raspberry Pi 4B with Raspbian GNU/Linux 11 (bullseye)
- Brovit Stick (E3372-325, firmware revision: 3.0.2.61(H057SP5C983), I've checked already if there is a new firmware available, but the webinterface of the brovit stick said it's already the latest
- WvDial 1.61
- smstools 3.1.21

I've tried already everything from this forum, but the /dev/ttyUSB* devices will never generated.

Maybe someone can give me a short guide.


Best regards
Carsten

[darkridge]

I have this brovi E3372-325 and I cannot get it to work. I followed all posts in this thread and many others - with not luck.

I plugged the stick into a Mac. There it works. No updates available.

This is what I have: debian 10, brovi E3372-325, latest usb_modeswitch.

This is plexeus' script which I ran as root:

Code: Select all

#!/bin/bash

while true; do
    echo "checking devices..."

    if [[ $(lsusb -d 3566:2001) ]]; then
        echo "Huawei E3372-325 detected. Performing mode switch..."
        /sbin/usb_modeswitch -v 3566 -p 2001 -W -R -w 400
        /sbin/usb_modeswitch -v 3566 -p 2001 -W -R
        echo "Mode switch completed."
        break
    fi
    sleep 1  # Wait for 1 second before checking again
done

Then I plugged in the stick. Here is the output:

Code: Select all

Huawei E3372-325 detected. Performing mode switch...
Take all parameters from the command line

 * usb_modeswitch: handle USB devices with multiple modes
 * Version 2.6.0 (C) Josua Dietze 2017
 * Based on libusb1/libusbx

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x3566
DefaultProduct= 0x2001

Look for default devices ...
  found USB ID 8087:8001
  found USB ID 1d6b:0002
  found USB ID 1d6b:0003
  found USB ID 04f2:b45d
  found USB ID 8087:0a2a
  found USB ID 138a:0017
  found USB ID 0bdb:193e
  found USB ID 1ea7:0066
  found USB ID 3566:2001
   vendor ID matched
      product ID matched
  found USB ID 1d6b:0002
 Found devices in default mode (1)
Access device 011 on bus 002
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
 with class 224

USB description data (for identification)
-------------------------
Manufacturer: Mobile
     Product: Mobile
  Serial No.: 123456789ABCD
-------------------------
Warning: no switching method given. See documentation
Reset USB device ........... Reset USB device failed with error -4-> Run lsusb to note any changes. Bye!

Take all parameters from the command line


 * usb_modeswitch: handle USB devices with multiple modes
 * Version 2.6.0 (C) Josua Dietze 2017
 * Based on libusb1/libusbx

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x3566
DefaultProduct= 0x2001

  found USB ID 8087:8001
  found USB ID 1d6b:0002
  found USB ID 1d6b:0003
  found USB ID 04f2:b45d
  found USB ID 8087:0a2a
  found USB ID 138a:0017
  found USB ID 0bdb:193e
  found USB ID 1ea7:0066
  found USB ID 1d6b:0002
 No devices in default mode found. Nothing to do. Bye!

Mode switch completed.   
   

No network device or anything presend.

With the following command I get a network device but to no avail.

Code: Select all

/sbin/usb_modeswitch -v 3566 -p 2001 -X

Any help or ideas would be appreciated.

[abhay]

/etc/udev/rules.d/40-huawei.rules:
# This is part of USB_ModeSwitch version 1.x.x
#
ACTION!="add", GOTO="modeswitch_rules_end"
SUBSYSTEM!="usb", GOTO="modeswitch_rules_end"

# All known install partitions are on interface 0
ATTRS{bInterfaceNumber}!="00", GOTO="modeswitch_rules_end"

# only storage class devices are handled; negative
# filtering here would exclude some quirky devices
ATTRS{bDeviceClass}=="e0", GOTO="modeswitch_rules_begin"
ATTRS{bInterfaceClass}=="e0", GOTO="modeswitch_rules_begin"
GOTO="modeswitch_rules_end"

LABEL="modeswitch_rules_begin"
# Huawei E3372-325
ATTRS{idVendor}=="3566", ATTRS{idProduct}=="2001", RUN+="/sbin/usb_modeswitch -v 3566 -p 2001 -W -R -w 400"
ATTRS{idVendor}=="3566", ATTRS{idProduct}=="2001", RUN+="/sbin/usb_modeswitch -v 3566 -p 2001 -W -R"

LABEL="modeswitch_rules_end"

This worked for me! Thank you very much.

Okay, the device works but it does not reconnect after a reboot. Device works again after replugging. Will submit logs later.

Same issue with me. device works by adding udev rules. but after reboot its not working without replugging. Anyone found the solution? please help!

[zermok]

is anyone solve this issue? I have the same with huawei E3372h-510....
btw it's on RB but also Linux with kernel 6.6.1
thanks

[rami]

I want to share the setup that worked on my rpi 4 flashed with bookworm. Thanks a lot to everyone in this thread and especially to [kraev][memberlist.php?mode=viewprofile&u=4338] and to [Pexeus][memberlist.php?mode=viewprofile&u=4467].
Add a new NetworkManager connection (Let’s call it lte-stick):

Code: Select all

nano /etc/NetworkManager/system-connections/lte-stick.nmconnection

Paste the following:

Code: Select all

[connection]
id=lte-stick
uuid=83eba70d-820a-4a6e-9d9b-589917becc2e
type=ethernet
interface-name=usb0

[ethernet]

[ipv4]
method=auto
route-metric=0

[ipv6]
addr-gen-mode=default
method=auto
route-metric=0

[proxy]

We need udev rules to switch the lte stick from storage into hi-link mode when plugged in.

[code]nano /etc/udev/rules.d/40-huawei.rules

Paste the following

Code: Select all

# This is part of USB_ModeSwitch version 1.x.x
#
ACTION!="add", GOTO="modeswitch_rules_end"
SUBSYSTEM!="usb", GOTO="modeswitch_rules_end"

# All known install partitions are on interface 0
ATTRS{bInterfaceNumber}!="00", GOTO="modeswitch_rules_end"

# only storage class devices are handled; negative
# filtering here would exclude some quirky devices
ATTRS{bDeviceClass}=="e0", GOTO="modeswitch_rules_begin"
ATTRS{bInterfaceClass}=="e0", GOTO="modeswitch_rules_begin"
GOTO="modeswitch_rules_end"

LABEL="modeswitch_rules_begin"
# Huawei E3372-325
ATTRS{idVendor}=="3566", ATTRS{idProduct}=="2001", RUN+="/sbin/usb_modeswitch -v 3566 -p 2001 -W -R -w 400"
ATTRS{idVendor}=="3566", ATTRS{idProduct}=="2001", RUN+="/sbin/usb_modeswitch -v 3566 -p 2001 -W -R"

LABEL="modeswitch_rules_end"

The problem now is that the connection is only succesfully established after replugging the stick.

The problem is, the stick needs the modeswitch right after it registers, thats why it works on replug, but not on boot.
So you need a service that starts early in the boot process and waits for the stick to register to the system.

To fix this, we need a service that monitors when the stick is connected on boot:

Code: Select all

sudo nano /etc/systemd/system/stick_startup.service

Paste the following:

Code: Select all

[Unit]
Description=Stick
DefaultDependencies=no
Before=local-fs.target

[Service]
ExecStart=/usr/local/bin/stick_startup.sh

[Install]
WantedBy=sysinit.target

Create this script:

Code: Select all

sudo nano /usr/local/bin/stick_startup.sh

Paste the following:

Code: Select all

#!/bin/bash

while true; do
    echo "checking devices..."

    if [[ $(lsusb -d 3566:2001) ]]; then
        echo "Huawei E3372-325 detected. Performing mode switch..."
        /sbin/usb_modeswitch -v 3566 -p 2001 -W -R -w 400
        /sbin/usb_modeswitch -v 3566 -p 2001 -W -R
        echo "Mode switch completed."
        break
    fi
    sleep 1  # Wait for 1 second before checking again
done

Save the file and make it executable:

Code: Select all

sudo chmod +x /usr/local/bin/stick_startup.sh

Reload systemd to pick up the changes:

Code: Select all

sudo systemctl daemon-reload

Enable the service to start on boot:

Code: Select all

sudo systemctl enable stick_startup.service

Now, after rebooting, NetworkManager should establish an internet connection using the brovi stick.

[rosydam]

/etc/udev/rules.d/40-huawei.rules:
# This is part of USB_ModeSwitch only up version 1.x.x
#
ACTION!="add", GOTO="modeswitch_rules_end"
SUBSYSTEM!="usb", GOTO="modeswitch_rules_end"

# All known install partitions are on interface 0
ATTRS{bInterfaceNumber}!="00", GOTO="modeswitch_rules_end"

# only storage class devices are handled; negative
# filtering here would exclude some quirky devices
ATTRS{bDeviceClass}=="e0", GOTO="modeswitch_rules_begin"
ATTRS{bInterfaceClass}=="e0", GOTO="modeswitch_rules_begin"
GOTO="modeswitch_rules_end"

LABEL="modeswitch_rules_begin"
# Huawei E3372-325
ATTRS{idVendor}=="3566", ATTRS{idProduct}=="2001", RUN+="/sbin/usb_modeswitch -v 3566 -p 2001 -W -R -w 400"
ATTRS{idVendor}=="3566", ATTRS{idProduct}=="2001", RUN+="/sbin/usb_modeswitch -v 3566 -p 2001 -W -R"

LABEL="modeswitch_rules_end"

I tried this but it doesn't seem like the usb_modeswitch get's triggered. My device never seems to have bDeviceClass == "e0" or bInterfaceClass == "e0". I'm running Ubuntu 20.04.

I think so

[saveinsta1]

While the temptation to instagram video download online may be strong, it's crucial to navigate this territory with respect for privacy and copyright. Instagram's built-in features offer a safe and legal way to save your own content