Bricked SDR?

[hockeyref2]

Hello,
I have an RTL-SDR v3. I used RelWithDebInfo (rtl_eeprom) to attempt to change the serial # of the receiver... The drivers seem to be installed properly but the SDR is now not seen with rtl_test, unitrunker or SDR#.

ZADIG shows a "RTL2838UHIDIR" device with WinUSB 6.1 drivers installed. I have tried reinstalling drivers several times. Rebooting etc. Even tried it on a different PC that has never had a SDR on it. At one point, it was showing "bulk-in interface 0" and "bulk-in interface 1" at the same time in both zadig and device manager....

I uninstalled in device manager, and reinstalled drivers multiple times.

If I run RTL_TEST, it just says no devices....

Any thoughts on what to try, or what to look at to get it working again?

Thanks!

 

[foxtail]

Try doing the eprom again...reflash the eeprom, if you can see it.
Or try in a linux pc.

 

[boatbod]

Had this happen to me once. Luckily I was able to use the same utility to read the config out of another rtl device and then write it back in to the "bricked" device. Worked like a charm after that.

 

[hockeyref2]

It is not seen on my RPi3 either, so I cannot write anything to it... Thanks.

 

[boatbod]

It is not seen on my RPi3 either, so I cannot write anything to it... Thanks.

Ugh, that sucks. Does it show up with 'lsusb'?

 

[hockeyref2]

Ugh, that sucks. Does it show up with 'lsusb'?

Actually yes.... to an extent..

pi@raspberrypi:/etc $ lsusb
Bus 001 Device 005: ID 00a0:2838

In comparison, my flightaware pro says Bus 001 Device 006: ID 0bda:2832 Realtek Semiconductor Corp. RTL2832U DVB-T

Any other thoughts? I already ordered a new one, but it would be nice if I could get it working again. Thanks for your help!

 

[boatbod]

Actually yes.... to an extent..

pi@raspberrypi:/etc $ lsusb
Bus 001 Device 005: ID 00a0:2838

In comparison, my flightaware pro says Bus 001 Device 006: ID 0bda:2832 Realtek Semiconductor Corp. RTL2832U DVB-T

Any other thoughts? I already ordered a new one, but it would be nice if I could get it working again. Thanks for your help!

So rtl_eeprom does not see the device at all? When I bricked mine I was fortunately still able to access it with rtl_eeprom even though the kernel couldn't load the proper driver.

 

[hockeyref2]

No, none of the rtl_ commands I tried saw it.
Thanks

 

[boatbod]

No, none of the rtl_ commands I tried saw it.
Thanks

Sadly there's probably not a lot you can do. I assume you already tried plugging it in a different machine to see if that would recognize it?