Important note about upgrading HD300 firmware to version 20110506 0

[Opus4]

There is a known issue that can prevent the HD300 firmware upgrade from completing successfully when upgrading from a beta firmware version prior to version "20110506 0". (For details on beta firmware "20110506 0", see this post.)


Symptom: While upgrading the beta firmware, the HD300 may stop on the screen telling you that the upgrade is in process & not to turn the unit off.


Solution: Use the Service Menu to reload the previous release version of the firmware, then upgrade to the latest beta firmware version "20110506 0".

For details on how to use the service menu, see the HD300 PDF manual "Configuration Reset Procedure" on p. 11 or this FAQ. Use the option to reload the firmware "From Internet" in order to reload the latest release version. Once the release version has been reloaded, you should be able to then upgrade to the beta firmware version "20110506 0".


Alternative solutions:

1. While the HD300 appears to be locked during the beta firmware upgrade process, do the following:
   1. telnet into the unit
   2. login as 'root'
   3. type this command:
      
      /sbin/updateflash /tmp/firmware.bin
   
   
2. Use the Service Menu to load the latest beta firmware directly - download the files from the beta firmware announcement and see this FAQ regarding how to rename the files to load them from the service menu via either the "From SageTV Server" or the "From USB" option.

- Andy

[cat6man]

hi,

can you also confirm that the new beta update will succeed if we first take the hd300 back to the last non-beta release?

thanks

[HelenWeathers]

Originally Posted by cat6man

hi,

can you also confirm that the new beta update will succeed if we first take the hd300 back to the last non-beta release?

thanks

That's what I did - prev NR then new beta - beta loaded w no problem

[cat6man]

Originally Posted by HelenWeathers

That's what I did - prev NR then new beta - beta loaded w no problem

strange......prev NR has hung on me twice now, so that doesn't work here

[Graygeek]

Originally Posted by cat6man

strange......prev NR has hung on me twice now, so that doesn't work here

+1 .. doesn't work here either

[cat6man]

however, telnet approach (per above) to updating flash worked fine...........i'm now happily on latest beta, which seems to fix my (bug reported) hdmi audio click problem when skipping ahead/back

[Opus4]

Originally Posted by cat6man

can you also confirm that the new beta update will succeed if we first take the hd300 back to the last non-beta release?

You can revert to the previous release version from the service menu.

The issue is that there can be a problem during the upgrade process to any firmware version while using the previous beta firmware - i.e.: the firmware update issue is with the previous beta firmware, not the new beta firmware.

- Andy

[rugerp90]

I can confirm that going back to the latest stable firmware (20101007 0) and then updating to the new beta worked for me.

[EasyME]

Originally Posted by cat6man

however, telnet approach (per above) to updating flash worked fine...........i'm now happily on latest beta, which seems to fix my (bug reported) hdmi audio click problem when skipping ahead/back

+1
Reverting back to old firmware would freeze and not reboot.
The telnet approached worked great.

Thanks.

[Graygeek]

Originally Posted by EasyME

+1
Reverting back to old firmware would freeze and not reboot.
The telnet approached worked great.

Thanks.

+2 ... only telnet worked for both HD300's

[bits]

Where are the instructions for telnetting into the HD300?

[Graygeek]

Originally Posted by bits

Where are the instructions for telnetting into the HD300?

See "Alternative solutions:" A in the first post above by Opus

[wayner]

Is this just a bug in the "20110506 0" firmware or will we always have this problem when upgrading? In other words - should I skip this firmware update and hope that it is resolved in the next version?

[sleonard]

Originally Posted by wayner

Is this just a bug in the "20110506 0" firmware or will we always have this problem when upgrading? In other words - should I skip this firmware update and hope that it is resolved in the next version?

Try reading a few posts up.

S

[bits]

Originally Posted by Graygeek

See "Alternative solutions:" A in the first post above by Opus

That tells me to telnet, not how to telnet. I have never telnet'd into my HD300 so I need specific instructions on how to do that.

[carlgar]

Originally Posted by bits

That tells me to telnet, not how to telnet. I have never telnet'd into my HD300 so I need specific instructions on how to do that.

It looks like you are running windows 7. If so, you may need to install telnet. use the windows help and find "Telnet: frequently asked questions".
Once you have telnet installed, you need to determine the IP address of the HD300. Then bring up the DOS command prompt window and enter telnet followed by the IP address. Example:telnet 192.168.1.88
You should then get the login prompt from the HD300.

[bits]

Originally Posted by carlgar

It looks like you are running windows 7. If so, you may need to install telnet. use the windows help and find "Telnet: frequently asked questions".
Once you have telnet installed, you need to determine the IP address of the HD300. Then bring up the DOS command prompt window and enter telnet followed by the IP address. Example:telnet 192.168.1.88
You should then get the login prompt from the HD300.

Thank you!

[gplasky]

Originally Posted by wayner

Is this just a bug in the "20110506 0" firmware or will we always have this problem when upgrading? In other words - should I skip this firmware update and hope that it is resolved in the next version?

It doesn't affect everyone. I upgraded from the previous beta firmware to the latest and it just worked as it always does.

Gerry

[carlgar]

Originally Posted by gplasky

It doesn't affect everyone. I upgraded from the previous beta firmware to the latest and it just worked as it always does.

Gerry

I can confirm this. I went back to the non-beta firmware at least once, before I was hit the next time I tried. I suspect this bug is related to memory being overwritten. I suspect the wireless issues I am still seeing with this new firmare are caused by a memory related issue. I was able to run for almost a full day in wireless mode before seeing random issues. I am now back to running wired until the next firmware release.

[Opus4]

Originally Posted by carlgar

I suspect this bug is related to memory being overwritten.

No, this potential stuck-while-upgrading issue has nothing to do with any sort of memory issue.

- Andy