rtl_eepromto successfully write a different S/N to my Nooelec NESDR Mini 2+.
rtl_eeprom -s 00000001
rtl_eeprom -s 00000002
FCIV -sha1hashes of the relevant files are:
rtl_eeprom -r dump.binresults in similar errors and gibberish in the Manufacturer, Product, etc.? I don't think there's a solution then, unless someone else has written a different EEPROM reader/writer that works correctly with that particular hardware.
Writing bad information to the EEPROM will make your device useless.
Glad you got it going, and that's good information to know for future reference if somebody else has the same problem. I saw that option in the man page but they didn't have a listing for nooelec so I didn't know if that would work or brick your particular device or not. Has SDRTrunk been working the way you'd expect it to work since you got it straightened out?Thanks for all the help. I reached out to Nooelec support and I needed to run rtl_eeprom -g realtek and then I was able to run rtl_eeprom -s 00000001. I now have the serial number enabled and written on both SDR tuners.
Yeah, me too. However, looking at the dumps I did of my RTL-SDR.comv2 and NooElec Mini2+, the only diff between them was that the NooElec has 0xA0 instead of 0x00 at positions 0xA0 and 0xA1. @estone4009: Did/would you do a dump (with.. I saw that option [-g] in the man page but they didn't have a listing for nooelec so I didn't know if that would work or brick your particular device or not. ...
rtl_eeprom -r dump.bin) and would you PM it to me? I'd like to see what the difference is between it and the factory firmware. Unfortunately,
rtl_eepromdoesn't have an option to write the
-gresult to a file instead of the device itself and I'd rather not risk bricking a working device.