Talk:Non Flashable HD-HG300 - Revision history

Paddytb at 14:20, 18 December 2007

Paddytb — Tue, 18 Dec 2007 14:20:08 GMT

← Older revision		Revision as of 14:20, 18 December 2007
Line 1:		Line 1:
	* For some reason you cannot flash these HD-HG300 LinkStations with custom firmwares [[OpenLink]] and [[FreeLink]]. However the original <tt>'''firmimg.bin'''</tt> can be flashed via JTAG...maybe because it is smaller. Normal flashing via the Firmware Updater will create a brick.''Really? So how did this guy'' {{forumpost\|6\|342\| manage to produce his 4th brick in a row with a stock firmware?}}		* For some reason you cannot flash these HD-HG300 LinkStations with custom firmwares [[OpenLink]] and [[FreeLink]]. However the original <tt>'''firmimg.bin'''</tt> can be flashed via JTAG...maybe because it is smaller. Normal flashing via the Firmware Updater will create a brick.''Really? So how did this guy'' {{forumpost\|6\|342\| manage to produce his 4th brick in a row with a stock firmware?}}

-	*An alternative explanation is that this particular LS became popular at about the same time and sold well. Many people who didn't know what they where doing, and who couldn't follow instructions ("Disable '''all''' firewalls ...") tried to flash their shiny new LS. Instead of admitting they weren't up to the task they came up with the "some series must be broken!" excuse, and use isolated observations (defect flash prom in a single LS), to explain the theory.	+	*An alternative explanation is that this particular LS became popular at about the same time and sold well. Many people who didn't know what they where doing, and who couldn't follow instructions ("Disable '''all''' firewalls ...") tried to flash their shiny new LS. Instead of admitting they weren't up to the task they came up with the "some series must be broken!" excuse, and use isolated observations (defect flash prom in a single LS), to explain the theory. '''''I think this is unfair - if you read the thread posted above you'll see that the suggestion of a duff series was made by European Technical support, and that they bricked one them selves whilst trying to flash using the stock firmware. I'm not a Linux guru but I am a professional programmer and like to think I'm able to disable a firewall where necessary... PaddyTB'''''

	* The HG I repaired via JTAG uses the 2.4.31 kernel, telnet and ftp enabled firmware, and U-Boot. I was not able to repair it by flashing via U-Boot and had to use JTAG to install the new firmware, so there was something wrong or different about the hardware. Once U-boot and the new firmware were flashed via JTAG the HG worked perfectly. kuroguy		* The HG I repaired via JTAG uses the 2.4.31 kernel, telnet and ftp enabled firmware, and U-Boot. I was not able to repair it by flashing via U-Boot and had to use JTAG to install the new firmware, so there was something wrong or different about the hardware. Once U-boot and the new firmware were flashed via JTAG the HG worked perfectly. kuroguy

Ramuk at 07:09, 11 September 2007

Ramuk — Tue, 11 Sep 2007 07:09:53 GMT

← Older revision		Revision as of 07:09, 11 September 2007
Line 1:		Line 1:
-	* For some reason you cannot flash these HD-HG300 LinkStations with custom firmwares [[OpenLink]] and [[FreeLink]]. However the original <tt>'''firmimg.bin'''</tt> can be flashed via JTAG...maybe because it is smaller. Normal flashing via the Firmware Updater will create a brick.''Really? So how did this guy'' {{forumpost\|6\|342 manage to produce his 4th brick in a row with a stock firmware?}}	+	* For some reason you cannot flash these HD-HG300 LinkStations with custom firmwares [[OpenLink]] and [[FreeLink]]. However the original <tt>'''firmimg.bin'''</tt> can be flashed via JTAG...maybe because it is smaller. Normal flashing via the Firmware Updater will create a brick.''Really? So how did this guy'' {{forumpost\|6\|342\| manage to produce his 4th brick in a row with a stock firmware?}}

	*An alternative explanation is that this particular LS became popular at about the same time and sold well. Many people who didn't know what they where doing, and who couldn't follow instructions ("Disable '''all''' firewalls ...") tried to flash their shiny new LS. Instead of admitting they weren't up to the task they came up with the "some series must be broken!" excuse, and use isolated observations (defect flash prom in a single LS), to explain the theory.		*An alternative explanation is that this particular LS became popular at about the same time and sold well. Many people who didn't know what they where doing, and who couldn't follow instructions ("Disable '''all''' firewalls ...") tried to flash their shiny new LS. Instead of admitting they weren't up to the task they came up with the "some series must be broken!" excuse, and use isolated observations (defect flash prom in a single LS), to explain the theory.

Ramuk at 07:09, 11 September 2007

Ramuk — Tue, 11 Sep 2007 07:09:35 GMT

← Older revision		Revision as of 07:09, 11 September 2007
Line 1:		Line 1:
-	* For some reason you cannot flash these HD-HG300 LinkStations with custom firmwares [[OpenLink]] and [[FreeLink]]. However the original <tt>'''firmimg.bin'''</tt> can be flashed via JTAG...maybe because it is smaller. Normal flashing via the Firmware Updater will create a brick.''Really? So how did this guy ~~[http://forum.linkstationwiki.net/index.php?action=vthread&forum=~~6~~&topic=~~342~~&page=1#msg3504]~~ manage to produce his 4th brick in a row with a stock firmware?''	+	* For some reason you cannot flash these HD-HG300 LinkStations with custom firmwares [[OpenLink]] and [[FreeLink]]. However the original <tt>'''firmimg.bin'''</tt> can be flashed via JTAG...maybe because it is smaller. Normal flashing via the Firmware Updater will create a brick.''Really? So how did this guy'' {{forumpost\|6\|342 manage to produce his 4th brick in a row with a stock firmware?}}

	*An alternative explanation is that this particular LS became popular at about the same time and sold well. Many people who didn't know what they where doing, and who couldn't follow instructions ("Disable '''all''' firewalls ...") tried to flash their shiny new LS. Instead of admitting they weren't up to the task they came up with the "some series must be broken!" excuse, and use isolated observations (defect flash prom in a single LS), to explain the theory.		*An alternative explanation is that this particular LS became popular at about the same time and sold well. Many people who didn't know what they where doing, and who couldn't follow instructions ("Disable '''all''' firewalls ...") tried to flash their shiny new LS. Instead of admitting they weren't up to the task they came up with the "some series must be broken!" excuse, and use isolated observations (defect flash prom in a single LS), to explain the theory.

Davy gravy: /* Success followed by Failure (this turned out to be no issue at all - everything was resolved without JTAG, nothing even broken...) */

Davy gravy — Sat, 18 Nov 2006 14:15:56 GMT

Success followed by Failure (this turned out to be no issue at all - everything was resolved without JTAG, nothing even broken...)

← Older revision		Revision as of 14:15, 18 November 2006
Line 22:		Line 22:
	-- it was more a problem with the 2.6-kernel. while in 2.6-kernel, the flash is read only. so if you want to dd to the flash you need to get into the 2.4 kernel. [[User:85.124.221.56\|85.124.221.56]] 03:50, 17 November 2006 (EST)		-- it was more a problem with the 2.6-kernel. while in 2.6-kernel, the flash is read only. so if you want to dd to the flash you need to get into the 2.4 kernel. [[User:85.124.221.56\|85.124.221.56]] 03:50, 17 November 2006 (EST)

-	Followup: there was no damage or problem w/ the flash at all. As correctly pointed out by several folks, the 2.6 kernel that I was using doesn't support writing to flash.	+	Followup: there was no damage or problem w/ the flash at all. As correctly pointed out by several folks, the 2.6 kernel that I was using doesn't support writing to flash. I later did successfully flash my box w/ both U-Boot and a new 2.4.33.3 v3 firmimg.bin.

Davy gravy: /* Success followed by Failure */

Davy gravy — Sat, 18 Nov 2006 14:14:13 GMT

Success followed by Failure

← Older revision		Revision as of 14:14, 18 November 2006
Line 12:		Line 12:


-	==Success followed by Failure==	+	==Success followed by Failure (this turned out to be no issue at all - everything was resolved without JTAG, nothing even broken...) ==
	I've flashed a variety of Linkstations/relatives, with OpenLink and FreeLink. A Kuro, too. All successfully.		I've flashed a variety of Linkstations/relatives, with OpenLink and FreeLink. A Kuro, too. All successfully.
-	Flashed an old KuroHG to UBoot w/o incident, a great improvement. When I tried replicate the same type of flash on my LS-HG 250, the image did not write correctly to the flash chip, apparently. The image file has been confirmed to be valid, so after examining the output of dd, comp and od of the files, it is my guess that the chip was defective somehow. Or it is write-protected (I find this unlikely, though). I only know that the process was the same as that others used. It was double-check. It simply did not work on this machine. ~~SN 45801560710476F~~	+	Flashed an old KuroHG to UBoot w/o incident, a great improvement. When I tried replicate the same type of flash on my LS-HG 250, the image did not write correctly to the flash chip, apparently. The image file has been confirmed to be valid, so after examining the output of dd, comp and od of the files, it is my guess that the chip was defective somehow. Or it is write-protected (I find this unlikely, though). I only know that the process was the same as that others used. It was double-check. It simply did not work on this machine.

	Luckily this has a chance to be fixed w/ JTAG.		Luckily this has a chance to be fixed w/ JTAG.
Line 21:		Line 21:

	-- it was more a problem with the 2.6-kernel. while in 2.6-kernel, the flash is read only. so if you want to dd to the flash you need to get into the 2.4 kernel. [[User:85.124.221.56\|85.124.221.56]] 03:50, 17 November 2006 (EST)		-- it was more a problem with the 2.6-kernel. while in 2.6-kernel, the flash is read only. so if you want to dd to the flash you need to get into the 2.4 kernel. [[User:85.124.221.56\|85.124.221.56]] 03:50, 17 November 2006 (EST)
		+
		+	Followup: there was no damage or problem w/ the flash at all. As correctly pointed out by several folks, the 2.6 kernel that I was using doesn't support writing to flash.

85.124.221.56: /* Success followed by Failure */

85.124.221.56 — Fri, 17 Nov 2006 08:50:05 GMT

Success followed by Failure

← Older revision		Revision as of 08:50, 17 November 2006
Line 18:		Line 18:
	Luckily this has a chance to be fixed w/ JTAG.		Luckily this has a chance to be fixed w/ JTAG.

-	A point to make here is that flashing w/ the Buffalo Updater is not the same as flashing the ROM w/ dd. This unit did flash w/ both OpenLInk and FreeLink, but did not w/ dd.	+	A point to make here is that flashing w/ the Buffalo Updater is not the same as flashing the ROM w/ dd. This unit did flash w/ both OpenLInk and FreeLink, but did not w/ dd.
		+
		+	-- it was more a problem with the 2.6-kernel. while in 2.6-kernel, the flash is read only. so if you want to dd to the flash you need to get into the 2.4 kernel. [[User:85.124.221.56\|85.124.221.56]] 03:50, 17 November 2006 (EST)

Davy gravy: /* Success followed by Failure*/

Davy gravy — Thu, 16 Nov 2006 02:49:35 GMT

Success followed by Failure

← Older revision		Revision as of 02:49, 16 November 2006
Line 10:		Line 10:

	Flashed once with stock firmware to test then again with Freelink. No problems at all. Serial 45803360612820		Flashed once with stock firmware to test then again with Freelink. No problems at all. Serial 45803360612820
		+
		+
		+	==Success followed by Failure==
		+	I've flashed a variety of Linkstations/relatives, with OpenLink and FreeLink. A Kuro, too. All successfully.
		+	Flashed an old KuroHG to UBoot w/o incident, a great improvement. When I tried replicate the same type of flash on my LS-HG 250, the image did not write correctly to the flash chip, apparently. The image file has been confirmed to be valid, so after examining the output of dd, comp and od of the files, it is my guess that the chip was defective somehow. Or it is write-protected (I find this unlikely, though). I only know that the process was the same as that others used. It was double-check. It simply did not work on this machine. SN 45801560710476F
		+
		+	Luckily this has a chance to be fixed w/ JTAG.
		+
		+	A point to make here is that flashing w/ the Buffalo Updater is not the same as flashing the ROM w/ dd. This unit did flash w/ both OpenLInk and FreeLink, but did not w/ dd.

PeteD: /* Success */

PeteD — Wed, 25 Oct 2006 23:57:55 GMT

Success

← Older revision		Revision as of 23:57, 25 October 2006
Line 8:		Line 8:
	I've flash Openlink on 4 different HD-HG300's w/o incident.		I've flash Openlink on 4 different HD-HG300's w/o incident.
	Sorry, I don't have the serial numbers handy. [[User:Hsum\|Hsum]]		Sorry, I don't have the serial numbers handy. [[User:Hsum\|Hsum]]
		+
		+	Flashed once with stock firmware to test then again with Freelink. No problems at all. Serial 45803360612820

Kuroguy at 13:20, 24 October 2006

Kuroguy — Tue, 24 Oct 2006 13:20:42 GMT

← Older revision		Revision as of 13:20, 24 October 2006
Line 3:		Line 3:
	*An alternative explanation is that this particular LS became popular at about the same time and sold well. Many people who didn't know what they where doing, and who couldn't follow instructions ("Disable '''all''' firewalls ...") tried to flash their shiny new LS. Instead of admitting they weren't up to the task they came up with the "some series must be broken!" excuse, and use isolated observations (defect flash prom in a single LS), to explain the theory.		*An alternative explanation is that this particular LS became popular at about the same time and sold well. Many people who didn't know what they where doing, and who couldn't follow instructions ("Disable '''all''' firewalls ...") tried to flash their shiny new LS. Instead of admitting they weren't up to the task they came up with the "some series must be broken!" excuse, and use isolated observations (defect flash prom in a single LS), to explain the theory.

-	The HG I repaired via JTAG uses the 2.4.31 kernel, telnet and ftp enabled firmware, and U-Boot. I was not able to repair it by flashing via U-Boot and had to use JTAG to install the new firmware, so there was something wrong or different about the hardware. Once U-boot and the new firmware were flashed via JTAG the HG worked perfectly. kuroguy	+	* The HG I repaired via JTAG uses the 2.4.31 kernel, telnet and ftp enabled firmware, and U-Boot. I was not able to repair it by flashing via U-Boot and had to use JTAG to install the new firmware, so there was something wrong or different about the hardware. Once U-boot and the new firmware were flashed via JTAG the HG worked perfectly. kuroguy

	==Success==		==Success==
	I've flash Openlink on 4 different HD-HG300's w/o incident.		I've flash Openlink on 4 different HD-HG300's w/o incident.
	Sorry, I don't have the serial numbers handy. [[User:Hsum\|Hsum]]		Sorry, I don't have the serial numbers handy. [[User:Hsum\|Hsum]]

Kuroguy: fixed one with JTAG

Kuroguy — Tue, 24 Oct 2006 13:20:10 GMT

fixed one with JTAG

← Older revision		Revision as of 13:20, 24 October 2006
Line 2:		Line 2:

	*An alternative explanation is that this particular LS became popular at about the same time and sold well. Many people who didn't know what they where doing, and who couldn't follow instructions ("Disable '''all''' firewalls ...") tried to flash their shiny new LS. Instead of admitting they weren't up to the task they came up with the "some series must be broken!" excuse, and use isolated observations (defect flash prom in a single LS), to explain the theory.		*An alternative explanation is that this particular LS became popular at about the same time and sold well. Many people who didn't know what they where doing, and who couldn't follow instructions ("Disable '''all''' firewalls ...") tried to flash their shiny new LS. Instead of admitting they weren't up to the task they came up with the "some series must be broken!" excuse, and use isolated observations (defect flash prom in a single LS), to explain the theory.
		+
		+	The HG I repaired via JTAG uses the 2.4.31 kernel, telnet and ftp enabled firmware, and U-Boot. I was not able to repair it by flashing via U-Boot and had to use JTAG to install the new firmware, so there was something wrong or different about the hardware. Once U-boot and the new firmware were flashed via JTAG the HG worked perfectly. kuroguy

	==Success==		==Success==
	I've flash Openlink on 4 different HD-HG300's w/o incident.		I've flash Openlink on 4 different HD-HG300's w/o incident.
	Sorry, I don't have the serial numbers handy. [[User:Hsum\|Hsum]]		Sorry, I don't have the serial numbers handy. [[User:Hsum\|Hsum]]