Hacking Boot with CFW directly ?

  • Thread starter Thread starter Xyphoseos
  • Start date Start date
  • Views Views 4,249
  • Replies Replies 28
Yes, vesselhax exists. Is that what coldboothax uses? NO.
It's the same. The change is only the title.

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

My point here is that CBH is very user-unfriendly, very risky and very easy to mess up for someone who doesnt fully understand what they are doing.
All in the WiiU scene is unfriendly. Wupinstaller can brick, regionhax can brick, redNAND can brick sysNAND(update redNAND)

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

Some people get suprised by updates, cant/ wont set up DNS, their DNS goes down for long enough to update, plus people still believe in "bypass updates"
Oh and if a DNS goes down you can't connect to internet at all
 
It's the same. The change is only the title.
Alright, I'm going to take some time and explain to you what is going on here. What you have set up on your wii u is something called coldboothax. What coldboothax (we will refer to it as CBH from now on) does is changes the system boot to load a different app on boot than the wii u menu. This works because in system.xml, there is a line that controls what title ID the system boots. This is set to the home menu by default, but we change it to our DS game of choice. What happens next, is we have the DS game hacked via the Haxchi method. Haxchi allows the DS game to load homebrew off of the SD card - in this case, your "cfw." So when the wii u boots, it checks system.xml and sees that its supposed to boot the DS game, boots it, which loads a "cfw" for you. Now vesselhax is the same thing as haxchi, but with an n64 game. However, VHX (vesselhax) has not yet been exploited in a way to run CBH in the same way as haxchi. Therefore, VESSELHAX != COLDBOOTHAX.

Now one thing that has not yet been tested is if the Haxchi exploit will still work after an update, if Ninty patches it out or not. Remember, coldboothax is just a loader for haxchi. So, if haxchi stops working after an update, and you update, you will effectively brick your system, as it will now forever load a broken DS game.
 
  • Like
Reactions: Quantumcat
if you wanted to use cfw-coldboothax which is still kind of work in progress use make cfw-coldboot or you can wait patiently for salt team to make and release their cfw
Can you put that ''patiently'' in bold, add brackets, add an exclamation mark and make font size 80 please ?
 
Alright, I'm going to take some time and explain to you what is going on here. What you have set up on your wii u is something called coldboothax. What coldboothax (we will refer to it as CBH from now on) does is changes the system boot to load a different app on boot than the wii u menu. This works because in system.xml, there is a line that controls what title ID the system boots. This is set to the home menu by default, but we change it to our DS game of choice. What happens next, is we have the DS game hacked via the Haxchi method. Haxchi allows the DS game to load homebrew off of the SD card - in this case, your "cfw." So when the wii u boots, it checks system.xml and sees that its supposed to boot the DS game, boots it, which loads a "cfw" for you. Now vesselhax is the same thing as haxchi, but with an n64 game. However, VHX (vesselhax) has not yet been exploited in a way to run CBH in the same way as haxchi. Therefore, VESSELHAX != COLDBOOTHAX.

Now one thing that has not yet been tested is if the Haxchi exploit will still work after an update, if Ninty patches it out or not. Remember, coldboothax is just a loader for haxchi. So, if haxchi stops working after an update, and you update, you will effectively brick your system, as it will now forever load a broken DS game.
haxchi = contenthax
vesselhax = contenthax
They're the same thing
If coldboothax loads an haxchi game it will load a vesselhax game too
contenthax = permanent unsigned code execution (in this case homebrews)

If ninty patches haxchi at 100% someone will exploit N64 contenthax
 
haxchi = contenthax
vesselhax = contenthax
They're the same thing
If coldboothax loads an haxchi game it will load a vesselhax game too
contenthax = permanent unsigned code execution (in this case homebrews)

If ninty patches haxchi at 100% someone will exploit N64 contenthax
Yes, so the fact still remains that you will brick upon update. I dont see why you're trying to argue with me, im trying to make you aware that what you are using is Haxchi, which can be patched, and will cause a brick. Vesselhax has nothing to do with that, i mentioned it because you did.
 
Yes, so the fact still remains that you will brick upon update. I dont see why you're trying to argue with me, im trying to make you aware that what you are using is Haxchi, which can be patched, and will cause a brick. Vesselhax has nothing to do with that, i mentioned it because you did.
Ok when I'll update (if I'll update) I'll remove coldboothax
If ninty won't patch the exploit... coldboothax for the second time
 
Last edited by C0mm4nd_,
  • Like
Reactions: ItsKipz
if you wanted to use cfw-coldboothax which is still kind of work in progress use make cfw-coldboot or [you can wait patiently for salt team to make and release their cfw!] (God Damn it)
 
Last edited by Mustacheboyo,

Site & Scene News

Popular threads in this forum