PROD - Revision history

Ih8sn0w at 19:35, 16 July 2015

2015-07-16T19:35:44Z

Ih8sn0w: Much of this was wrong. Corrected.

2015-07-16T19:34:48Z

Much of this was wrong. Corrected.

Awesomebing1: Fixed, see discussions for what it was

2014-12-07T03:37:19Z

Fixed, see discussions for what it was

5urd at 21:44, 24 December 2012

2012-12-24T21:44:13Z

5urd at 04:13, 11 February 2011

2011-02-11T04:13:15Z

Cmdshft: Undo revision 8407 by Jennie (Talk)

2010-08-17T08:09:43Z

Undo revision 8407 by Jennie (Talk)

Jennie at 07:51, 17 August 2010

2010-08-17T07:51:32Z

ChronicDev at 13:56, 12 August 2009

2009-08-12T13:56:10Z

ChronicDev at 13:54, 12 August 2009

2009-08-12T13:54:08Z

Geohot at 04:33, 12 August 2009

2009-08-12T04:33:41Z

← Older revision		Revision as of 19:35, 16 July 2015
Line 3:		Line 3:
	This is to prevent production devices from running non-production code.		This is to prevent production devices from running non-production code.

−	{{stub\|firmware}}
	[[Category:Firmware Tags]]		[[Category:Firmware Tags]]

← Older revision		Revision as of 19:34, 16 July 2015
Line 1:		Line 1:
−	The '''PROD''' ('''PRODuction''') tag is a bit value that denotes if a ~~firmware~~ is for production devices or not. When set to <code>true</code>, the ~~firmware~~ is designated to be installed onto production devices. When ~~set~~ to <code>false</code>, the ~~firmware~~ is ~~typically~~ ~~incomplete~~ ~~and~~ ~~designed for~~ [[Prototypes\|internal devices]].	+	The '''PROD''' ('''PRODuction''') tag is a bit value that denotes if the image/ticket signature is for production devices or not. It is present in the SHSH certificate img3 and APTicket. When set to <code>true</code>, the image is designated to be installed onto production and development devices. When the tag value is <code>false</code>, the image/ticket is only explicitly accepted on [[Prototypes\|internal devices]]. This is enforced through [[iBoot (Bootloader)\|iBoot]]'s <code>do_load_image(void);</code> routine. The routine skips the '''PROD''' tag check if the device's fuse value is <code>false</code>.

		+	This is to prevent production devices from running non-production code.
−	This is most likely to prevent production devices from running internal firmwares as Apple wants [[iTunes]] to "phone home" for every restore, but at the same time, not affect their internal debug devices. This is acomplished through [[iBoot (Bootloader)\|iBoot]]'s <code>do_load_image(void);</code> routine that skips all tag checks if the '''PROD''' tag is not set.
−
−	== C-pseudocode for <code>do_load_image()</code> ==
−	if (flags.prod)
−	do_load_image();

	{{stub\|firmware}}		{{stub\|firmware}}

← Older revision		Revision as of 03:37, 7 December 2014
Line 1:		Line 1:
−	The '''PROD''' ('''PRODuction''') tag is a bit value that denotes if a firmware is for production devices or not. When set to <code>true</code>, the firmware is designated to be installed onto production devices. When set to <code>false</code>, the firmware is typically incomplete and designed for [[~~User:sonny722~~\|internal devices]].	+	The '''PROD''' ('''PRODuction''') tag is a bit value that denotes if a firmware is for production devices or not. When set to <code>true</code>, the firmware is designated to be installed onto production devices. When set to <code>false</code>, the firmware is typically incomplete and designed for [[Prototypes\|internal devices]].

	This is most likely to prevent production devices from running internal firmwares as Apple wants [[iTunes]] to "phone home" for every restore, but at the same time, not affect their internal debug devices. This is acomplished through [[iBoot (Bootloader)\|iBoot]]'s <code>do_load_image(void);</code> routine that skips all tag checks if the '''PROD''' tag is not set.		This is most likely to prevent production devices from running internal firmwares as Apple wants [[iTunes]] to "phone home" for every restore, but at the same time, not affect their internal debug devices. This is acomplished through [[iBoot (Bootloader)\|iBoot]]'s <code>do_load_image(void);</code> routine that skips all tag checks if the '''PROD''' tag is not set.

← Older revision		Revision as of 21:44, 24 December 2012
Line 1:		Line 1:
		+	The '''PROD''' ('''PRODuction''') tag is a bit value that denotes if a firmware is for production devices or not. When set to <code>true</code>, the firmware is designated to be installed onto production devices. When set to <code>false</code>, the firmware is typically incomplete and designed for [[User:sonny722\|internal devices]].
−	Denotes if the firmware image should be used on a production mode device or not. This is set to 1 on personalized + release firmware images (complete images that have ECID included and such), while set to 0 on yet-to-be-personalized images. This is probably to prevent production devices from running them, since Apple wants iTunes to phone home for every restore, but at the same time will not affect their debug devices, because there is a check in iBoot's do_load_image(); routine that will skip all tag checks if it is running on a debug device.

		+	This is most likely to prevent production devices from running internal firmwares as Apple wants [[iTunes]] to "phone home" for every restore, but at the same time, not affect their internal debug devices. This is acomplished through [[iBoot (Bootloader)\|iBoot]]'s <code>do_load_image(void);</code> routine that skips all tag checks if the '''PROD''' tag is not set.
		+
		+	== C-pseudocode for <code>do_load_image()</code> ==
		+	if (flags.prod)
		+	do_load_image();
		+
		+	{{stub\|firmware}}
	[[Category:Firmware Tags]]		[[Category:Firmware Tags]]

← Older revision		Revision as of 04:13, 11 February 2011
Line 2:		Line 2:

	[[Category:Firmware Tags]]		[[Category:Firmware Tags]]
−	[[Category:Firmware Parsing]]

← Older revision		Revision as of 08:09, 17 August 2010
Line 1:		Line 1:
	Denotes if the firmware image should be used on a production mode device or not. This is set to 1 on personalized + release firmware images (complete images that have ECID included and such), while set to 0 on yet-to-be-personalized images. This is probably to prevent production devices from running them, since Apple wants iTunes to phone home for every restore, but at the same time will not affect their debug devices, because there is a check in iBoot's do_load_image(); routine that will skip all tag checks if it is running on a debug device.		Denotes if the firmware image should be used on a production mode device or not. This is set to 1 on personalized + release firmware images (complete images that have ECID included and such), while set to 0 on yet-to-be-personalized images. This is probably to prevent production devices from running them, since Apple wants iTunes to phone home for every restore, but at the same time will not affect their debug devices, because there is a check in iBoot's do_load_image(); routine that will skip all tag checks if it is running on a debug device.
−
−	[http://www.superiorpapers.com/edlev_college.php college essay]

	[[Category:Firmware Tags]]		[[Category:Firmware Tags]]

← Older revision		Revision as of 07:51, 17 August 2010
Line 1:		Line 1:
	Denotes if the firmware image should be used on a production mode device or not. This is set to 1 on personalized + release firmware images (complete images that have ECID included and such), while set to 0 on yet-to-be-personalized images. This is probably to prevent production devices from running them, since Apple wants iTunes to phone home for every restore, but at the same time will not affect their debug devices, because there is a check in iBoot's do_load_image(); routine that will skip all tag checks if it is running on a debug device.		Denotes if the firmware image should be used on a production mode device or not. This is set to 1 on personalized + release firmware images (complete images that have ECID included and such), while set to 0 on yet-to-be-personalized images. This is probably to prevent production devices from running them, since Apple wants iTunes to phone home for every restore, but at the same time will not affect their debug devices, because there is a check in iBoot's do_load_image(); routine that will skip all tag checks if it is running on a debug device.
		+
		+	[http://www.superiorpapers.com/edlev_college.php college essay]

	[[Category:Firmware Tags]]		[[Category:Firmware Tags]]

← Older revision		Revision as of 13:56, 12 August 2009
Line 1:		Line 1:
	Denotes if the firmware image should be used on a production mode device or not. This is set to 1 on personalized + release firmware images (complete images that have ECID included and such), while set to 0 on yet-to-be-personalized images. This is probably to prevent production devices from running them, since Apple wants iTunes to phone home for every restore, but at the same time will not affect their debug devices, because there is a check in iBoot's do_load_image(); routine that will skip all tag checks if it is running on a debug device.		Denotes if the firmware image should be used on a production mode device or not. This is set to 1 on personalized + release firmware images (complete images that have ECID included and such), while set to 0 on yet-to-be-personalized images. This is probably to prevent production devices from running them, since Apple wants iTunes to phone home for every restore, but at the same time will not affect their debug devices, because there is a check in iBoot's do_load_image(); routine that will skip all tag checks if it is running on a debug device.
		+
		+	[[Category:Firmware Tags]]
		+	[[Category:Firmware Parsing]]

← Older revision		Revision as of 13:54, 12 August 2009
Line 1:		Line 1:
−	Denotes if the firmware image should be used on a production mode device or not. ~~Obviously, this~~ is set to 1 on ~~all~~ ~~firmwares~~, while ~~assumed~~ to be ~~set~~ to 0 on ~~debug~~ / ~~engineering~~ devices.	+	Denotes if the firmware image should be used on a production mode device or not. This is set to 1 on personalized + release firmware images (complete images that have ECID included and such), while set to 0 on yet-to-be-personalized images. This is probably to prevent production devices from running them, since Apple wants iTunes to phone home for every restore, but at the same time will not affect their debug devices, because there is a check in iBoot's do_load_image(); routine that will skip all tag checks if it is running on a debug device.
−
−	Is also set to 0 on 3GS unspecialized firmwares(w/o ECID)

← Older revision		Revision as of 04:33, 12 August 2009
Line 1:		Line 1:
	Denotes if the firmware image should be used on a production mode device or not. Obviously, this is set to 1 on all firmwares, while assumed to be set to 0 on debug / engineering devices.		Denotes if the firmware image should be used on a production mode device or not. Obviously, this is set to 1 on all firmwares, while assumed to be set to 0 on debug / engineering devices.
		+
		+	Is also set to 0 on 3GS unspecialized firmwares(w/o ECID)