MobileRead Forums - View Single Post - Firmware Update Problem with Firmware 3.0.2 for K3

sirmaru · 11-14-2010, 09:24 AM

I had two spontaneous resets with Firmware 3.0.2 for the Kindle WiFi 3: one on 11/3/2010 and the other on 11/14/2010.

I then upgraded to Firmware 3.0.3 (536720111).

However, while connecting the K3 to the PC via the USB port with 3.0.2 active, it showed the Kindle drive as normal but it listed another device under "Other." It was not listed with Drives or Devices with Removable Storage. The Kindle drive was shown under Devices with Removable Storage.

I unmounted the Kindle drive but that "Other" device remained and could not be removed. On rebooting that "Other" device disappeared. Thus, it was only present when 3.0.2 was in place while connecting to the PC.

After 3.0.3 was installed I connected to the PC again and that "Other" device did not show up. It had not been present for 3.0.0 or 3.0.1. It was unique to 3.0.2.

I mention this because this may have been a bug in 3.0.2 and then upgrading to 3.0.3 is more of a necessity even though it is still in a beta (preview) test.

11-14-2010, 09:24 AM	#1
sirmaru Wizard Posts: 2,426 Karma: 6561538 Join Date: Nov 2007 Device: Kindle PW 2013, HDX 2013, Galaxy S5 2014	Problem with Firmware 3.0.2 for K3 I had two spontaneous resets with Firmware 3.0.2 for the Kindle WiFi 3: one on 11/3/2010 and the other on 11/14/2010. I then upgraded to Firmware 3.0.3 (536720111). However, while connecting the K3 to the PC via the USB port with 3.0.2 active, it showed the Kindle drive as normal but it listed another device under "Other." It was not listed with Drives or Devices with Removable Storage. The Kindle drive was shown under Devices with Removable Storage. I unmounted the Kindle drive but that "Other" device remained and could not be removed. On rebooting that "Other" device disappeared. Thus, it was only present when 3.0.2 was in place while connecting to the PC. After 3.0.3 was installed I connected to the PC again and that "Other" device did not show up. It had not been present for 3.0.0 or 3.0.1. It was unique to 3.0.2. I mention this because this may have been a bug in 3.0.2 and then upgrading to 3.0.3 is more of a necessity even though it is still in a beta (preview) test.