Activation Codes and Methods, Hardware Details, Sniffing
Post Reply
merla
Posts: 4
Joined: 14 Sep 2013, 12:28

FRITZ!WLAN USB Stick N v2

Post by merla » 14 Sep 2013, 13:04

This device is stuck in CD-Rom mode by default on my Kubuntu 13.04 system.

Code: Select all

Bus 001 Device 005: ID 057c:62ff AVM GmbH AVM Fritz!WLAN USB (in CD-ROM-mode)
Windows 7 device manager lists the same usb device as:

Code: Select all

USB\VID_057C&PID_8501&REV_0413
USB\VID_057C&PID_8501
fwlanusb5
FRITZ!WLAN USB Stick N v2
using the message from

Code: Select all

# AVM Fritz!Wlan USB Stick N

TargetVendor=  0x057c
TargetProduct= 0x8401

MessageContent="5553424312345678000000000000061b000000ff0000000000000000000000"
doesn't trigger the switch on my newer revision of the product.

since http://www.pcausa.com/Utilities/UsbSnoop/default.htm , from http://blogger.ziesemer.com/2008/10/all ... buntu.html is said to not work on windows 7 i used
http://blogs.msdn.com/usbcoreblog/archi ... stack.aspx

Unfortunately i haven't been able yet to find the magic MessageContent that would trigger the switch.

merla
Posts: 4
Joined: 14 Sep 2013, 12:28

Re: FRITZ!WLAN USB Stick N v2

Post by merla » 03 Oct 2013, 17:30

i obviously made the classic mistake and forgot the "-I" when testing on the command line :oops:
I made a copy of the original file and adjusted it to the new v2 revision of the hardware.

filecontent of: 057c:62ff

Code: Select all

# AVM Fritz!Wlan USB Stick N v2

TargetVendor=  0x057c
TargetProduct= 0x8501

MessageContent="5553424312345678000000000000061b000000ff0000000000000000000000"

NoDriverLoading=1
Attachments
057c_62ff.txt
(176 Bytes) Downloaded 1064 times

Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Re: FRITZ!WLAN USB Stick N v2

Post by Josh » 12 Oct 2013, 08:51

Thanks a lot for the report!

I'm actually thinking about reversing the logic of the -I parameter in future releases ...

merla
Posts: 4
Joined: 14 Sep 2013, 12:28

Re: FRITZ!WLAN USB Stick N v2

Post by merla » 16 Mar 2014, 20:52

The new AC 430 uses the same id for the cdrom mode but comes out as pid 8502 in the end, would that cause any issues with usb_modeswitch?

merla
Posts: 4
Joined: 14 Sep 2013, 12:28

Re: FRITZ!WLAN USB Stick N v2

Post by merla » 08 May 2014, 19:18

i think the file needs to be updated for the new wifi dongle in the following way
Attachments
057c_62ff_v2.txt
(184 Bytes) Downloaded 1037 times

LOM
Posts: 1404
Joined: 11 Jul 2012, 15:14
Location: Koh Samui, TH

Re: FRITZ!WLAN USB Stick N v2

Post by LOM » 09 May 2014, 05:27

Thanks for the report, the additional id will be included in the next update of the usb_modeswitch data package.

Have you ever tried the standard cdrom eject message on these two devices?
The only difference between your msg and the std eject msg is only one byte, your "ff" is "02" in std eject.

bemk
Posts: 1
Joined: 07 Jul 2016, 14:09

Re: FRITZ!WLAN USB Stick N v2

Post by bemk » 07 Jul 2016, 14:47

In my current release (20160112) the file included is as follows:

Code: Select all

# AVM Fritz!Wlan USB Stick N v2                                                 
TargetVendor=0x057c
TargetProductList="8501,8502"
StandardEject=1
NoDriverLoading=1
This doesn't work as apparently the device doesn't listen for a standard eject message.
Adding in the above MessageContent line however seems to fix the issue.

Could you please include the following line in your next release for file 057c:62ff?

Code: Select all

MessageContent="5553424312345678000000000000061b000000ff0000000000000000000000"
Thanks for your time.

Kind regards,
Bart Kuivenhoven.

EDIT:
I almost forgot, you might also want to know what system I'm running.

A fresh Fedora 24 install on a 64-bits Intel machine.
Using version 2.3.0 of usb_modeswitch.

I scanned the source quickly but couldn't find a difference in message contents between the versions in terms of a standard eject though.

LOM
Posts: 1404
Joined: 11 Jul 2012, 15:14
Location: Koh Samui, TH

Re: FRITZ!WLAN USB Stick N v2

Post by LOM » 08 Jul 2016, 02:52

bemk wrote:I scanned the source quickly but couldn't find a difference in message contents between the versions in terms of a standard eject though.
The difference is the parameter given together with the 1b command, a parameter which can be 1 or 2 but not ff.
Fritz or his mfgr has abused a standardized command by giving it an invalid parameter instead of using any of the many cmds listed as mfgr specific.
Thanks for the report, we will revert back the config to contain ff as parameter in the next issue of the usb_modeswitch data package.

Post Reply