FlightAware Discussions

Bricked Pro Stick just from setting serial numbers?

I wanted to add an orange 978 dongle to my RasPi setup, and serialized my blue Pro Stick Plus as 00001090 and the orange Pro Stick as 00000978 as per the instructions found in various threads. However, after rebooting the Pi, neither one was detected. I even tried using a different Pi, and rtl_test comes back with “No supported devices found.” However, dmesg shows the device:

[ 1610.715247] usb 1-1.1.2: new high-speed USB device number 7 using dwc_otg
[ 1610.856981] usb 1-1.1.2: New USB device found, idVendor=41a0, idProduct=28a0, bcdDevice= 1.00
[ 1610.857001] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1610.857015] usb 1-1.1.2: Product: RTL2832U
[ 1610.857028] usb 1-1.1.2: Manufacturer: Realtek
[ 1610.857041] usb 1-1.1.2: SerialNumber: 00001090

Did I brick both my dongles just by trying to set separate serial numbers?

Try with only one connected, make sure you completely power cycle it so it all reads correctly.


sudo rtl_test

If it says claim error then you have something else using it.
Or you’re using a really old Raspbian …

Completely power cycled, only the blue dongle connected:

pi@adsb:~ $ sudo rtl_test
No supported devices found.

I think you can try connecting in Windows and maybe there resetting the serial number.
Not sure.

Or see if the utility to write the serial number will find it.
I haven’t dealt with this issue.

@abcd567 i remember you dealing with something like this at some point?

Those vendor/product IDs don’t look right (and librtlsdr finds the dongle by those IDs, so if they’re wrong, it won’t find the dongle). They are read from the EEPROM. Check your rtl_eeprom settings.

(You will probably have difficulty getting rtl_eeprom to talk to the dongle now, since it also won’t recognize it… You may need to recompile librtlsdr with those wrong IDs to make it work)


Please see these two posts:



I did a little more testing, and it appears that my orange dongle is still able to be found by rtl_test and rtl_eeprom. So it’s just the blue dongle that is misbehaving, I think. I did find abcd567’s posts on using “rtl1090.exe /eeprom” on Windows, but the dongle wasn’t recognized by rtl1090 there either.

@obj thanks for the tip on the VID/PID being used to identify. Do you know what they should be for a Pro Stick Plus v1.0? (sticker on the side indicates Mar. 2017 manufacture)

The default values are (IIRC) VID=0x0BDA, PID=0x2832

Full list of values that librtlsdr recognizes

1 Like