Hacking Lost sd card to my softmodded wii

[Andriko]

Hi, I lost my sd card that i used when softmodding my wii, and I have priiloader and bootmii installed on it, and I can't boot up my wii without it... what do I do? D:

 

[loco365]

Find the card or else get a new one. That's about all I can think of. Unless someone else has a radical solution.

 

[bowser]

Huh? Why won't your Wii boot without the SD card?

The bootmii files are not specific to each Wii AFAIK so you can just download them from somewhere and put them on an SD card. I think there should be a folder called 'bootmii' in the root of the SD card and a couple of files inside that (forgot what they are).

Did you try holding the reset button on the Wii after powering it on? That should get you into Priiloader.

 

[Andriko]

Huh? Why won't your Wii boot without the SD card?

The bootmii files are not specific to each Wii AFAIK so you can just download them from somewhere and put them on an SD card. I think there should be a folder called 'bootmii' in the root of the SD card and a couple of files inside that (forgot what they are).

Did you try holding the reset button on the Wii after powering it on? That should get you into Priiloader.

My wii can't boot into system menu or the homebrew channel, how can I make an sd card that mas my current version of bootmii and priiloader if i cant check the bootmii version(unless bootmii was installed on the sd card... idk) I mean aren't there logs on the wii's nand that say what was installed where?

 

[Sicklyboy]

Something isn't right. The SD card doesn't have anything mandatory for the Wii to boot. Bootmii isn't mandatory, nor is it specific to each wii, so you can go into ModMii and have it prepare the BootMii SD files for you.

Priiloader doesn't ever go on the SD card. Ever. The ONLY thing I could think is if you set priiloader to forward to something on the SD card instead of the SM, but I am pretty sure that if the SD is missing it boots to the next applicable option. (Edit: In fact, let me go test it.)

Mind going a bit more in-depth as to what is happening?

Edit 2 - wow, of course I would forget that the file installs to the Wii first, so it doesn't actually work that way.

Edit 3 - Turn the Wii off. Make sure the power LED is red. Press it (the power button), then immediately hold down reset. This will get you into priiloader. Tell me if you're able to do this.

 

[Andriko]

Something isn't right. The SD card doesn't have anything mandatory for the Wii to boot. Bootmii isn't mandatory, nor is it specific to each wii, so you can go into ModMii and have it prepare the BootMii SD files for you.

Priiloader doesn't ever go on the SD card. Ever. The ONLY thing I could think is if you set priiloader to forward to something on the SD card instead of the SM, but I am pretty sure that if the SD is missing it boots to the next applicable option. (Edit: In fact, let me go test it.)

Mind going a bit more in-depth as to what is happening?

Edit 2 - wow, of course I would forget that the file installs to the Wii first, so it doesn't actually work that way.

Edit 3 - Turn the Wii off. Make sure the power LED is red. Press it (the power button), then immediately hold down reset. This will get you into priiloader. Tell me if you're able to do this.

As i have explained, I am able to get into priiloader, but not into system menu or homebrew channel

 

[obcd]

It would be beter if you explained how the issue happened in the first place.
You are one step away from fully bricking your wii.
If you don't work very carefully from now on, you will likely take that step.

 

[AbdallahTerro]

Looks like a semi brick!
Please tell us what you did (installed a wad, theme, changed some settings...) , System Menu and Homebrew channel are not SD card dependent.
You should consider a re-hack AFTER providing us with more info .

 

[TiMeBoMb4u2]

Yep... I agree with a few of these posts.
Looks like you have a semi-brick. But if you're not careful, you could easily have a full brick!

Since you can still get to Priiloader, here's what I'd recommend...

1. Get a new SD Card
2. Use the ModMii Wizard to prepare your SD Card (it will set up the BootMii files for you)
3. Download sysCheck, and extract it to your new SD Card
4. Boot to Priiloader, and select BootMii IOS
5. In BootMii, perform a NAND Backup
6. After your NAND Backup (while still in BootMii), launch The Homebrew Channel
   1. If launching HBC fails, you should launch "bootmini.elf" from BootMii's SD navigation menu, and use it to reinstall the HBC.
7. Once the HBC has launched, run sysCheck
8. Shut down your Wii, and don't use it, until we all have a look at your sysCheck log
9. Post your sysCheck log here (be sure to use SPOILER tags when posting)

Good Luck!

 

[shortz1994]

from reading this post. an the quick descriptions from OP, this sounds like he doesn't understand too much of whats going on with the wii ( yeah kinda repeating everyone here.)
sounds like this is a "i paid/someone hacked it for me, an did something, an i don't know how to fix it." going on this info, if you can get to priiloader, go down to settings an see if auto boot is on for an app, like a usbloader, an is set to return to " usbloader" this would give a black screen, if this is the case, just switch it back to boot the menu. a long with the return to line. cause the sd card is not in to read the file. also in the menu of priiloader he can still run to system menu, without the sd card. wondering if he/she has tried this? if so. the the OP should follow the above post (timebomb 4u2)..
@ OP as it has been explained the sd card has nothing to do with booting the wii (unless you have priiloader set to point to an app on the sd card). sd card just holdes the files for your app, an thats all. find your sd card, or any card.
i don't under stand how anyone can think it's a semi brick or a brick with just the short line the OP used to describe his/her problem.. need more info then what he/she wrote.

 

[AbdallahTerro]

Correct me if I'm wrong, but to use the priiloader autoboot feature the file is installed from SD to wii nand and thus works without SD

 

[DeadlyFoez]

Correct me if I'm wrong, but to use the priiloader autoboot feature the file is installed from SD to wii nand and thus works without SD

You are correct.

 

[XFlak]

Correct me if I'm wrong, but to use the priiloader autoboot feature the file is installed from SD to wii nand and thus works without SD

You are correct.

Technically correct, but if a forwarder channel is installed as priiloader's autoboot file, the forwarder dol is saved to the nand and booted. In turn it forwards to an app on the sd card or fat32 hdd. Most forwarders will return to the system menu if the forwarder's path does not exist, but some older forwarders will just blackscreen.

The first thing the OP should try is loading the system menu directly via priiloader. He should also verify that he doesn't have any bogus system menu hacks enabled (ie. blackscreen at startup).

Also, TiMeBoMb4u2's suggestion will not work. Bootmii's SD navigation menu will only launch "mini" apps, so therefore it will fail if attemping to launch syscheck directly. Instead, the OP should try launching the homebrew channel via bootmii (launching the HBC from older versions of priiloader may not work due to the title ID change of the latest HBC, but bootmii is usually updated along with the HBC so it should be able to launch whatever version of the HBC is currently installed, assuming it is in fact installed). If that fails, then the OP should launch bootmini.elf from Bootmii's SD navigation menu, and use it to reinstall the HBC. Once the HBC is installed, the OP will be able to launch apps like syscheck in order to get to the bottom of his problem.

A couple of noteworthy things... since the OP is able to access priiloader, it means that the system menu and system menu IOS are intact. It's possible, however unlikely, that the system menu is corrupted and needs to be reinstalled... but the most likely cause of this problem is bogus priiloader system menu hacks enabled or autoboot settings configured to launch a forwarder that won't return to the Wii Menu if the forwarder path is not found. The OP should first focus on making a nand backup, then getting access to the HBC\system-menu, then a straightforward re-softmod using ModMii or w/e should cover everything else.

 

[AbdallahTerro]

As i have explained, I am able to get into priiloader, but not into system menu or homebrew channel

@[member='XFlak']
So why he can't even get into the HBC also?
the only thing that explains the OP description will be a failed hardware (BT module) to be exact.

 

[obcd]

Maybe he doesn't know the procedure to enter priiloader setup and use it to boot into the hbc.

There are a lot of speculations but not much infomation from the topic originator.

So, we might as well wait for more information from him before we give him some hints to proceed.

With a failed BT module, the system won't boot into priiloader either. I suspect more something like a system menu upgrade that got interrupted halfaway.
But again, without more info, this are just speculations, and they could be totally wrong.

 

[Luigi2012SM64DS]

i bet you had recovery mode hacks on and you used bootmii to get into the homebrew to boot somehing from there

 

[XFlak]

As i have explained, I am able to get into priiloader, but not into system menu or homebrew channel

@[member='XFlak']
So why he can't even get into the HBC also?
the only thing that explains the OP description will be a failed hardware (BT module) to be exact.

launching the HBC from older versions of priiloader may not work due to the title ID change of the latest HBC, but bootmii is usually updated along with the HBC so it should be able to launch whatever version of the HBC is currently installed, assuming it is in fact installed

It's possible that the HBC does not exist on this Wii (ie. older version removed due to system menu update, manual deletion, wii memory format, etc.). If this is the case then the HBC would obviously need to be reinstalled before being able to be accessed.

Also, if the OP has priiloader v0.4 installed, it will not natively be able to launch HBC v1.0.7 or higher if installed (i.e. it can only load HBC's with title ID of "HAXX" or "JODI"). However, the HBC should appear on the title launcher menu, and can be booted from there. But if the OP has an older version of priiloader installed that does not have the title launcher, a HBC v1.0.7+ forwarder dol can be installed as priiloader's file and can be launched that way. However, all versions of priiloader can launch bootmii as IOS, since it's always been installed to slot 254 and nothing has changed in that regard. And once bootmii is loaded, it should be able to launch the HBC if it's installed or the hackmii installer (bootmini.elf) if it's not. And if neither bootmii or the HBC is installed, then priiloader can be used to load the hackmii installer's boot.elf (either by installing it or a forwarder as priiloader's file).

Until we hear more from the OP, we cannot diagnose this problem further... but one this is for certain, hardware failure is NOT the only explanation


@OP,
Check your priiloader system menu hacks and report what you have enabled. Also tell us what version of priiloader you have installed.

Also, download the bootmii sd files from here:
http://static.hackmii.com/bootmii_sd_files.zip
extract the bootmii folder to your new sd card (i.e. SD:\bootmii\) and try loading bootmii via priiloader again. Then let us know whether this loads the bootmii menu or not.

 

[TiMeBoMb4u2]

...Also, TiMeBoMb4u2's suggestion will not work. Bootmii's SD navigation menu will only launch "mini" apps, so therefore it will fail if attemping to launch syscheck directly. Instead, the OP should try launching the homebrew channel via bootmii (launching the HBC from older versions of priiloader may not work due to the title ID change of the latest HBC, but bootmii is usually updated along with the HBC so it should be able to launch whatever version of the HBC is currently installed, assuming it is in fact installed). If that fails, then the OP should launch bootmini.elf from Bootmii's SD navigation menu, and use it to reinstall the HBC. Once the HBC is installed, the OP will be able to launch apps like syscheck in order to get to the bottom of his problem.

Very true; thanks for reminding me. I totally forgot that it was strictly "mini" apps. I'll edit my post.

 

[Andriko]

I tried autobooting into system menu, but an error came up in priiloader saying: Error autobooting systemmenu! ES_DiVerfiy failed! no iOS with it patched?
I tried opening HBC and this error came up: Error autobooting HBC, maybe title not installed?
I tried opening bootmii ios, and this error came up: Error booting Bootmii iOS

I see iOS v50 systemmenu v0 in the bottom left of priiloader =S

I have priiloader v0.3(r43), I have HBC installed, and BootMii both on what I remember as the "better option" in the bootmii installation

Currently I am downloading the bootmii sd files and putting it on an sd card and gonna try to boot into system menu, if that doesn't work hbc, and then whatever you guys suggested

 

[XFlak]

Try accessing bootmii by following the instructions from my previous post (hopefully u have an sd card u can use). Once you are able to access bootmii, you should make a nand backup just in case, and also see if you can access the HBC via bootmii.

FYI, some funky shit is installed on your Wii. System menu v0 indicates that u may have a system menu installed with its version # changed. Anyways, so far it sounds like this can be fixed by using the homebrew channel, so don't freak out and try something silly.