Not too long ago I ran into a problem with my console that I did not quite understand. The problem and my intrigue for understanding and circumventing it lead me to this site among other resources.
Now, nearly six months down the line I am met with yet another issue of which I don't recognize the root cause, but this time I am confident that the bane of my problems stems from a modification's affinity to be compromised.
All due respect to the efforts made to learn about Nintendo current model and the hard work that it took to development interfaces and applications to meet the demand for the console. I am nevertheless frustrated about the sheer amount of information that I have to sift through to gain some sort of familiarity with the hacking scene that consistently fails to reciprocate the same level of insight which lead the community in their discoveries. At this point I feel like its necessary that I research the hacking scene from square one and follow up with my programming degree to finally comprehend where competent hackers are coming from.
Now before the flag of "nagging incompetent user" comes to thought, I would like to address the vast number of threads that have gone up on this site all posing permutations of homebrew shortcommings.
In truth, the matter that even compelled me into writing this was my disappointment over an administrators response: Google it. The most amusing part in this scenario is that time and time again I come across different tutorials all urging people to ask questions.
So what should I ask and how do ask it in a manner that appropriately conveys this confusion? All with the goal in mind to understand and, as a result, avoid whatever issue brought me to become confused in the first place.
What does it mean for a console to hang at the Health and Safety screen and for that hanging to override the solutions prepared on this website?
What work can be done to salvage my console.
Retracing my steps
The date of my recent brick, my intentions were to demonstrate Project M to some fellows.
I ran into a snag with the codeset not activating, ergo the change menu orientation (found in P:M) was present but the actual stages and physics reverted to the original brawl settings.
I figured it may be necessary to update my Gecko install so I registered a Gecko Channel so as to run the Modification through the system menu. Gecko was successful, Project M was not.
Low and behold, the Project M codeset will not activate on a SD-HC or any card greater than 2GB.
I had it in mind that the codeset would indeed activate under a HC card if I ran the codeset under a custom IOS. IOS60 --> CIOS249. Why not, right? Wrong.
Now comes the folly- I try to enter Multi-Mod Manager throught the HB Channel forgetting that I had removed the SD card (with all the applications on file) in order to replicate the codeset on a non HC card.
The play by play of what occurred:
The HBC loads, I select MMM, the console searches for that particular application, it does not find it, thus a System Menu failure [Brick]
My memory is fuzzy as to what happened onscreen where the immediate brick occured. After restarting the console, the startup does not allow me to enter the System Menu (No Press A comes onscreen). No solution saved to my SD card will activate.
I'll need trace back further as to why the Boot2 option is absent. Bootmii was my means to restoring my NAND when I first could not access the Menu (ie first brick).