The location of fw.img is dependent on the id for the inject.
Do you know how to figure out the ID? Or is it always random
The location of fw.img is dependent on the id for the inject.
Do you know how to figure out the ID? Or is it always random
C:\ProgramData\JNUSToolDownloads\Rhythm Heaven Fever [VAKE01]\codeDo you know how to figure out the ID? Or is it always random
Almost done! What command do i use?To patch fw.img use my fork of nfs2iso2nfs https://github.com/ymweiss/nfs2iso2nfs
I think your only option to recover is restoring a nand backup with hardware unless you had ISFShax installedAlmost done! What command do i use?
Post automatically merged:
Bad news, i used the -patch option and even replacing all fw.imgs didnt work. Input does not register in priiloader
Post automatically merged:
Nevermind i bricked my wiiu sadly by replacing each
Its not your fault @Karlmann dont worry it was my stupidity
Do I use this to apply the ssl.ips patch that you posted earlier?To patch fw.img use my fork of nfs2iso2nfs https://github.com/ymweiss/nfs2iso2nfs
Planning to get a verified hardmodder to repair it. Costs 30$. In about 2 weeks ill ship it to them. Hopefully all goes well!@awesomee I'm sorry that happened to you (we already talked about this through dms, if anyone is reading this). Consider getting a Raspberry Pi Pico 2 (W) and try UDPIH and see if that works. Next time install ISFSHax!!
Do I use this to apply the ssl.ips patch that you posted earlier?
UDPIH cannot work if the OSv10 fw.img doesn't boot, which is the case here.Consider getting a Raspberry Pi Pico 2 (W) and try UDPIH and see if that works.
On closer inspection, the ssl.ips is invalid. Some offsets in the ELF header mismatch with their associated binaries. Do not use it.@awesomee I'm sorry that happened to you (we already talked about this through dms, if anyone is reading this). Consider getting a Raspberry Pi Pico 2 (W) and try UDPIH and see if that works. Next time install ISFSHax!!
Do I use this to apply the ssl.ips patch that you posted earlier?
I should have at least specified system titles to have prevented this issue. I apologize for the miscommunication and do not modify system titles (excluding OSv0 and OSv1 due to those being for backward compatibility)Planning to get a verified hardmodder to repair it. Costs 30$. In about 2 weeks ill ship it to them. Hopefully all goes well!
And ill be moving on from this. Learned my lesson
I accept your apology. Luckily it should be fixable with some De_fuse modchip. Next time i try this ill be sure to test it on some safe environmentI should have at least specified system titles to have prevented this issue. I apologize for the miscommunication and do not modify system titles (excluding OSv0 and OSv1 due to those being for backward compatibility)

UDPIH cannot work if the OSv10 fw.img doesn't boot, which is the case here.
UDPIH exploits a flaw in the OS contained within the fw.img. It cannot work if the fw.img is broken.Any idea if the pull request “sleep” could fix this? It seems to connect before the console turns on, maybe code could be executed before it fails booting?
@Karlmann
Alrighty for future reference can you please specify where the files go? Thanks in advance!
Ill consider trying this again on something like ISFSHax / REDNand to make sure nothing goes wrong.
Alrighty! Thanks a ton! This should help clarify stuff. Dont feel too bad about it, keep up the great work!View attachment 495734The code directory for any VC title must contain the following files.
Due to the issue where the ES calls do not work due to issues with the HAI-IOS kernel, I am changing my approach. At a high level, this approach consists of replacing the standard OHCI1 module with the one from HAI-IOS. I hope to get the gamepad to work with physical discs and titles loaded from USB loaders.
Does this mean that Wii VC injects would now boot under the ''normal'' mode of the vWii instead of ''HAI'' while only using the HAI-IOS's OHCI1 module?Due to the issue where the ES calls do not work due to issues with the HAI-IOS kernel, I am changing my approach. At a high level, this approach consists of replacing the standard OHCI1 module with the one from HAI-IOS. I hope to get the gamepad to work with physical discs and titles loaded from USB loaders.
Correct.Does this mean that Wii VC injects would now boot under the ''normal'' mode of the vWii instead of ''HAI'' while only using the HAI-IOS's OHCI1 module?
Does your HAI-Riivolution github have anything to do with this?Additionally, with Riivolution's source being available, a modified version of Riivolution should work when a minimal cIOS layer is applied to IOS 37.
The github repository does not have any changes from the Riivolution source. The only thing I did with it was attempting to have Riivolution work on HAI-IOS, which was unsuccessful. This would have addressed Riivolution not being usable for Wii VC titles legitimately purchased before the eshop closed.Does your HAI-Riivolution github have anything to do with this?