Hacking IOSUHAX CFW vs REDNAND

[C0mm4nd_]

Then add the fact that you need a SD card for sysNAND as a con, you just said it yourself, it's a requirement, so it's a con.

You can use your phone card, your 3DS card, your camera card

 

[KevinX8]

Then add the fact that you need a SD card for sysNAND as a con, you just said it yourself, it's a requirement, so it's a con.

if it applies to both its not a con lol both require you to lauch them throught some exploit first aswell and I didn't add that both require you to have decent knowledge at compiling or searching throught dodgy pages on "that iso site"

 

[iAqua]

if it applies to both its not a con lol both require you to lauch them throught some exploit first aswell and I didn't add that both require you to have decent knowledge at compiling or searching throught dodgy pages on "that iso site"

Then remove it as a con for redNAND.

 

[C0mm4nd_]

You are retarded.
We know the case difference is "IOSUHAX can be run from any SD card you might be having lying around"
while full redNAND is for those who just happen to have 64 gig cards around. Wii/3DS etc consoles ship with 2 or 4 gig card anyway. Wii U does not but anyone who has done nintendo for a while will have bunch of smaller sized SD cards lying around.

Stop posting any time.

Then remove it as a con for redNAND.

 

[DeslotlCL]

Hey guys, instead of flaming and getting warning points, do you want a nice and simple solution?

For fuck sake, wait for team salt.

I'm just here, laughing at this, with my vanilla wii u and pirated titles, waiting patiently for an user friendly cfw solution from team salt. They can take all the time they want, i can wait and do not need to rush anything.

 

[KevinX8]

Then remove it as a con for redNAND.

um where the hell is your common sense gone? con: "a disadvantage of or argument against something" having to use a 64GB sd is a disadvantage for redNAND. you are not required to use a 64GB card for iosu cfw you can use a 64mb sd card if you even had on. Having to use a sd card on both is not a con as neither are at a disadvantge from that

 

[icw35]

if 20 euros is cheap for you then cool but it still is a con since it is a requirement for redNAND and if you don't have one redNAND not possible but iosu cfw is

It's all about perspective mate.

€20 for me = 4 pints of beer (so stay sober for 48h - I don't drink much, for some this would be "stay sober for 2 hours") or 2.5 NHS prescriptions (f'ing rip off when I pay taxes but hey ho, hope I don't get ill any time soon). When I compare this to the €1000's I saved on games (that I wouldn't have bought mind you), well, it's nothing (if you have a job). Same reason I paid £6 for some shite DS game for haxchi. £6!!! F'ing rip off but in relative terms...a drop in the ocean if I can have a pretty Homebrew Channel on my WiiU (which is really the only reason I did it, so sad).



So guys lighten up! Have fun with your WiiU and let's not bitch about it! (Unless you brick it, lol).

 

[75mak]

The biggest decision for those still undecided is which one is more likely to be adopted and developed as the future...

For me as a vanilla (Brazilian USB method user). I see more development for iosu + sysnand side. If I adopt redNand, the biggest problem for me would be I would probably have to reinstall all Brazil method install again in future, and the SEEPROM using redNand will definitely cause issues down the line.

Once sysnand+iosu cfw has a safe coldboot method and develops a method to install titles safely etc. I will jump on that method. If I had to choose one now I would still choose sysnand cfw method for VC Wii titles. But right now I'm sticking to vanilla as the other stuff isn't that important for me

 

[icw35]

The biggest decision for those still undecided is which one is more likely to be adopted and developed as the future...

For me as a vanilla (Brazilian USB method user). I see more development for iosu + sysnand side. If I adopt redNand, the biggest problem for me would be I would probably have to reinstall all Brazil method install again in future, and the SEEPROM using redNand will definitely cause issues down the line.

Once sysnand+iosu cfw has a safe coldboot method and develops a method to install titles safely etc. I will jump on that method. If I had to choose one now I would still choose sysnand cfw method for VC Wii titles. But right now I'm sticking to vanilla as the other stuff isn't that important for me

I hear ya bro. Same here. Can't be bothered to re-install everything and with this rednand update brick...gives me the heeby jeebies.

 

[AboodXD]

This isn't really accurate... :/

 

[KevinX8]

This isn't really accurate... :/

Care to make it more accuate then? any help is much appreciated but posting nothing is not helpful at all

 

[AboodXD]

By IOSUHAX CFW, you mean @FIX94's repo, right?

iosuhax isn't really a cfw, neither is redNAND.

 

[EclipseSin]

@KevinX8 Just a two things for you...

System Config Tool can be installed to sysNAND with a proper package (which will not be provided here), and it will not take over the Home/System Menu. It also will only be usable while in CFW. That said, don't mess with it if you do not know what you're doing, as there are some options that can cause a brick.

Packages made using NUSPacker will work on sysNAND by either using a newer CFW (wupserver fw.img) with extra sigpatches, or by manually modifying the tik and tmd. I do the latter and have no problems.


That said, redNAND *IS* safer if you're looking for brick protection. If you're not going to be retarded, sysNAND is just fine.

Thanks. Later man.

 

[KevinX8]

By IOSUHAX CFW, you mean @FIX94's repo, right?

iosuhax isn't really a cfw, neither is redNAND.

please enough do I really have to explain again. What you are used to is a permanent/semi-permanent cfw. The definition of cfw: "Custom firmware, also known as aftermarket firmware, is an unofficial new ormodified version of firmware created by third parties on devices such as video game consoles and various embedded device types to provide new features or to unlock hidden functionality." this completely applys to both as they are both cfw temporarily
the definition those not state it has to be permanent and also all 3ds cfw is temporary aswell it is just injected with arm9lh on boot

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

@KevinX8 Just a two things for you...

System Config Tool can be installed to sysNAND with a proper package (which will not be provided here), and it will not take over the Home/System Menu. It also will only be usable while in CFW. That said, don't mess with it if you do not know what you're doing, as there are some options that can cause a brick.

Packages made using NUSPacker will work on sysNAND by either using a newer CFW (wupserver fw.img) with extra sigpatches, or by manually modifying the tik and tmd. I do the latter and have no problems.


That said, redNAND *IS* safer if you're looking for brick protection. If you're not going to be retarded, sysNAND is just fine.

Thanks. Later man.

can you link me to the repo with the extra sig patches? also I thought if you install any system title it bricks wii u? or is the one you are refering to patched to have a different title id?

 

[EclipseSin]

please enough do I really have to explain again. What you are used to is a permanent/semi-permanent cfw. The definition of cfw: "Custom firmware, also known as aftermarket firmware, is an unofficial new ormodified version of firmware created by third parties on devices such as video game consoles and various embedded device types to provide new features or to unlock hidden functionality." this completely applys to both as they are both cfw temporarily
the definition those not state it has to be permanent and also all 3ds cfw is temporary aswell it is just injected with arm9lh on boot

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


can you link me to the repo with the extra sig patches? also I thought if you install any system title it bricks wii u? or is the one you are refering to patched to have a different title id?

Maschell's WUPServer FW: https://github.com/Maschell/iosuhax/tree/bb932c4a6e75264c8a73e49d223738ee2a9ff5dd

And yes, you change the title ID as well as app type.

 

[thaikhoa]

As far as I understand FIX94 branch is just a custom FW and WUPserver...
For whatever reason I am under impression FIX94's github iosuhax does not have sigpatches, and those are separate modifications by someone..?


You are retarded.
We know the case difference is "IOSUHAX can be run from any SD card you might be having lying around"
while full redNAND is for those who just happen to have 64 gig cards around. Wii/3DS etc consoles ship with 2 or 4 gig card anyway. Wii U does not but anyone who has done nintendo for a while will have bunch of smaller sized SD cards lying around.

Stop posting any time.

FYI, to install game to the system using wupinstaller, we still need a large capacity sd card.

 

[KevinX8]

FYI, to install game to the system using wupinstaller, we still need a large capacity sd card.

That thosen't matter this is just obvious if you download a 20 GB game you will need 20 GB of sd card space

 

[Sumea]

FYI, to install game to the system using wupinstaller, we still need a large capacity sd card.

Yes, up to 32 gig is very nice to have. But say, with IOSUHAX on SYSnand you could also just region mod your Sysnand and import discs. REDnand needs a large SD card no matter what usecase while IOSUHAX needs it depending of the usecase.

I am not retard, yes most people will want it for the specific usecase of installing stuff on their console so that is most people. But even for 32 gig Wii U then a 32 gig card is enough for anything you want with IOSUhax.

And just mind you I am running REDnand on my 2nd Wii U and nothing on my first currently. I am planning to get IOSUhax so I can region modify sysnand on my first Wii U (but I will bother to do it when more japanese games get out in the wild in legit USB format)

 

[AboodXD]

please enough do I really have to explain again. What you are used to is a permanent/semi-permanent cfw. The definition of cfw: "Custom firmware, also known as aftermarket firmware, is an unofficial new ormodified version of firmware created by third parties on devices such as video game consoles and various embedded device types to provide new features or to unlock hidden functionality." this completely applys to both as they are both cfw temporarily
the definition those not state it has to be permanent and also all 3ds cfw is temporary aswell it is just injected with arm9lh on boot

LOL, I know what a cfw is. redNAND (NAND redirection) is just loading your dumped NAND from SD Card, that's it.
All the modifications are done later...

Feel free to correct me though.

 

[KevinX8]

LOL, I know what a cfw is. redNAND (NAND redirection) is just loading your dumped NAND from SD Card, that's it.
All the modifications are done later...

So your point is? It thosen't change the fact it modifies the system firmware albeit temporarly but like I said cfw those not have to be permanent. Lets just stop quarreling over this its just a word anyway aeof