Is coldbooting Aroma and Tiramisu Safe?

[pichuluv84]

I am looking forward to homebrew my Wii U soon but I'd like to coldboot it but I am afraid of bricking my Wii U after I bricked my Wii U with ColdBootHaxchi (I unbricked it by the way.) and If I plan on coldbooting it, Is it safe to coldboot Aroma and Tiramisu? Most of the time I probably will be booting into Aroma for Pretendo Network since Tiramisu is no longer supported by Pretendo. Is coldbooting Aroma and Tiramisu safe?

 

[BaamAlex]

The other question is, why not? It is totally safe. Otherwise the dev wouldn't offer a coldboot solution. Unlike cbhc, the title (the one where tiramisu/aroma is installed) cannot be deleted "accidentally".

 

[Ryab]

I am looking forward to homebrew my Wii U soon but I'd like to coldboot it but I am afraid of bricking my Wii U after I bricked my Wii U with ColdBootHaxchi (I unbricked it by the way.) and If I plan on coldbooting it, Is it safe to coldboot Aroma and Tiramisu? Most of the time I probably will be booting into Aroma for Pretendo Network since Tiramisu is no longer supported by Pretendo. Is coldbooting Aroma and Tiramisu safe?

It is nowhere near as dangerous as CBHC used to be.

 

[MikaDubbz]

It is nowhere near as dangerous as CBHC used to be.

I feel like you're even overselling how dangerous CBHC was to begin with. I mean yeah, if you did something dumb, you could brick with CBHC, but if you only ever followed the official tutorials, you really never were in any danger. Plus, now thanks to UDPIH, just about any brick you might get from a CBHC specific issue can be unbricked without a hardmod.

Point is, hacking a Wii U, be it with a current or former solution, is almost entirely risk-free. If you find yourself bricked, you very likely can also get yourself out of that situation without having to physically alter anything about your system. Of course, there is always still risk that if you mess around with your Wii U outside of the confines of anything documented from within the scene as safe that you could still brick. I wouldn't be very worried about these remotely possible bricks, but just be aware that they exist all the same, no matter what cfw you use.

 

[Ryab]

I feel like you're even overselling how dangerous CBHC was to begin with. I mean yeah, if you did something dumb, you could brick with CBHC, but if you only ever followed the official tutorials, you really never were in any danger. Plus, now thanks to UDPIH, just about any brick you might get from a CBHC specific issue can be unbricked without a hardmod.

Point is, hacking a Wii U, be it with a current or former solution, is almost entirely risk-free. If you find yourself bricked, you very likely can also get yourself out of that situation without having to physically alter anything about your system. Of course, there is always still risk that if you mess around with your Wii U outside of the confines of anything documented from within the scene as safe that you could still brick. I wouldn't be very worried about these remotely possible bricks, but just be aware that they exist all the same, no matter what cfw you use.

I mean CBHC was a pretty simple process yes, but people will be people and I guarentee that 90% of bricked Wii Us are related.

 

[pichuluv84]

It is nowhere near as dangerous as CBHC used to be.

Cool. Thanks!

 

[SDIO]

I would argue it is even safer, as it gives you an entry point in case you break something with the menu. And breaking the menu is much easier, even a corrupted banner is enough.
But now that we have UDPIH, it doesn't even matter as it gives us the option to change the cold boot title to whatever we want, no matter what it was set to previously.

One could maybe argue that writing the system.xml could be considered dangerous, as if that gets truly corrupted, UDPIH will no longer work. But for that to happen you either need a really corrupt SLC (but then you have other problems anyway) or a power outage in the wrong split second. So I wouldn't consider that a realistic risk...

 

[BaamAlex]

I mean CBHC was a pretty simple process yes, but people will be people and I guarentee that 90% of bricked Wii Us are related.

Dumb cbhc bricks in the past are almost 100% user error.

 

[Ryab]

Dumb cbhc bricks in the past are almost 100% user error.

Oh for sure.

 

[V10lator]

The worst that happens with Aroma/Tiramisu coldboot is an update of the home menu overwriting the coldboot entry. That's not a brick through but the Wii U will just boot into stock firmware. In that case you just start healt&safety while holding (X) and re-run the coldboot setup.

I feel like you're even overselling how dangerous CBHC was to begin with

I noticed cases of "I buyed a Wii U off eBay, factory resetted it and it's bricked now, why?". So in my eyes the most danger of CBHC was people not deinstalling it before selling their consoles (and sometimes not even telling the buyer that there's a CFW).

//EDIT:

I probably will be booting into Aroma for Pretendo Network

Then you have no choice anyway:

Inkay is only supported on the release version of Aroma configured for autoboot/coldboot.

(Source: https://github.com/PretendoNetwork/Inkay )

 

[Ryab]

The worst that happens with Aroma/Tiramisu coldboot is an update of the home menu overwriting the coldboot entry. That's not a brick through but the Wii U will just boot into stock firmware. In that case you just start healt&safety while holding (X) and re-run the coldboot setup.


I noticed cases of "I buyed a Wii U off eBay, factory resetted it and it's bricked now, why?". So in my eyes the most danger of CBHC was people not deinstalling it before selling their consoles (and sometimes not even telling the buyer that there's a CFW).

I guarentee you a majority of bricks were people either formatting or deleting the account.

 

[Lostbhoy]

I guarentee you a majority of bricks were people either formatting or deleting the account.

So users then? Not the software??

Cars are dangerous but the driver is always to blame!

 

[V10lator]

So users then? Not the software??

When you get told for your whole live to factory reset a second hand purchased gaming console it's hard to say this is user error.

//EDIT:

the driver is always to blame!

What about burning lithium batteries? What about self-driving cars?

 

[Lostbhoy]

When you get told for your whole live to factory reset a second hand purchased gaming console it's hard to say this is user error.

//EDIT:

What about burning lithium batteries? What about self-driving cars?

I never said error I only said user

Your other points are sorta valid but again its down to regular maintenence and that is always on the user of any device or machine regardless of knowledge or know how. A sat nav will tell you where to go but you still have to decide if that route is open, safe, available ect.

Self driving cars fall into that category as im sure when you buy one you will be told the same disclaimer as a sat nav regarding manual takeover control and decision making for certain situations so yeah... The user is always at fault in these scenarios but part failure and software corruption is not the topic here!

Someone already said... People will be people and if your gonna buy something second hand you should gather all the info you need or you have failed right away. This is true again of any device or machine but again dont shift blame to the thing because person A didn't bother doing thier homework properly.... That's on them.

 

[Ryab]

So users then? Not the software??

Cars are dangerous but the driver is always to blame!

I felt that was quite obvious yes. User error is what causes them.

 

[V10lator]

Self driving cars fall into that category as im sure when you buy one you will be told the same disclaimer as a sat nav regarding manual takeover control and decision making for certain situations so yeah...

You can't buy such a car but anyway, there are cases where the time to grab the steering wheel was higher than the time to hit a passerby. And of course the driver was instructed to not have hands on the wheel while AI drives. The software could have moved the car away but impossible for the human... But the software didn't. Hard to blame the driver here in my eyes but yea, the drivers got blamed cause else it would be the car manufacturer who would be to blame but they want to stay legally safe.

Anyway, let's Just agree to not agree here.