Exactly, if you want to use signpatcher you nee dthe one compiled for coldboot, not the one returning to sysmenu.sigpatcher2sysmenu isn't compatible with coldboothax
Use either cfw-coldboot branch of iosuhax or rednand
Exactly, if you want to use signpatcher you nee dthe one compiled for coldboot, not the one returning to sysmenu.sigpatcher2sysmenu isn't compatible with coldboothax
Use either cfw-coldboot branch of iosuhax or rednand
Yes to both questions.Ok I dusted off my wii u from this march. before I attempt this hachi stuff I got 2 questions:
1. I need access to the wiiu shop to buy a ds game yes?
2. Is the latest firmware exploitable? cause I hadn't bought a ds game yet.
You will brick if your DS VC game is on USB and not in sysNAND, but the installer will make sure that the game you select is in sysNAND. USB games are not shown in the list.I've heard that if you have games on your HDD while using cold boot your Wii U will brick. Is this true?
Nope, just the autobooted title needs to be in system memory.I've heard that if you have games on your HDD while using cold boot your Wii U will brick. Is this true?
I don't see why it should be a problem. In the worst case, just turn on the Wii U from its power button (not the gamepad one) and it will boot normally.just in case, but should quick start be enabled or not? does it make a difference?
yeah......I forgot about that. I just generally start the console from the gamepad, so...I don't see why it should be a problem. In the worst case, just turn on the Wii U from its power button (not the gamepad one) and it will boot normally.
<?xml version="1.0" encoding="utf-8"?>
<system type="complex" access="777">
<version type="unsignedInt" length="4">21</version>
<cmdFlags type="unsignedInt" length="4">0</cmdFlags>
<default_os_id type="hexBinary" length="8">000500101000400a</default_os_id>
<default_title_id type="hexBinary" length="8">0005001010040100</default_title_id>
<log type="complex" length="0">
<enable type="unsignedInt" length="4">0</enable>
<max_size type="unsignedInt" length="4">8388607</max_size>
</log>
<standby type="complex" length="0">
<enable type="unsignedInt" length="4">1</enable></standby>
<ramdisk type="complex" length="0">
<cache_user_code type="unsignedInt" length="4">0</cache_user_code>
<max_file_size type="unsignedInt" length="4">10485760</max_file_size>
<cache_delay_ms type="unsignedInt" length="4">10000</cache_delay_ms>
</ramdisk>
<simulated_ppc_mem2_size type="hexBinary" length="4">00000000</simulated_ppc_mem2_size>
<dev_mode type="unsignedInt" length="4">0</dev_mode>
<prev_title_id type="hexBinary" length="8">0000000000000000</prev_title_id>
<prev_os_id type="hexBinary" length="8">0000000000000000</prev_os_id>
<default_app_type type="hexBinary" length="4">90000001</default_app_type>
<default_device_type type="string" length="16" />
<default_device_index type="unsignedInt" length="4">0</default_device_index>
<fast_relaunch_value type="unsignedInt" length="4">0</fast_relaunch_value>
<default_eco_title_id type="hexBinary" length="8">0005001010066000</default_eco_title_id>
</system>
It seems thet id of the system menu is different depending on the region of your console. My installer works on EU consoles only atm. I will update the installer.@::Phoenix:: now another issue. I tried installing coldboothax (5.5.1U), but it said "Default id is wrong. Coldboothax already installed? Exiting...", despite the fact I've never modified system.xml at all. do you know why this could happen?
storage_slc/config/system.xml contents
Code:<?xml version="1.0" encoding="utf-8"?> <system type="complex" access="777"> <version type="unsignedInt" length="4">21</version> <cmdFlags type="unsignedInt" length="4">0</cmdFlags> <default_os_id type="hexBinary" length="8">000500101000400a</default_os_id> <default_title_id type="hexBinary" length="8">0005001010040100</default_title_id> <log type="complex" length="0"> <enable type="unsignedInt" length="4">0</enable> <max_size type="unsignedInt" length="4">8388607</max_size> </log> <standby type="complex" length="0"> <enable type="unsignedInt" length="4">1</enable></standby> <ramdisk type="complex" length="0"> <cache_user_code type="unsignedInt" length="4">0</cache_user_code> <max_file_size type="unsignedInt" length="4">10485760</max_file_size> <cache_delay_ms type="unsignedInt" length="4">10000</cache_delay_ms> </ramdisk> <simulated_ppc_mem2_size type="hexBinary" length="4">00000000</simulated_ppc_mem2_size> <dev_mode type="unsignedInt" length="4">0</dev_mode> <prev_title_id type="hexBinary" length="8">0000000000000000</prev_title_id> <prev_os_id type="hexBinary" length="8">0000000000000000</prev_os_id> <default_app_type type="hexBinary" length="4">90000001</default_app_type> <default_device_type type="string" length="16" /> <default_device_index type="unsignedInt" length="4">0</default_device_index> <fast_relaunch_value type="unsignedInt" length="4">0</fast_relaunch_value> <default_eco_title_id type="hexBinary" length="8">0005001010066000</default_eco_title_id> </system>
Don't know what the title id is for the JAP Wii U menu...It seems thet id of the system menu is different depending on the region of your console. My installer works on EU consoles only atm. I will update the installer.
yeah I tried to look at wiiubrew but couldn't find anything. I think I know someone with a JPN wiiu though, so if I can ask them......Don't know what the title id is for the JAP Wii U menu...
Try this one: https://mega.nz/#!3hozlbxb!w6TgUz0t4TLkBMPTyqihcrk5O60N9CGQMd5a6AbcB4Iyeah I tried to look at wiiubrew but couldn't find anything. I think I know someone with a JPN wiiu though, so if I can ask them......
Oh the agony!! :,PWe're doomed. Users following instructions? you ask too much!
looks like it works now, system booted to hbl
I also found the title id for the JAP Menu. Commited the changes and I uploading the new version. Thank you for letting me notice it.looks like it works now, system booted to hbl
The double loading is still there. I had to setup redNAND first, before experimenting with the issue and it took a lot to dump the nand. That's something I working on. Coldboothax has nothing to do with that issue, is an issues of fw.img and cfw_booter.I just have one question. Does this still include that thing where it'll boot up fw.img twice, having to go through the IOSUHAX logo two times before the home menu loads up? I'm waiting for the times when coldboot is seamless and works as quick as booting cfw manually.