Toggle sidebar

Homebrew Unable to install Isfshax

  • Thread starter Thread starter benefits
  • Start date Start date
  • Views Views 2,631
  • Replies Replies 18
benefits

benefits

Member
Newcomer
Level 2
Joined
Mar 2, 2025
Messages
11
Reaction score
1
Trophies
0
Age
16
XP
111
Country
Ireland
I've been trying to install isfshax on my bricked Wii U using de_fuse, unfortunately I haven't been able to get a fully functional OTP, but I was able to get a minimally working OTP using otp-builder.py which should allow me to install isfshax. But Isfshax says this:
Console Type: Retail
boot1 version: Unsupported (8354)
isfshax: Cannot be installed
Click to expand...
Is there any workaround to the unsupported boot1 version? any suggestions are appreciated!!
 
Last edited by benefits,
you could get the latest boot1 from another Wii U and flash it to this one using minute. Make sure you have a complete slc dumpe copied somewhere else first.
 
SDIO said:
you could get the latest boot1 from another Wii U and flash it to this one using minute. Make sure you have a complete slc dumpe copied somewhere else first.
Click to expand...
I don't have another Wii U to source a Boot1. are there any available downloadable Boot1 dumps online?
 
SDIO said:
You could remove or change the version check in the isfshax installer to allow installing it on your boot1 version: ((link removed from quote because i'm still Noob rank.))

It should work with your boot1 too
Click to expand...
I can't compile Isfshax Installer (after removing the version check) for the life of me. I don't have any major experience in C, despite downloading all the compilation dependencies, I still run into errors when attempting to run the makefile.
 
This should allow the install on unsupported boot1 versions

EDIT: ISFShax should work with v8296, v8325, v8377 it does not work with v8339, v8342, v8354. Thanks Rairii
 

Attachments

Last edited by SDIO,
  • Like
Reactions: benefits
SDIO said:
This should allow the install on unsupported boot1 versions

EDIT: ISFShax should work with v8296, v8325, v8377 it does not work with v8339, v8342, v8354. Thanks Rairii
Click to expand...
Is there any way to get it to work with v8339 that i have?
Post automatically merged:

Mine says failed to find unpatched superblocks?
 
Last edited by Tomas_B,
SDIO said:
Then your OTP probably doesn't have the correct SLC key. You can test it with the NAND-extractor: https://github.com/koolkdev/wiiu-nandextract/releases/tag/0.1.0

Also all seeproms use the same key. So you could get the seeprom key and the slc boot1 from another console and use that to update the boot1 on your console
Click to expand...
the OTP seems to be correct atleast in the NAND extractor. to bad i dont have another console to dump thoose files from...
When i check my slc dump in nandbincheck i have 64 bad superblocks.
 
The superblocks aren't encrypted, only hmaced. I guess the NAND extractor ignores the hmac, but if you extract any file it will likely only contain garbage. You could try with one of the xml files. The nandBinCheck probably complains about the HMAC of the superblocks, right?
 
Hi i have som pictures of everything so there will be no miss understandings due to english not being my first language :)

I have included the pictures of the errors that ISFShax installer gives me and what nandbincheck tells me.

any ideas how to get any further with this?

The otp i use is a minimal otp created with your python scriprt from my extracted crypto.dmp
 

Attachments

  • nandbincheck.png
    nandbincheck.png
    26.9 KB · Views: 50
  • Nandbincheck1.png
    Nandbincheck1.png
    20 KB · Views: 44
  • ISFShax error.png
    ISFShax error.png
    9.7 MB · Views: 46
  • ISFShax.png
    ISFShax.png
    8.4 MB · Views: 56
yes the problem is tht your otp.bin is bad. You should not try to install ISFShax with that or it will corrupt the SLC.

If you have an older firmware, which the strange boot1 indicates, then the addresses of the kes in the dump might be different, so extracting them probably goes wrong.

So what I would try would be:
1. make SLC and SEEPROM backup and put it in a save place
2. get boot1_slc and otp (for the SLC key) bin from another console.
3. flash the boot1 and let it update the SEEPROM
4. remove the otp.bin
5. try dumping the otp again with PRSHhax

Don't try to to boot or do anything else with the otp from the other console.
 
Hey there, I used your ios.img on 8354. Stupid me didn't read correctly.

Now I have a blue blinking light. I have backups of the SLC, but I used Paid the Beak and now can't trigger the minute menu anymore.
Post automatically merged:

Triggered PTB again and uninstalled ISFXHAX.
Post automatically merged:

Now I am stuck. It won't let me update boot1 to the newest one. Also not with the correct otp.bin from the donor board.

I can not reflash the (USB)MLC as the installed software is not 5.5.x I suppose. The blue light just does not start to blink. ... Any idea? Thanks in advance. The MLC-Chip is dead. (Hynix from 2015)
 

Attachments

  • 20250913_202111.jpg
    20250913_202111.jpg
    6.7 MB · Views: 47
Last edited by classiphil,
when you use PTB, you don't need any otp.bin. What is stopping you from flashing the latest boot1?
 
SDIO said:
when you use PTB, you don't need any otp.bin. What is stopping you from flashing the latest boot1?
Click to expand...
Minute does not let me flash the boot1_slc.raw. It says it is forbidden, as no isfshax or defuse is present.
Post automatically merged:

I just followed your guide for redirecting MLC to a rednand-SD. No luck. The LED just stays purple after GoGoGo. (My Wii U is disassembled, so it is the red and blue LED.) Could it be the rather old system software? I doubt there is a way to update that with a dead MLC chip. I ordered a Toshiba-emmc. But even when it will work again, I cannot make minute starting the installation of the MLC-system-titles.
 
Last edited by classiphil,
SDIO said:
Try flashing boot1 with this minute: https://gbatemp.net/threads/how-to-set-up-isfshax.642258/post-10705309
Click to expand...
Thanks. Did the trick. Isfshax is installed.
But still purple led after Go Go Go when trying to set up Rednand or USBMLC. I saw the partition mismatch. But that does not seem to be the problem.
Post automatically merged:

I followed your hint to using ios_orig.img from fw.img from jnustool. "We are blinking." :)

Guys, after 7 years this Wii U is up and running. I will link to the thread i mentioned above after celebrating.

Thanks to the whole community.
Post automatically merged:

SDIO said:
Maybe the IOSU on the SLC is to old. If you have a SLC dump, which you should have, you can extract it and look at the app.xml to see which version the iosu has.

If you just want to make it work fast, I would siggest downloading the latest iosu with jnus and put the fw.img from it as ios_orig.img on the sd. Then you can use the second option in minute `Patch and boot ios_orig.img`.
I wouid then suggest you download also the SLC titles and put them also in the wafel_install, so the titles on the slc will be updated to during the mlc rebuild
Click to expand...
 
Last edited by classiphil,
  • Like
Reactions: SDIO

Site & Scene News

Go to forum More news

Popular threads in this forum

Strange Blue Blinking Wii U

Hacking Homebrew Project  Modernized YouTube for Wii U

Feedback  Community Overclock Stats: A5X vs B1X Motherboards

Wii Games Performance on Wii U (vWii C2W Overclock) – Community Testing & Results Sharing

Gaming Homebrew Misc Project  Roséverse - a 1:1 Miiverse revival by Project Rosé!

Can the Wii u pro controller works for Wii games ?

My dad's Wii U cannot install Aroma. HELP!!

I broken my wii u