Hacking Coldboothax - solving infinite loop with sysNAND CFW

  • Thread starter Thread starter ::Phoenix::
  • Start date Start date
  • Views Views 40,324
  • Replies Replies 239
  • Likes Likes 28
Can I have rednand as default and sysnand loaded with A? Or will that somehow screw everything up?
 
Installed. Wii U is not a brick. Now I don't have to tap the gamepad three times to load CFW. Can't wait until next week when there is a homebrew app that sets up coolboothax with the touch of a button. Not that this was terribly hard. Especially since Haxchi is easy to setup now. If people just follow directions they should be good.
 
Last edited by DocAmes1980,
two questions:
1) Can we just cooldboothax->haxchi->sign_patcher.elf ?
2) Try to copy that elf to nand, so no SD card required at all? EX: "/vol/storage_mlc01/elf/sign_patcher.elf"
 
Last edited by ThePwnerer,
Yeah, i saw that thread, so i'm trying to get the best of the 3 worlds. But i'm asking first to see if this should work or is just crazy

Wait.. what is sign patcher? What can that combination do that just having a fw.img on your NAND can't do?
 
two questions:
1) Can we just cooldboothax->haxchi->sign_patcher.elf ?
2) Try to copy that elf to nand, so no SD card required at all? EX: "/vol/storage_mlc01/elf/sign_patcher.elf"
I don't think it is possible, without a full relaunch of the system. Sign patcher just patches the on memory fw.IMG, but after that there is no relaunch of it (of course, otherwise you would loose the patches). But without reloading fw.IMG (a modified one for coldboot) you will get stuck in a selfloop again.
 
Can I have rednand as default and sysnand loaded with A? Or will that somehow screw everything up?
As far as you put a backup xml like syshax.xml in your sysnand and configure haxchi to run at least one fw.img, you will always be safe.
So, having that said, you can configure rednand and sysnand cfw separatedly and decide what to boot on startup.
 
What I'm understanding here is that you use a custom fw.img that will load "syshax.xml" with the 'correct' titleID instead of "system.xml" which just keeps trying to load itself, correct?
 
I asked this in another thread, but I thought it was worth giving it a shot here as well.

How can I move from this solution (coldbooting dimok's fw.img with syshax.xml) to his signature-patching ELF?
 
You just need to change your config.txt of your haxchi install.

I must be doing something wrong, because it either throws me into a reloading loop (if the ELF is placed at the root of the SD card) or it gives me a -5 error (if it's placed in something like wiiu/apps/iosu/sigpatcher.elf). I double checked and my config.txt is pointing to the correct location. What could be wrong?
 
I think I found wy the cfw is loading twice. I would need someone which has already
I must be doing something wrong, because it either throws me into a reloading loop (if the ELF is placed at the root of the SD card) or it gives me a -5 error (if it's placed in something like wiiu/apps/iosu/sigpatcher.elf). I double checked and my config.txt is pointing to the correct location. What could be wrong?
The sign patcher does not apply the coldboot patches, it will always end up bootlooping.
 
-5 means that your path is wrong. Check if your config.txt is really having the correct path.

Have you taken the correct elf file from this post: https://gbatemp.net/threads/simple-signature-check-patcher.451138/page-4#post-6892235 ?

And double check if the filename matches the name in your config

Ah, you're right: I didn't get the correct ELF.

I think I found wy the cfw is loading twice. I would need someone which has already

The sign patcher does not apply the coldboot patches, it will always end up bootlooping.

Well, I'm using the ELF that specifically says "coldbooting". But if you've solve the issue of CFW loading twice, I think I'd rather wait until you make your solution public instead of using the ELF method. So it's back to fw.img for me :)
 
Ah, you're right: I didn't get the correct ELF.



Well, I'm using the ELF that specifically says "coldbooting". But if you've solve the issue of CFW loading twice, I think I'd rather wait until you make your solution public instead of using the ELF method. So it's back to fw.img for me :)
Did not know dimok updated the sign patcher. The solution should be a change in cfw booted forcing it to apply the coldboot patches to the in memory MCP otherwise at a first try it will Los the original XML and THEN load the fw.img

--------------------- MERGED ---------------------------

Did not know dimok updated the sign patcher. The solution should be a change in cfw booted forcing it to apply the coldboot patches to the in memory MCP otherwise at a first try it will Los the original XML and THEN load the fw.img
Ah, you're right: I didn't get the correct ELF.



Well, I'm using the ELF that specifically says "coldbooting". But if you've solve the issue of CFW loading twice, I think I'd rather wait until you make your solution public instead of using the ELF method. So it's back to fw.img for me :)
I am not at home now but if you could add an entry on your config.txt and try my cfw booted I can publish the change.
 
Did not know dimok updated the sign patcher. The solution should be a change in cfw booted forcing it to apply the coldboot patches to the in memory MCP otherwise at a first try it will Los the original XML and THEN load the fw.img

--------------------- MERGED ---------------------------



I am not at home now but if you could add an entry on your config.txt and try my cfw booted I can publish the change.

Sure. Just tell me what you want me to do and I'll try it. Glad to be of use.
 

Site & Scene News

Popular threads in this forum