Hacking Wii Update: 3.3U Out

  • Thread starter Thread starter yumms
  • Start date Start date
  • Views Views 126,660
  • Replies Replies 655
FGOD said:
it only blocked fike signed discs not fake signed channels or anything else...
That is incorrect. The IOSes updated with the "first" 3.3 update would not install fakesigned content either. But as they only patched IOSes 30 (used by the System Menu) and 37 (unused til now), there were enough other IOS versions left unpatched to use to install fakesigned content. With this update, however, all the IOSes have been patched not to accept anything fakesigned, so there's nowhere to turn to.

Edit: The system still accepts anything that is already installed as legit, that's why fakesigned channels will still run (sort of, some other functions have been patched, too). There's just no way to install them right now.
 
what's the point of keeping all the old IOS's? if they just let everything run through the latest patched one, wouldn't that be much easier for Nintendo?
 
would it be possible to edit some homebrew applications to run under cIOS like a NAND dumper? also would it be possible just to delete every ios except 30, 51, and cIOS and restore the old versions from a game disc?
 
already updated to 3.3e
Pal Wiikey 1.9s

I was having problems with the latest games all giving a black screen or error 001 , nothing seems touched really, all my older games play , the ones that were giving me black screens still do so , never had any vc titles or homebrew . The games that were giving blackscreens are all usa imports , used brick blocker and regionfrii all the same , maybe just blocks the play of other region games ?

**EDIT* just tried ntsc high school musical untouched and it worked ??????
 
QUOTE(FGOD @ Oct 24 2008, 02:24 AM)
it only blocked fike signed discs not fake signed channels or anything else...
That is incorrect. The IOSes updated with the "first" 3.3 update would not install fakesigned content either. But as they only patched IOSes 30 (used by the System Menu) and 37 (unused til now), there were enough IOSes left unpatched to do the "dirty work". With this update, however, all the IOSes have been patched not to accept anything fakesigned, so there's nowhere to turn to for the dirty deeds.
mikeyt1998 said:
to the above...

that was a great first post XD


I Just laughed my ass off!
Sry
 
kedest said:
what's the point of keeping all the old IOS's? if they just let everything run through the latest patched one, wouldn't that be much easier for Nintendo?

because older games require older IOS versions
 
alucard_xs said:
so the zelda thing does not work anymore ?
If by "zelda thing" you are referring to the Twilight Hack: No, it still works. It's the installers that are started by the Twilight Hack that have to be updated.
 
diegoesgriam said:
Anyone knows if it anytitledeleter or wadmanager can erase things after the update??

you can still delete stuff, I accidently erased everything I had installed exept the Homebrew Channel
frown.gif

(I used the wad uninstaller...)
 
Ur-Quan said:
boab said:
How will the update affect bootmii seeing as the bootmii-core is fakesigned?
It's not affected at all. Boot1, the instance that is starting BootMii, has the fakesign bug and is not updateable.

Cool. I had a feeling it might be unscathed but I wasn't sure if it was an IOS call that done the install of boot2 and therefor was fixed by the update.
 
boab said:
Ur-Quan said:
boab said:
How will the update affect bootmii seeing as the bootmii-core is fakesigned?
It's not affected at all. Boot1, the instance that is starting BootMii, has the fakesign bug and is not updateable.

Cool. I had a feeling it might be unscathed but I wasn't sure if it was an IOS call that done the install of boot2 and therefor was fixed by the update.

there will likely be issue(S) with the install, this is true, but marcan will work them out. the fact that the fakesign bug is in boot1 is true, and relevant, but this update will likely have some affect on the installation, you just don't need to worry 'cuz there is no doubt he has ways to get around that, as I'm pretty sure he's said when he talked about BootMii and future updates a few weeks ago. althought it is good that the bug is in boot1's, we don't control boot1 (there isn't much to control anyways)...and so it won't play an integral role in the install.
 
IF you have a WORKING WAD MANAGER 1.21 via a cIOS on the new update, please read:


have you tried using wad-manager to install an IOS35 wad from the SMG disc or newer game?

do so if you have a chance, and afterwards let me know if you can run YaWNd, and attempt to downgrade with AnyRegion Changer 1.1.
 

Site & Scene News

Popular threads in this forum