Hacking how to check wii for unmodified ios?

[blueagent004]

It is highly recommended to install Priiloader only on a Wii with only unmodified IOSs!

how do i check my second handed wii console to see if its ios has been modified or not?

thanks for the help!

 

[GreyWolf]

http://gbatemp.net/threads/posting-a-system-check.300279/

 

[blueagent004]

SysCheck v2.3.2 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on vIOS58 (rev 6176).

Region: PAL
System Menu 4.3E (v514)

Drive date: 02.13.2007
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x11
Console ID: 72906558
Console Type: Wii
Shop Channel Country: United Kingdom (110)
Boot2 v4
Found 67 titles.
Found 46 IOS on this console. 14 of them are stub.

IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6400): Stub
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): No Patches
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249[56] (rev 65535, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 65535, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10
Report generated on 08/25/2018.

------------------------------------------

i ran syscheck on my wii.

though i don't really understand what "Stub" or "Trucha Bug" means, also bootMii is installed on IOS254, does this mean i can't install prilloader then?

thanks so much for letting me know!

 

[FrenezyFr]

Yes it is recommended to install Priiloader but you will need to install IOS236 before
For IOS249 I will have recommended d2x-v10beta52
and with d2x-v10beta52 installed the CIOS, IOS245 base 37, IOS246 base 38, IOS247 base 53, IOS248 base 55, IOS251 base 58, for a more complete hack.

 

[Cyan]

doesn't priiloader installer use AHB now ? you don't need IOS236 on newer homebrew.

Blueagent : if you are not sure, post your syscheck report and we can tell you if there's any problem.

 

[XFlak]

doesn't priiloader installer use AHB now ? you don't need IOS236 on newer homebrew.

Blueagent : if you are not sure, post your syscheck report and we can tell you if there's any problem.

Because of the occasional HBC network connection bug crash impacting apps loaded with AHBPROT I think the priiloader 236 installer is safer than the AHBPROT one

Edit: at OP, just use ModMii if u are concerned you don't have the optimal set up

 

[GreyWolf]

Priiloader runs under the system menu IOSes and they do not have AHB access. That IOS 236 is just IOS 36 with the AHB_PROT flag enabled.

 

[XFlak]

Priiloader runs under the system menu IOSes and they do not have AHB access. That IOS 236 is just IOS 36 with the AHB_PROT flag enabled.

I'm talking about the installer, not priiloader itself. Priiloader runs off of the system menu IOS but the 236 installer obviously uses 236 (and yes I'm aware it's just a patched 36) and the ahbprot installer uses whatever IOS the HBC is using (ideally 58).

Any time u launch an app from the HBC using ahbprot there is a risk that it will crash (something to do with failing to establishing a network connection, I can't recall specifics). If you're installing a patched ios 36 to slot 236 and it fails its no big deal, you don't need 236 for the wii to function so u can try again. But if you use an ahbprot enabled priiloader installer and it crashes at the wrong moment u got yourself a brick.

Edit: more info on the bug I'm referring to here: https://gbatemp.net/threads/how-to-fix-the-connection-issue-while-running-in-ahbprot-mode.301061/

 

[Cyan]

I didn't know about this bug. I learn new things every days.

Daveboal seems to tell there's a fix to that issue, so some homebrew have been using the fix ? not priiloader installer?
I've read his thread, but I didn't really understand what the fix is. it seems it's only a check if ahb is enabled or not.
I'm particularly curious about this post, which can enable ahb access from the installed dol in priiloader, nor if we can really just call sys_call54 whenever we want.

 

[XFlak]

To the best of my knowledge a fix was never pushed for the priiloader installer. It definitely wasn't released at the time, but I'll concede it's possible an update was pushed during my 'wii-tirement' and I missed it.


I wonder if the open homebrew channel has this fixed? If so, a solution might be to install the official HBC using the hackmii installer, then install the open HBC using ahbprot (and if it fails who cares its not risky), then use the open HBC to launch other ahbprot tools safely.

Edit:
@FIX94, I know you have a mod of the open HBC on github, I was wondering if you ever considered a fix for this particular issue.

 

[GreyWolf]

That's very old. I run my fork of USB Loader GX as the default HBC IOS (58) all the time and networking works fine.

AHB isn't a brick risk, writing to NAND is. Whether you're running the installer from the patched IOS 36 or the HBC with <ahb_access /> tag in meta.xml it is running in the same mode. Updating officially with a disc or online has the same risk if something goes wrong.

 

[XFlak]

That's very old. I run my fork of USB Loader GX as the default HBC IOS (58) all the time and networking works fine.

AHB isn't a brick risk, writing to NAND is. Whether you're running the installer from the patched IOS 36 or the HBC with <ahb_access /> tag in meta.xml it is running in the same mode. Updating officially with a disc or online has the same risk if something goes wrong.

I agree that the risk is writing to critical parts of the nand, but if u launch an app using the HBC on a wii without network access and ahbprot enabled there is a solid chance of a crash (unless the app itself takes countermeasures which I'm not all too clear on). So neither ahbprot or writing to the nand alone caused the brick, but combined they had that effect.

So I think saying "AHB isn't a brick risk" is at best semantics and at worst short-sighted. If I misunderstood what you were saying then I apologize. I quoted @davebaol at the bottom of this message because I think his explanation is very clear. And I know it was a long time ago but to my knowledge nothing has changed on this matter. I would love nothing more than to be wrong on this last point so if I'm missing something please let me know.

AHB works just fine and safe when launched from an ahbprot enabled forwarder channel. But chances are if you're not experiencing even the odd crash from ahbprot then you're likely either not loading via the HBC, or you always have wifi, or the apps you're using have been updated to counter this bug and I'm not even sure how possible that is (I read about tueidj suggest that specifying a section of memory outside the range of what the HBC uses would solve this). I don't recall anyone ever having 100% success rate. In fact I even remember the IOS236 installer mod was tweaked to run super quickly without prompts to reduce the chances of a crash which is clearly a suboptimal solution especially for something like the priiloader installer. But this was a very real issue and an ahbprot priiloader installer caused bricks (see JoostinOnline's message below). I distinctly remember brainstorming with other knowledgeable gbatemper's way back in the day how the heck to softmod using ahbprot safely and the 236 installer was the best/most-safe option.

this bug resulted in several full bricks from Priiloader v0.5

And even davebaol says here his solution isn't 100% safe.

But the only chance for this patch to fail is if the IPC reply for the async call comes before patch completion. We're talking about few milliseconds, so from a probabilistic point of view it's almost impossible. Let's say it's 99.99% safe.

And I have to agree with Joostin here where he says he's not about to introduce a "maybe" factor into his guides. Even if it has a 99.99% success rate, ModMii is/was used so much that that's still 100 bricks out of every 1 million mods, and even just 1 in a million is too many for my high standards!

Two of my guides involve using IOS's and require patches to install. AHBPROT would be a great choice, but ever since the bug was discovered, I haven't trusted it. I've worked very hard to make sure my guides are safe for newbies, and I'm not going to add a "maybe" factor in there.

there is an issue in the Homebrew Channel that makes crash homebrew apps when you don't have your wii connected to the network and HBC is configured to load apps without reloading IOS, which is the only known way to get AHBPROT access rights.

... Snip...

There are 2 known workarounds to fix this issue but both have drawbacks.

The 1st way is to force HBC to reload IOS when it loads the app, which also kill any initiated network callback automatically and prevents the apps from crashing.
However this solution makes you loose AHBPROT access rights.

Another solution is to wait about 1 minute on the HBC hoping that the asynchronous call is terminated in the meanwhile.
However experience teaches that this workaround doesn't work always for every Wii out there.

Edit:
here's one of the many threads from the priiloader 0.5 installer ahbprot brick fiasco
https://gbatemp.net/threads/priiloader-messed-up-wii-please-help.251061/

 

[scooby74029]

http://www.hacksden.com/downloads.php?do=file&id=154

heres link to download for new priiloader from daco

 

[stomp_442]

http://www.hacksden.com/downloads.php?do=file&id=154

heres link to download for new priiloader from daco

newer version yet
http://wiibrew.org/wiki/Priiloader

 

[XFlak]

Thanks for the links. Reading through the change log it looks like after the brick fiasco he put out at least 3 further updates to the installer.... sooooo maybe ahbprot issues have all been resolved? This is what happens when u disappear for years at a time and have a bunch of kids, now I'm behind on important wii information, lol

 

[Cyan]

IOS249[56] (rev 65535, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 65535, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0

Thanks for posting the report, sorry I didn't see it sooner as you edited an old message of yours.

Replace your slot 249 with d2x v10 r2, base56.
r53 is bad, will have issues with hardware and games.

 

[blueagent004]

Thanks for posting the report, sorry I didn't see it sooner as you edited an old message of yours.

Replace your slot 249 with d2x v10 r2, base56.
r53 is bad, will have issues with hardware and games.

opps it was my fault, i probably should have put the report in a new reply instead of editing the old one.

thank you so very much for helping me! i truly appreciate your help! thanks again!