Hacking IOSUHAX CFW vs REDNAND

  • Thread starter Thread starter KevinX8
  • Start date Start date
  • Views Views 37,437
  • Replies Replies 217
  • Likes Likes 4

Which do you use?

  • REDNAND

    Votes: 41 29.1%
  • IOSUHAX CFW

    Votes: 82 58.2%
  • Vanilla all the way son

    Votes: 18 12.8%

  • Total voters
    141

KevinX8

Proud user of The Dark Theme
Member
Joined
May 12, 2016
Messages
960
Reaction score
566
Trophies
0
Age
35
Location
Down there
XP
1,033
Country
Currently there are two ways you can use to get full access to your wii u to do whatever you want to it they are iosu cfw and rednand respectively. This thread is mainly for newcomers unsure of what to install on their brand new haxorz machines. On this Thread I will post there pro's and con's for each one and update them as time goes on. Eventually once boot 0 cfw comes out iosu CFW will obvs win so rednand will become redundant but for now its still useful so wait until then.

Why do I want any cfw?
The main reason you would want custom firmware is to install unsigned tickets for things like eshop titles and DLC. You can also install Regionhax allowing you to run any game region free forever. Atm its not very useful to the end user just for experimenting really

IOSU CFW
Pros

  • sd card of any size will work with this
  • uses only 14MB on sd compared to the 8GB/32GB of redNAND
  • Works with vWii titles installed with Wup installer
  • SD card can be removed while in operation without utter anihilation
  • Can return to stock any time (those it for you on every reboot lol)
Cons
  • Not 100% safe as it mods sysNAND only temporarly and to reactivate the mods (sig patches etc.) has to be launched again. This makes it so if you modified some critical file incorrectly your wii U will become a fancy black/white brick
  • Can't install sysConfig Tool as it is a system title
REDNAND
Pros

  • Should be completely safe to mod anything without worry of brick as you can revert from backup
  • works with Official Sysconfig Tool(Modified one availble in the wild that works on sysNAND not recommended to install thought)
Cons
  • 64GB(black/premium)16GB(white/basic) sd card or higher required to install
  • Dumping your system can take between 1-9 hours depending on your NAND/SD setup
  • System will be limited to the speeds of your sd card so a slow sd will dramatically effect load times
  • Can't format without bricking
  • if you want to return to stock you will lose everything you have done on your redNAND, this includes all title installs and save data (wupserver can be used to transfer saves but not titles)
  • UNCOFIRMED:According to the current information we have it can never be updated due to the SEEPROM memory not being redirected correctly on REDNAND and once it checks last run latest firmware it will brick unless sysNAND is same firmware
For anyone that is unaware you can install unsigned titles of any kind on both just fine(includes eshop only titles,DLC etc.)

NUSpacker on sysNAND now works if you use @Maschell 's fork here

If you feel I have left any pros or cons out feel free to leave a reply with what I missed

You can weight out what is best for yourself from these pros and cons, the current iosuhax cfw I use can be found here and is maintained by @FIX94 and for redNAND installs the recommended fork is @dimok 's one here , neither of these could have been possible without @smealum so thank him for his work too.
 
Last edited by KevinX8,
Isn't another pro for redNAND the fact that it allows keeping the Wii U to a hackable firmware (on sysNAND) but still having access to the latest firmware (on redNAND)?
Well, not relevant today since the latest is hackable, but maybe it should be added anyway as a possibility if it's the case.
 
You should add the sysnand cfw can run Wii VC (You know the special wii eshop titles with gamepad support)
And Rednand can't run vWii.
yeah thats true will add that also will add sysconfig tool thosent work on sysNAND because its system titles aswell
 
wtf, iosuhax is the "tool-chain" that permits us to create some patched fw.img so it should be "redNAND fw.img VS WUPserver fw.img"
 
Isn't another pro for redNAND the fact that it allows keeping the Wii U to a hackable firmware (on sysNAND) but still having access to the latest firmware (on redNAND)?
Well, not relevant today since the latest is hackable, but maybe it should be added anyway as a possibility if it's the case.
Updating in rednand will brick it so that is pointless (Several devs have proved that)
 
The best would be sysnand with coldboot recovery like we had on wii
 
Cons
  • 64GB(black/premium)16GB(white/basic) sd card or higher required to install
  • takes almost a whole day to dump
  • System will be limited to the speeds of your sd card so a slow sd will dramatically effect load times
  • Can never be updated
My dump/install took around 1 1/2 hour to dump, + System speed's are the same for both nands here.

You should add the sysnand cfw can run Wii VC (You know the special wii eshop titles with gamepad support)
And Rednand can't run vWii.

True, But we still have access to sysNAND that has a working vWii.
 
wtf, iosuhax is the "tool-chain" that permits us to create some patched fw.img so it should be "redNAND fw.img VS WUPserver fw.img"
Wupserver is on rednand too so that thosen't really matter CFW sounds better anyway since thats what it pretty much
 
IOSUHAX CFW sysNAND.
All homebrew are in the very early stages anyway. Everything is too early to say anyway.

My hopes for NTR viewer U on sysNAND!
 
My dump/install took around 1 1/2 hour to dump, + System speed's are the same for both nands here.



True, But we still have access to sysNAND that has a working vWii.
Its different for everyone it seems some people report 9 hours to dump or even longer, guessing the NAND chip your wii u came with and sd card would affect the dump speed also if you have some Class II 64GB sd card from china rated at 10MB/s it will only run at that speed so yes it will affect rednand speed
 
  • Like
Reactions: Jaythe4
Unless you bricked vwii. Which then your limited to Wii VC because it uses OSv1 instead of your bricked OSv0
Before or after making a redNAND image? If you bricked your vWii before making a redNAND image, It'll be exactly the same on the redNAND image after... Bricked. RedNAND is 1v1 image (Pretty much) of sysNAND on SD card with sig patches & so on.
 
Last edited by BIFFTAZ,
Before or after making a redNAND image? If you bricked your vWii before making a redNAND image, It'll be exactly the same on the redNAND image after... Bricked. RedNAND is 1v1 image of sysNAND on SD card with sig patches & so on.
But rednand can't boot OSv1 (Wii VC) meaning you can't use any wii related software after bricked vwii
 
  • Like
Reactions: BIFFTAZ
Never going to happen. NTR viewer only worked on new 3ds because it was running off the extra hardware of the new 3ds which is also why no old 3ds support.
Mario Kart 8 can do screen recording so I don't see why this can't be implemented into other games... Will just have to wait and see I guess
 

Site & Scene News

Popular threads in this forum