Hacking IOSUHAX CFW vs REDNAND

[KevinX8]

IT'S shit; what are you talking about, are you actually retarted? It's a good solution.

but like he said its permanent, changing the fw.img file will do you no good as it will just go in a bootloop like you said so its impossible to revert once actual permanent boot0 cfw (which activates before anything is even booted not adding an extra 40 seconds to boot time) comes out

 

[Kohmei]

Once Salt Releases a proper cfw you won't be able to update to it because they stated it might not work with the current rednand.

This is the biggest con of the current rednand. I don't want to have to reinstall all my games because I'm using a defunct and kludgy rednand that someone threw together that does nothing iosuhax doesn't.

 

[KevinX8]

OK let me chime in here as well.

*** Do not attempt ColdBoot ***

If you try that shit you are going to brick.

Let me explain real quick like.

Stage:1 Hardware checks software in mlc, hardware loads software AKA System OS.
Stage:2 OS checks sigs and whatnot for OS related security, I.E. Games and titles.
Stage:3 We boot isouhax through OS, in a vulerability within OS.
Stage:4 You want to patch files checked in OS by hardware?
Stage:5 You decide to make these changes then wonder why the fuck you bricked, because you can't tell hardware the files in OS are legit.
Stage:6 You post here whining about shit and we laugh at you.
Stage:7 After reading this, you decide not to *** Brick your WiiU ***

the current coldboothax those work since the system.xml is not sig checked or hash checked

 

[C0mm4nd_]

@KevinX8Can never be updated That's not 100% known whatsover, okay?

Pls....
When you update sysNAND/emuNAND the version is saved on a chip (SEEPROM)
So, if you load the outdated NAND won't load (like 3DS, it checks the version)

 

[Supster131]

Pls....
When you update sysNAND/emuNAND the version is saved on a chip (SEEPROM)
So, if you load the outdated NAND won't load (like 3DS, it checks the version)

 

[KevinX8]

Key word here is "apparently" so there is absolutely no confirmation

 

[C0mm4nd_]

I found a better explanation

@Reecey you are totally wrong rednand can't be updated as it bricks the wiiu nand the reason for this is because the wiiu stores firmware on two chips firstly on the nand and secondly on a eprom chip. When you switch the wiiu on the eprom checks the firmware version on the eprom matches the the firmware on the nand. If you update Rednand it will also update the eprom. So when you switch on the wiiu the firmware version on the eprom will be higher than the firmware on the nand so it won't boot anything and you will have a expensive brick. This has been discussed already in other threads. The 3ds only stores firmware in nand so that is why emunand can be updated on a 3ds.

 

[Supster131]

Key word here is "apparently" so there is absolutely no confirmation

That argument can be used both ways.

 

[KevinX8]

That argument can be used both ways.

Yes so let's just wait and see hum. Someone will have to test for us thought and risk a brick or if they have a hardmod spend 20 minutes undoing it

 

[Afraidium]

The only way around this is to patch the update and to patch the update process. Just saying.

 

[C0mm4nd_]

SEEPROM checks version in boot0:

Boot parameters (encrypted with Wii U SEEPROM key).
Structure containing parameters for boot0:
- 0x1D0 to 0x1D2 (0x02 bytes): boot1 version.
- 0x1D2 to 0x1D4 (0x02 bytes): boot1 NAND sector.
- 0x1D4 to 0x1DC (0x08 bytes): Empty.
- 0x1DC to 0x1E0 (0x04 bytes): CRC32 of data from 0x1D0 to 0x1DC.

Boot parameters (encrypted with Wii U SEEPROM key).
Structure containing parameters for boot0:
- 0x1E0 to 0x1E2 (0x02 bytes): boot1 copy version.
- 0x1E2 to 0x1E4 (0x02 bytes): boot1 copy NAND sector.
- 0x1E4 to 0x1EC (0x08 bytes): Empty.
- 0x1EC to 0x1F0 (0x04 bytes): CRC32 of data from 0x1E0 to 0x1EC.

(http://wiiubrew.org/wiki/Hardware/SEEPROM)

We need Wii U SEEPROM key for exploiting update-check

 

[Greggen]

Maybe abit ot but is there any work on injecting wii "VC"-titles? If so and that works with iosuhax it would be pretty awesome. Then we could finally skip that dual HDD requirement.

 

[xtheman]

The major problem with using rednand though is that when salts real tools come out it won't work with it. Meaning you have to reinstall all your games and backup and restore ALL your saves.

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

Maybe abit ot but is there any work on injecting wii "VC"-titles? If so and that works with iosuhax it would be pretty awesome. Then we could finally skip that dual HDD requirement.

Not yet. It doesn't look like something that is easily done either

 

[iAqua]

http://gbatemp.net/threads/sigpatch...ould-use-rednand-instead.448670/#post-6829935

 

[BIFFTAZ]

Once Salt Releases a proper cfw

That old chestnut. Hearing this a lot lately, That all.. Nothing else..

 

[Afraidium]

The major problem with using rednand though is that when salts real tools come out it won't work with it. Meaning you have to reinstall all your games and backup and restore ALL your saves.

You are inSALTing those who are working on the "fake" tools, don't be so snobbish.
People are trying to bring to this community free options to homebrew and backup loading.

Who cares if you have to reinstall games and saves. There are options for that. This is for early adopters. Things change, and as such, don't be so ungrateful.

 

[xtheman]

• As of now it cannot install titles created with NUS packer which means in the future when HBL RPX edition is released it will not work with IOSU CFW unless NUS packer is made to work with sysNAND

The games installed to my patched sysnand, work on my patched sysnand

From the maker

 

[KevinX8]

http://gbatemp.net/threads/sigpatch...ould-use-rednand-instead.448670/#post-6829935

It's funny I make a fair comparison of each and you make a thread about how terrible iosu cfw is nice one

 

[iAqua]

It's funny I make a fair comparison of each and you make a thread about how terrible iosu cfw is nice one

Fair? Please add to the cons of sysNAND that the current coldboot doesn't support it, add to redNAND's pros that it actually does support sysConfig. That'll be a little more fair.

 

[xtheman]

Fair? Please add to the cons of sysNAND that the current coldboot doesn't support it, add to redNAND's pros that it actually does support sysConfig. That'll be a little more fair.

That is fair yes.