thought you might want to know this.
https://github.com/FIX94/haxchi/pull/6#issuecomment-265325678
https://github.com/FIX94/haxchi/pull/6#issuecomment-265325678
Does it really need to check the title id? If someone's already installed coldboot and would like to update there haxchi installation with this it wouldn't work?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.
--------------------- MERGED ---------------------------
Don't know what the title id is for the JAP Wii U menu...
How do you compile it to be cfw-coldboot?maybe you are using regular CFW -- make sure you are using cfw-coldboot and not regular iosu or rednand when you compile your source
Use command "make cfw-coldboot".How do you compile it to be cfw-coldboot?
Not as for now, it needs to be sure the backup syshax.XML is safe. I can let it get the menu id from somewhere else and remove the need to check. But for now, this is how it works.Does it really need to check the title id? If someone's already installed coldboot and would like to update there haxchi installation with this it wouldn't work?
Yeah, I read your comments, it sound great! Looking forward on a better coldboothax solution!thought you might want to know this.
https://github.com/FIX94/haxchi/pull/6#issuecomment-265325678
Do I do this in the main directory? I cloned the source from github and I can't figure it outUse command "make cfw-coldboot".
On which repo? FIX94's or dimok's? (Sorry for the hijack.)Use command "make cfw-coldboot".
dimok'sOn which repo? FIX94's or dimok's? (Sorry for the hijack.)
I see know one has answered your problem so I will help. For a start your config.txt file is wrong, you have:-Installed this and get kinda of brick. Wii U loads, but it got looped with: black screen, Wii U logo in corner and "Wii U menu" loading screen(It might called different in English, hope you understood what i mean).
EUR 5.5.1 console, haxchi in NAND, config file contains this:
As you can see, I managed B button as Homebrew loader and it's perfectly loading, so I don't bothered too much about that brick, because I can fix it. But, what I'm doing wrong, to get this brick? I want coldboot, instead of this little occasion.
I see know one has answered your problem so I will help. For a start your config.txt file is wrong, you have:-
a=fw.img
it should be
default=fw.img
Its loading your coldboot img as button "a" and not as "default" load. You might also have bricked it unless you can get back into the homebrew launcher by pressing "b" on second boot up?
This is why tbh many that don't really know what they are doing with this and see a thread like this and think its straight forward, its still not!!! I know this thread makes it seem eaiser which it is to some but to l others it can still cause bricks. I think maybe the thread should still carry a warning in big red letters.
Exactly, if you want to use signpatcher you nee dthe one compiled for coldboot, not the one returning to sysmenu.
And he precisely stated he is able to boot in HBL, so He did not brick anything. He just has to use the right sign patcher.He already got an answer...
So we can dodimok's
There is no make coldboot.So we can do
Is that right? And how is make cfw different from doing make on FIX94's fork? And finally are there other options like these in FIX94's fork too?
- make
- make cfw
- make coldboot
- make cfw-coldboot
Thanks! So I can only do make on FIX94's fork? And what's the difference between make on FIX94's and make cfw on dimok's?There is no make coldboot.
For dimok's you have only
make (which coincides with make redNAND)
make cfw
make cfw-coldboot
--------------------- MERGED ---------------------------
FIX94's has no redNAND support as far as I recall.
Fix has not support for coldboot as well. There is no reason for using FIX's iosuhax. Dimok's is the most complete and up to date. I remember FIX was mostly working on wupclient related stuff.Thanks! So I can only do make on FIX94's fork? And what's the difference between make on FIX94's and make cfw on dimok's?
This would require a change in the haxchi code which will remove the "default=..." feature. Since FIX94 is working on his solution for coldboothax, I don't think it is worth the time changing haxchi to that level. I will just provide an uninstaller and let people reinstall coldboothax over the previous installation, instead of aborting the installation process.Would be awesome ( and less risky ) if it was triggered by a button at boot.
Let's say if you press L it coldboothax and if no button pressed it boots to sysnand.
This would require a change in the haxchi code which will remove the "default=..." feature. Since FIX94 is working on his solution for coldboothax, I don't think it is worth the time changing haxchi to that level. I will just provide an uninstaller and let people reinstall coldboothax over the previous installation, instead of aborting the installation process.
No more than that.