jaidenShepard / dop-mii

Automatically exported from code.google.com/p/dop-mii
GNU General Public License v3.0
0 stars 0 forks source link

"(-106) Invalid TMD when using ES_OpenContent or access denied" Error message when trying to use "Install IOS36" option... #45

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What IOS did you use?

I'm not sure I understand this question. If what's meant is "What IOS was 
selected for use (IOS: ???) on the main menu?", then that would be whichever 
one the system found on my first time running DOP-Mii; I don't recall what the 
number was. The number that's listed now by default since my first attempt is 
"IOS: 65536". However, if the question means "which IOS was/is installed on my 
system prior to installing DOP-Mii, the answer would be "IOS37" (this is 
according to my NAND backup provided by Boot-Mii).

What is the first 4 digits of your Wii's Serial Number?

LU53

What steps will reproduce the problem?
1. As of right now, the first is to load Dop-Mii from the HBC.
2. After the welcome screen, select "Install IOS36 (v3351) w/FakeSign".
3. After confirming the warning, DOP-Mii automatically starts to check IOS 
versions to find one to downgrade with. However, when it found IOS36, it 
immediately skipped it and auto-setup IOS41.

What is the expected output? What do you see instead?

According to the guide I've been following 
(http://sites.google.com/site/completesg/hacking-guide/trucha) I was supposed 
to have been able to start choosing the location of my IOS. However, what I got 
instead was this error message:

Checking IOS36 Version...Not Usable.
Checking IOS41 Version...Version Usable. Starting Downgrade.
Current IOS is not 41. Loading IOS41

>>ERROR!  Failed to Stored TMD for IOS36: (-106) Invalid TMD when using 
ES_OpenContent or access denied.

Press any key to return to the menu.

Please provide any additional information below.

It's important to note that I was closely following the instructions provided 
at the "CompleteSoftmodGuide" webpage 
(http://sites.google.com/site/completesg/hacking-guide/trucha). as you can see, 
if you've looked at the guide I've cited, I don't even get a chance to get to 
step 2-A. Up to this point in the guide, the only other things that were done 
successfully to my Wii were to follow all of the steps on the guide page that 
preceded the one I just mentioned 
(http://sites.google.com/site/completesg/hacking-guide/the-basics). The last 
official (with the normal Wii update feature) update this Wii ever received was 
the 3.3u update sometime back in October 2008. 

   Another note worth mentioning is that I no longer have the option to try and reattempt this install offline with my SD card (downloaded WAD files via NUS Downloader), as DOP-Mii seems to immediately use the files it downloaded from my first attempt to install, which were via NUS (Wi-Fi). To try and remedy this, I went ahead and deleted/reinstalled the DOP-Mii application on my SD card (my thought was that it was keeping track of the install in the apps or config folder there), and then restarted the Wii, but the results/error message appears at the same spot, prompting me to press any key to return to the main menu. The only thing I haven't tried as of this report is to do a full restore of my Key and NAND files, as I'm not sure if that would at least let me try to do this install again offline without the error. The last thing I can mention here is that according to the Homebrew Channel, it shows I'm still using IOS37 v8.22, yet when I load up DOP-Mii, it reports that I'm using IOS41 (it didn't show this IOS during my first attempt to "Install IOS36..."). I've also attached a "SysCheck" report from DOP-Mii in the hopes it may help someone identify my problem (see attached file).

Original issue reported on code.google.com by fig_n...@hotmail.com on 25 Aug 2010 at 8:10

Attachments:

GoogleCodeExporter commented 8 years ago
Should be fixed in v14.

Original comment by castleva...@yahoo.com on 21 Nov 2010 at 4:25