Talk:Flash Filesystem - Revision history

Smea: and at spelling apparently

2016-04-17T19:07:00Z

and at spelling apparently

← Older revision		Revision as of 23:07, 17 April 2016
Line 60:		Line 60:
	== Note: ==		== Note: ==

	There is currently a third TWL partition ~~who's~~ location in NAND is currently unknown. Said partition is TWLS, or TWL Sound. By default, this partition is empty, however, if you record a sound with the DSi Sound app, the partition is populated, similar to TWLP. --[[User:MassExplosion213\|MassExplosion213]] 23:03, 17 April 2016 (CEST)		There is currently a third TWL partition whose location in NAND is currently unknown. Said partition is TWLS, or TWL Sound. By default, this partition is empty, however, if you record a sound with the DSi Sound app, the partition is populated, similar to TWLP. --[[User:MassExplosion213\|MassExplosion213]] 23:03, 17 April 2016 (CEST)

MassExplosion213: Because I'm awful at hitting buttons

2016-04-17T19:04:15Z

Because I'm awful at hitting buttons

← Older revision		Revision as of 23:04, 17 April 2016
Line 60:		Line 60:
	== Note: ==		== Note: ==

	There is currently a third TWL partition who's location in NAND is currently unknown. Said partition is TWLS, or TWL Sound. By default, this partition is empty, however, if you record a sound with the DSi Sound app, the partition is populated, similar to TWLP. --[[User:MassExplosion213:MassExplosion213]] 23:03, 17 April 2016 (CEST)		There is currently a third TWL partition who's location in NAND is currently unknown. Said partition is TWLS, or TWL Sound. By default, this partition is empty, however, if you record a sound with the DSi Sound app, the partition is populated, similar to TWLP. --[[User:MassExplosion213\|MassExplosion213]] 23:03, 17 April 2016 (CEST)

MassExplosion213 at 21:03, 17 April 2016

2016-04-17T19:03:33Z

← Older revision		Revision as of 23:03, 17 April 2016
Line 57:		Line 57:
	::::::Aren't you talking about a movable.sed file or there are others not mentioned explicitly?--[[User:Duke srg\|Duke srg]] 14:01, 11 April 2014 (CEST)		::::::Aren't you talking about a movable.sed file or there are others not mentioned explicitly?--[[User:Duke srg\|Duke srg]] 14:01, 11 April 2014 (CEST)
	:::::::No, I mean this: [[Title_Database]]. --[[User:Yellows8\|Yellows8]] 18:23, 11 April 2014 (CEST)		:::::::No, I mean this: [[Title_Database]]. --[[User:Yellows8\|Yellows8]] 18:23, 11 April 2014 (CEST)

			== Note: ==

			There is currently a third TWL partition who's location in NAND is currently unknown. Said partition is TWLS, or TWL Sound. By default, this partition is empty, however, if you record a sound with the DSi Sound app, the partition is populated, similar to TWLP. --[[User:MassExplosion213:MassExplosion213]] 23:03, 17 April 2016 (CEST)

Yellows8: /* Possible firmware downgrade vulnerability */

2014-04-11T14:23:58Z

Possible firmware downgrade vulnerability

← Older revision		Revision as of 18:23, 11 April 2014
Line 56:		Line 56:
	:::::Yeah, at least one of those console-unique AESMACs would be rendered invalid with method you're describing. --[[User:Yellows8\|Yellows8]] 06:21, 11 April 2014 (CEST)		:::::Yeah, at least one of those console-unique AESMACs would be rendered invalid with method you're describing. --[[User:Yellows8\|Yellows8]] 06:21, 11 April 2014 (CEST)
	::::::Aren't you talking about a movable.sed file or there are others not mentioned explicitly?--[[User:Duke srg\|Duke srg]] 14:01, 11 April 2014 (CEST)		::::::Aren't you talking about a movable.sed file or there are others not mentioned explicitly?--[[User:Duke srg\|Duke srg]] 14:01, 11 April 2014 (CEST)
			:::::::No, I mean this: [[Title_Database]]. --[[User:Yellows8\|Yellows8]] 18:23, 11 April 2014 (CEST)

Duke srg at 12:01, 11 April 2014

2014-04-11T10:01:52Z

← Older revision		Revision as of 14:01, 11 April 2014
Line 55:		Line 55:
	::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware changes from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)		::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware changes from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)
	:::::Yeah, at least one of those console-unique AESMACs would be rendered invalid with method you're describing. --[[User:Yellows8\|Yellows8]] 06:21, 11 April 2014 (CEST)		:::::Yeah, at least one of those console-unique AESMACs would be rendered invalid with method you're describing. --[[User:Yellows8\|Yellows8]] 06:21, 11 April 2014 (CEST)
			::::::Aren't you talking about a movable.sed file or there are others not mentioned explicitly?--[[User:Duke srg\|Duke srg]] 14:01, 11 April 2014 (CEST)

Yellows8: /* Possible firmware downgrade vulnerability */

2014-04-11T02:21:54Z

Possible firmware downgrade vulnerability

← Older revision		Revision as of 06:21, 11 April 2014
Line 54:		Line 54:
	:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)		:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)
	::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware changes from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)		::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware changes from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)
			:::::Yeah, at least one of those console-unique AESMACs would be rendered invalid with method you're describing. --[[User:Yellows8\|Yellows8]] 06:21, 11 April 2014 (CEST)

Duke srg: typo

2014-04-11T02:00:59Z

typo

← Older revision		Revision as of 06:00, 11 April 2014
Line 53:		Line 53:
	::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)		::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)
	:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)		:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)
	::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware ~~canges~~ from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)		::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware changes from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)

Duke srg at 03:59, 11 April 2014

2014-04-11T01:59:42Z

← Older revision		Revision as of 05:59, 11 April 2014
Line 53:		Line 53:
	::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)		::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)
	:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)		:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)
	::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware canges from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.		::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware canges from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)

Duke srg: /* Possible firmware downgrade vulnerability */

2014-04-11T01:57:24Z

Possible firmware downgrade vulnerability

← Older revision		Revision as of 05:57, 11 April 2014
Line 53:		Line 53:
	::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)		::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)
	:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)		:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)
			::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware canges from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.

Yellows8: /* Possible firmware downgrade vulnerability */

2014-04-10T18:11:35Z

Possible firmware downgrade vulnerability

← Older revision		Revision as of 22:11, 10 April 2014
Line 52:		Line 52:
	:There's no way to convert a NAND image from one 3DS for use on another 3DS, without generating the NAND xorpad(s) for both systems(requires ARM9 code exec on both). Another reason why ARM9 exec is needed here is because there's certain files stored in CTRNAND containing console-unique AESMACs. Since that keyslot is initialized by bootrom those AESMACs can only be calculated on the same 3DS which you're calculating these CTRNAND AESMACs for. --[[User:Yellows8\|Yellows8]] 18:02, 10 April 2014 (CEST)		:There's no way to convert a NAND image from one 3DS for use on another 3DS, without generating the NAND xorpad(s) for both systems(requires ARM9 code exec on both). Another reason why ARM9 exec is needed here is because there's certain files stored in CTRNAND containing console-unique AESMACs. Since that keyslot is initialized by bootrom those AESMACs can only be calculated on the same 3DS which you're calculating these CTRNAND AESMACs for. --[[User:Yellows8\|Yellows8]] 18:02, 10 April 2014 (CEST)
	::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)		::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)
			:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)

← Older revision		Revision as of 18:23, 11 April 2014
Line 56:		Line 56:
	:::::Yeah, at least one of those console-unique AESMACs would be rendered invalid with method you're describing. --[[User:Yellows8\|Yellows8]] 06:21, 11 April 2014 (CEST)		:::::Yeah, at least one of those console-unique AESMACs would be rendered invalid with method you're describing. --[[User:Yellows8\|Yellows8]] 06:21, 11 April 2014 (CEST)
	::::::Aren't you talking about a movable.sed file or there are others not mentioned explicitly?--[[User:Duke srg\|Duke srg]] 14:01, 11 April 2014 (CEST)		::::::Aren't you talking about a movable.sed file or there are others not mentioned explicitly?--[[User:Duke srg\|Duke srg]] 14:01, 11 April 2014 (CEST)
			:::::::No, I mean this: [[Title_Database]]. --[[User:Yellows8\|Yellows8]] 18:23, 11 April 2014 (CEST)

← Older revision		Revision as of 14:01, 11 April 2014
Line 55:		Line 55:
	::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware changes from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)		::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware changes from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)
	:::::Yeah, at least one of those console-unique AESMACs would be rendered invalid with method you're describing. --[[User:Yellows8\|Yellows8]] 06:21, 11 April 2014 (CEST)		:::::Yeah, at least one of those console-unique AESMACs would be rendered invalid with method you're describing. --[[User:Yellows8\|Yellows8]] 06:21, 11 April 2014 (CEST)
			::::::Aren't you talking about a movable.sed file or there are others not mentioned explicitly?--[[User:Duke srg\|Duke srg]] 14:01, 11 April 2014 (CEST)

← Older revision		Revision as of 06:21, 11 April 2014
Line 54:		Line 54:
	:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)		:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)
	::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware changes from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)		::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware changes from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)
			:::::Yeah, at least one of those console-unique AESMACs would be rendered invalid with method you're describing. --[[User:Yellows8\|Yellows8]] 06:21, 11 April 2014 (CEST)

← Older revision		Revision as of 06:00, 11 April 2014
Line 53:		Line 53:
	::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)		::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)
	:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)		:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)
	::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware ~~canges~~ from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)		::::Ok, just to clarify, during system update AESMAC init file IS updated with the new console-unique data. So after transferring firmware changes from one system to another without complete decypher, during next boot at least AESMAC file on CTR NAND partition contents will have wrong data and REG_AESMAC being initialized with that will fail the following boot process. Smart enough.--[[User:Duke srg\|Duke srg]] 05:59, 11 April 2014 (CEST)

← Older revision		Revision as of 22:11, 10 April 2014
Line 52:		Line 52:
	:There's no way to convert a NAND image from one 3DS for use on another 3DS, without generating the NAND xorpad(s) for both systems(requires ARM9 code exec on both). Another reason why ARM9 exec is needed here is because there's certain files stored in CTRNAND containing console-unique AESMACs. Since that keyslot is initialized by bootrom those AESMACs can only be calculated on the same 3DS which you're calculating these CTRNAND AESMACs for. --[[User:Yellows8\|Yellows8]] 18:02, 10 April 2014 (CEST)		:There's no way to convert a NAND image from one 3DS for use on another 3DS, without generating the NAND xorpad(s) for both systems(requires ARM9 code exec on both). Another reason why ARM9 exec is needed here is because there's certain files stored in CTRNAND containing console-unique AESMACs. Since that keyslot is initialized by bootrom those AESMACs can only be calculated on the same 3DS which you're calculating these CTRNAND AESMACs for. --[[User:Yellows8\|Yellows8]] 18:02, 10 April 2014 (CEST)
	::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)		::I'm not about converting a NAND image from system to another directly. Can we alculate for a various firmware byte-to-byte XOR-difference, which result the same xorpads for each system to annihilate. And for the same CTRNAND files untouched with a firmware update this difference will be zero. So applying this difference for another console CTRNAND will update a firmware without the need of the actual console-unique xorpad--[[User:Duke srg\|Duke srg]] 21:48, 10 April 2014 (CEST)
			:::The CTRNAND files /w console-unique AESMACs I'm referring to get updated when sys-updates get installed, if those don't get updated properly(invalid AESMACs for example) you would have a system which would fail to boot when it tries to launch titles from CTRNAND-FS. There's no way to properly update those files without proper NAND xorpads/etc. --[[User:Yellows8\|Yellows8]] 22:11, 10 April 2014 (CEST)