Reply to thread

Message: <blockquote data-quote="fogbank" data-source="post: 1854279" data-attributes="member: 140488">I thought we already had anecdotal evidence that it was not related to the new boot1...? I have seen reports of users with the new boot1 that were able to fully hack their Wii.There is a possibility that it is related to the presence of a new IOS (IOS3) that was found by Title Lister on at least one "unhackable" Wii. In order to rule certain things out we would need to:1. Identify users with the new boot1 that have successfully hacked their Wii (already done).2. Identify users with the new IOS3 that have been unable to hack their Wii (already done).3. Identify users with the new IOS3 that have successfully hacked their Wii (NOT done?).In order to work on a FIX for this issue we would need to be able to identify the unhackable Wii's with 100% certainty before attempting to hack them beyond installing HBC. It may be possible to do this by detecting the presence of IOS3. There is at least one version of Title Lister that will work on these unhackable Wii's (title_lister_37_512). IF that version of Title Lister will work without having cIOS installed as IOS249 then that should be run on any new Wii before installing cIOS. At that point, if IOS3 is detected then cIOS should not be installed as IOS249.To my knowledge, what has not been tried is installing cIOS to an IOS slot other than 249 and recoding apps to use that IOS instead of 249. This would tell us if only IOS249 has been blocked for suid(0). This is unlikely, but testing the theory would be part of troubleshooting the problem.Again it will be difficult to make progress on the issue unless the "unhackable" Wii's can be identified with certainty before a hack attempt is made. Otherwise you will never know if a method worked, or if the Wii wasn't really "unhackable" to begin with.I would encourage anyone with a Wii having a higher serial number (lu64* or higher) to run Title Lister and see if IOS3 is listed. If we find one "hackable" Wii with that IOS then we know it is not related to the issue.</blockquote>

Verification

Search

Search

Reply to thread

Settings Notifications

Options