default=fw.img
<default_title_id type="hexBinary" length="8">0005001010040200</default_title_id>
.arm.big
.open "sections/0x5060000.bin","patched_sections/0x5060000.bin",0x05060000
; force loading of a different system.xml
.org 0x050600DC
.area 0x20
.ascii "/vol/system/config/syshax.xml",0
.endarea
.org 0x050600FC
.area 0x24
.ascii "/vol/system_slc/config/syshax.xml",0
.endarea
.Close
There is a moderate risk, aka do not do this unless you know what you are doing.Is this then persistant or can it be removed easily? If so, whats the disadvantage? Why "none" uses autoboot for haxchi with sysnand / rednand hack? Is there a high brick risk?
AFAIK is a high brick risk as we have to edit a .xml file which is completely essential to boot the wii u. If for some reason we make a typo or delete the installed vc game the console will brick. I was hoping that there was some sort of method in which we could boot into rednand and if for some reason the channel get deleted or the file get corrupted we could boot normally as "in boot to rednand if channel not found then boot to wii u sys menu"Is this then persistant or can it be removed easily? If so, whats the disadvantage? Why "none" uses autoboot for haxchi with sysnand / rednand hack? Is there a high brick risk?