RP-WD03: Exist a Variant? I have a Wifi Hardware issue

Hello @ all,

I used a RP-WD03 with OpenWRT 18.06 at work since it fell down a boiler platform and broke. I quickly purchased an other one and installed out of the box 19.06, which on a second "Play"-device works great. On the new one I have no Wifi, the Kern-log says:

[   10.200479] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device "factory"
[   10.207933] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 6352, rev 0500 detected
[   10.215852] ieee80211 phy0: rt2800_init_eeprom: Error - Invalid RF chipset 0xffff detected
[   10.224321] ieee80211 phy0: rt2x00lib_probe_dev: Error - Failed to allocate device

I exported mtd2 from the working device and from that without wifi to compare them, it seems that on the device with wifi the mtd2-partition is almost empty and on that without wifi there is a lot more data in. Don't know what kind of. mtd1 and mtd3 are different, too. I hesitate to simply try to write the mtd2 of the working device to that without wifi or vice versa to test if there is the fault. Does anybody know a solution of getting Wifi to work?

After things have gone wrong I noticed that the battery capacity is given with 6700 mAh on that one without wifi rather than 6000 mAh on the fully working one, the rest is identical (except the serial number of course) Is there a second version known? The Ravpower website gives no hint on that, there is even only one firmware file (Does it mean anything?).

Best regards

make a backup of both devices and post here before you overwrite some required partition

From which partition or file?

Buggy.OpenWrt.mtd2.bin is the factory mtd of the WD03 without wifi
Running.OpenWrt.mtd2.bin_factory is the one that works.

To be complete, Buggy.OpenWrt.mtd1.bin and Buggy.OpenWrt.mtd3.bin are the other partitions from that one without wifi, Running.OpenWrt.mtd1.bin_u-boot-env and Running.OpenWrt.mtd3.bin_firmware are from that one that works. The other mtd blocks or partitions are identical on both devices as mentioned earlier according to a "diff -s".


ok just reflash it with the one from working device. and tell the manufacurer to stop fooling around with meaningless ideas