Bricked - Revision history

Christoph: /* Useful information */

2008-12-29T10:30:46Z

‎Useful information

2008-09-21T04:36:25Z

‎What is/is not a 'bricked' Neo?

2008-07-08T04:47:29Z

2007-11-29T23:06:39Z

Add prolog, differentiate between bricked and dead battery.

2007-10-18T12:38:55Z

Warning about flashing bad mtdblock1

2007-08-12T14:41:18Z

‎Discoveries

2007-08-12T14:40:21Z

‎Result 1

2007-08-12T14:36:50Z

‎Result 1

2007-08-12T14:29:17Z

‎Result 1

2007-08-12T14:27:34Z

‎Result 1

@@ Line 90: / Line 90: @@
   mtd3: 000a0000 00004000 "splash"
   mtd4: 03d1c000 00004000 "rootfs
 [[Category:Hardware]]

@@ Line 3: / Line 3: @@
 "Bricked", by analogy with "as useful as a brick", means that the phone's state (as stored in flash memory) has gotten sufficiently messed up that you cannot get it operational via normal means, no matter how clever. The usual (but not the only) cause, as in the story below, is errors in re-flashing the device. The normal way to "un-brick" a phone requires use of a [[Debug_Board]].
-Note that being "bricked" must be distinguished from having a deeply-discharged battery. If you phone was working fine last Friday and won't boot up at all this Monday morning, it is more likely suffering the "really-dead-battery"; recovery from this is described on the [[Neo1973_Battery_Charger|Battery page]]; briefly: unplug USB, remove the battery for a minute, replace battery, connect USB, charge ('''without touching any buttons or trying to boot!''') for twelve hours.
+Note that being "bricked" must be distinguished from having a deeply-discharged battery. If you phone was working fine last Friday and won't boot up at all this Monday morning, it is more likely suffering the "really-dead-battery"; recovery from this is described on the [[Neo FreeRunner Hardware Issues#Can't boot with discharged or missing battery|Neo FreeRunner Hardware Issues]].
 == Notes on a 'bricked' Neo ==

← Older revision		Revision as of 23:06, 29 November 2007
Line 1:		Line 1:
		+	== What is/is not a 'bricked' Neo? ==
		+
		+	"Bricked", by analogy with "as useful as a brick", means that the phone's state (as stored in flash memory) has gotten sufficiently messed up that you cannot get it operational via normal means, no matter how clever. The usual (but not the only) cause, as in the story below, is errors in re-flashing the device. The normal way to "un-brick" a phone requires use of a [[Debug_Board]].
		+
		+	Note that being "bricked" must be distinguished from having a deeply-discharged battery. If you phone was working fine last Friday and won't boot up at all this Monday morning, it is more likely suffering the "really-dead-battery"; recovery from this is described on the [[Neo1973_Battery_Charger\|Battery page]]; briefly: unplug USB, remove the battery for a minute, replace battery, connect USB, charge ('''without touching any buttons or trying to boot!''') for twelve hours.
		+
	== Notes on a 'bricked' Neo ==		== Notes on a 'bricked' Neo ==

@@ Line 55: / Line 55: @@
 ==== Attempt 2 ====
-This idea involved taking the mtdblock1 from a working Neo and dd'ing it to the failed Neo's flash.
+This idea involved taking the mtdblock1 from a working Neo and dd'ing it to the failed Neo's flash. '''WARNING!!! Never flash an u-boot-env (mtdblock1) that does not come from your own Neo. It contains a partition table and bad block table that's unique for each Neo.'''
 ==== Result 2 ====

← Older revision		Revision as of 14:41, 12 August 2007
Line 68:		Line 68:


−	2. Hex editing the extracted mtd partition (u-boot-env) and trying to dd that works but the results are not what is expected. It appears that if one of the boot env parameters is missing, in this case splashimage, the u-boot-env parameters are all treated as if they were blank and the device uses default settings.	+	2. Hex editing the extracted mtd partition (u-boot-env) and trying to dd that works but the results are not what is expected. It appears that if one of the boot env parameters is missing, in this case splashimage, the u-boot-env parameters are all treated as if they were blank and the device uses default settings. This is because the CRC no longer matches.

← Older revision		Revision as of 14:40, 12 August 2007
Line 47:		Line 47:


−	'''Cesar Barros ~~(irc nick cesarb)~~ points out that'''	+	'''[[User:CesarB\|Cesar Barros]] points out that'''

	''The reason editing the environment by hand does not work well is not the missing variable, but that the CRC doesn't match anymore, which makes it ignore the whole environment''		''The reason editing the environment by hand does not work well is not the missing variable, but that the CRC doesn't match anymore, which makes it ignore the whole environment''

← Older revision		Revision as of 14:36, 12 August 2007
Line 47:		Line 47:


−	'''cesarb* points out that'''	+	'''Cesar Barros (irc nick cesarb) points out that'''

	''The reason editing the environment by hand does not work well is not the missing variable, but that the CRC doesn't match anymore, which makes it ignore the whole environment''		''The reason editing the environment by hand does not work well is not the missing variable, but that the CRC doesn't match anymore, which makes it ignore the whole environment''

@@ Line 47: / Line 47: @@
-'''cesarb points out that'''
+'''cesarb* points out that'''
 ''The reason editing the environment by hand does not work well is not the missing variable, but that the CRC doesn't match anymore, which makes it ignore the whole environment''
 which makes perfect sense.
 ==== Attempt 2 ====