Hacking Can't load up Homebrew Channel anymore after stupid mistake

[Deleted User]

None of those should be there.

223 is Hermes Payload, not compatible at all with vWii. In fact, it hasn't been updated in years.

BC v6 and DIOS MIOS (why? vWii isn't backwards compatible with GC - much less has the hardware)

What did you install these with? They need to be deleted before anything. Then try again.

 

[MartinDocNewland]

Its been a bust day for me today but just managed to have a clean up, what do you people think?

Spoiler

SysCheck v2.2.0 HD Edition by Double_A and R2-D2199, JoostinOnline, Nano
...runs on IOS58 (rev 6432).

Region: PAL
System Menu 4.3E (v546)

Drive date: 07.12.2012
Homebrew Channel is not installed

Hollywood v0x21
Console ID: 615108632
Console Type: vWii
Shop Channel Country: United Kingdom (110)
Boot2 v0
Found 46 titles.
Found 35 IOS on this console. 0 of them are stub.

IOS9 (rev 1290): No Patches
IOS12 (rev 782): No Patches
IOS13 (rev 1288): No Patches
IOS14 (rev 1288): No Patches
IOS15 (rev 1288): No Patches
IOS17 (rev 1288): No Patches
IOS21 (rev 1295): No Patches
IOS22 (rev 1550): No Patches
IOS28 (rev 2063): No Patches
IOS31 (rev 3864): No Patches
IOS33 (rev 3864): No Patches
IOS34 (rev 3864): No Patches
IOS35 (rev 3864): No Patches
IOS36 (rev 3864): No Patches
IOS37 (rev 5919): No Patches
IOS38 (rev 4380): No Patches
IOS41 (rev 3863): No Patches
IOS43 (rev 3863): No Patches
IOS45 (rev 3863): No Patches
IOS46 (rev 3863): No Patches
IOS48 (rev 4380): No Patches
IOS53 (rev 5919): No Patches
IOS55 (rev 5919): No Patches
IOS56 (rev 5918): No Patches
IOS57 (rev 6175): No Patches
IOS58 (rev 6432): USB 2.0
IOS59 (rev 9249): No Patches
IOS62 (rev 6430): No Patches
IOS80 (rev 7200): No Patches
IOS236 (rev 65535): Trucha Bug, ES Identify, NAND Access
IOS249[56] (rev 21010, Info: d2x-v10beta52-vWii): NAND Access, USB 2.0
IOS250[57] (rev 21010, Info: d2x-v10beta52-vWii): NAND Access, USB 2.0
IOS251[58] (rev 21010, Info: d2x-v10beta52-vWii): NAND Access, USB 2.0
IOS512 (rev 7): NAND Access, USB 2.0
IOS513 (rev 1): NAND Access, USB 2.0
Report generated on 07/17/2014.

EDIT

So I got rid of the 3 IOS's that should not be there but i'm STILL getting the freeze just before it says press 1 on the scam screen on the HBC loader! Should I get rid off IOS512 & IOS513?

EDIT 2

Looks like I need IOS512 & IOS513 so will not mess with them. But still puzzeled why I keep getting the freeze

 

[Deleted User]

Remove the IOS236 and try again.

Everything else looks okay at least revision wise.

Also, check your SD card for an installer.log file. There may be some pertinent info.

 

[MartinDocNewland]

Well this is the installer log I have from when I last tried to install HBC

Spoiler

HackMii v1.2 installer starting up
PVR = 00087200
running under IOS 59 rev 0x2421
46 titles are installed
Found IOS 58: revision: 0x1920*
Found IOS 0: revision: 0x0*
Found IOS 236: revision: 0xffff*
Found IOS 251: revision: 0x5212*
Found IOS 250: revision: 0x5212*
Found IOS 249: revision: 0x5212*
Found IOS 62: revision: 0x191e.
Found IOS 59: revision: 0x2421.
Found IOS 57: revision: 0x181f.
Found IOS 56: revision: 0x171e.
Found IOS 55: revision: 0x171f.
Found IOS 53: revision: 0x171f.
Found IOS 48: revision: 0x111c.
Found IOS 46: revision: 0xf17.
Found IOS 45: revision: 0xf17.
Found IOS 43: revision: 0xf17.
Found IOS 41: revision: 0xf17.
Found IOS 38: revision: 0x111c.
Found IOS 37: revision: 0x171f.
Found IOS 36: revision: 0xf18*
Found IOS 35: revision: 0xf18.
Found IOS 34: revision: 0xf18.
Found IOS 33: revision: 0xf18.
Found IOS 31: revision: 0xf18.
Found IOS 28: revision: 0x80f.
Found IOS 22: revision: 0x60e.
Found IOS 21: revision: 0x50f.
Found IOS 17: revision: 0x508.
Found IOS 15: revision: 0x508.
Found IOS 14: revision: 0x508.
Found IOS 13: revision: 0x508.
Found IOS 12: revision: 0x30e.
Found IOS 9: revision: 0x50a.
Found IOS 2: revision: 0x222.
Found IOS 80: revision: 0x1c20.
launching IOS 38 for the installer...

IOS launched...

IOS versions: Installer: 38, HBC: 0
starting preparations

Going to try what you said

 

[Cyan]

I suggest you always use a specific SD card for WiiU, and a different one for Wii. Never mixed them as when you install IOS or CIOS or any system file, it creates temporary files to prevent re-downloading them every time.
If you use the wrong SD card with the Temp files from the other console it will be used to install instead of downloading proper files, it might be what happened to you if you didn't installed these files yourself.


The log you posted is an old one (where it didn't even find IOS58).
Post the new log now that you reinstalled 58.

 

[Bug_Checker_]

Its been a bust day for me today but just managed to have a clean up, what do you people think?

Spoiler

SysCheck v2.2.0 HD Edition by Double_A and R2-D2199, JoostinOnline, Nano
...runs on IOS58 (rev 6432).

Region: PAL
System Menu 4.3E (v546)

Drive date: 07.12.2012
Homebrew Channel is not installed

Hollywood v0x21
Console ID: 615108632
Console Type: vWii
Shop Channel Country: United Kingdom (110)
Boot2 v0
Found 46 titles.
Found 35 IOS on this console. 0 of them are stub.

IOS9 (rev 1290): No Patches
IOS12 (rev 782): No Patches
IOS13 (rev 1288): No Patches
IOS14 (rev 1288): No Patches
IOS15 (rev 1288): No Patches
IOS17 (rev 1288): No Patches
IOS21 (rev 1295): No Patches
IOS22 (rev 1550): No Patches
IOS28 (rev 2063): No Patches
IOS31 (rev 3864): No Patches
IOS33 (rev 3864): No Patches
IOS34 (rev 3864): No Patches
IOS35 (rev 3864): No Patches
IOS36 (rev 3864): No Patches
IOS37 (rev 5919): No Patches
IOS38 (rev 4380): No Patches
IOS41 (rev 3863): No Patches
IOS43 (rev 3863): No Patches
IOS45 (rev 3863): No Patches
IOS46 (rev 3863): No Patches
IOS48 (rev 4380): No Patches
IOS53 (rev 5919): No Patches
IOS55 (rev 5919): No Patches
IOS56 (rev 5918): No Patches
IOS57 (rev 6175): No Patches
IOS58 (rev 6432): USB 2.0
IOS59 (rev 9249): No Patches
IOS62 (rev 6430): No Patches
IOS80 (rev 7200): No Patches
IOS236 (rev 65535): Trucha Bug, ES Identify, NAND Access
IOS249[56] (rev 21010, Info: d2x-v10beta52-vWii): NAND Access, USB 2.0
IOS250[57] (rev 21010, Info: d2x-v10beta52-vWii): NAND Access, USB 2.0
IOS251[58] (rev 21010, Info: d2x-v10beta52-vWii): NAND Access, USB 2.0
IOS512 (rev 7): NAND Access, USB 2.0
IOS513 (rev 1): NAND Access, USB 2.0
Report generated on 07/17/2014.

EDIT

So I got rid of the 3 IOS's that should not be there but i'm STILL getting the freeze just before it says press 1 on the scam screen on the HBC loader! Should I get rid off IOS512 & IOS513?

EDIT 2

Looks like I need IOS512 & IOS513 so will not mess with them. But still puzzeled why I keep getting the freeze

Since it's a busy day for you, Do NOT work on your wiiu until you can devote quiet ,thoughtful,non-hectic time to debugging. Debugging requires you to be focused and the #1 priority must be on the wiiu.
You are just in a semi-crappy state,now. You don't want to be in a FULLY-crappy state. There are some people who are stuck being vwii-less(perhaps for the life of the console). Do not be one of thoses people.

Did you do as I suggested and try to make a backup copy of your current vwii nand?
If not try this AFTER you have saved multiple copies of your original nand somewhere safe.
1 copy of your original nand should never be touched except to make a 2nd(or multiple) working copy(ies) that you can freely experiment with.
Now, if you have a current nand(the flawed version),make a "working" copy of that.
Then, try and exact ALL of the ios' from both "working" nands (the copies of the original and current nand) into separate directories. Compare all the ios from each directory.

Spoiler

If you are on windows, you can use the standard fc (file compare) command from a command prompt. You can use wildcards to speed the process up(example "fc /b /v c:\originalnand\*.* c:\currentnand\*.*" without quotes) (the "/b" and "/v" options are binary and verify).You can even redirect output of file compare(fc) to a file(example "fc /b /v c:\originalnand\*.* c:\currentnand\*.* > pick_a_good_filename.txt" without quotes).
I like a program called exactfile(maybe others will have better suggestions) from:
http://www.exactfile.com/downloads/
http://www.exactfile.com/files/ExactFile-Setup.exe
If you used exactfile choose "Create Digest" and make sure "Include subfolders" and "Output to file:" are both checked. Then select by "Method and Format" either "MD5" or "sha1"(or "sha1sum").

Report back findings. Good Luck.

btw, you were correct NEVER mess with ios512 or ios513

 

[MartinDocNewland]

Thanks people for the help so far, its been handy lol Don't worry bug checker I have a nand dump I have not touched saved and hidden safe lol Using computers for 29 years means you do learn from your lessons lol Cyan i'm only using the Wii U and the Wii U alone so don't worry about temp files, I been formatting the SD cards im using every so often so mistakes don't happen so again don't worry lol Right going to try to install HBC again on a clean card now so wish me luck lol

EDIT

I have 2 clean copies of my nand that I made straight after I installed the HBC for the first time ans a copy of the non working one so have been comparing them already

EDIT 2

I been looking at the installer log again for HBC (It was done at 17:07 today and your right, its not seeing IOS58. Going to do a Syscheck again so will post that when I get it

 

[Deleted User]

Yes, try it on a fresh card. That log doesn't look right as it's attempting to use IOS59 which it won't be able to patch. Those asterisks also mark non-standard IOS. But something about that numbering is all off. According to that one 36 and 58 are off.

It did find 58 at the top, but it's a modified one.

Just format the SD and put only what you need to launch HBC installer and repost the log file. Make sure you're using the 58 from YOUR nand dump, not random ones on the internet as it may be a diff region.

 

[MartinDocNewland]

Yes, try it on a fresh card. That log doesn't look right as it's attempting to use IOS59 which it won't be able to patch. Those asterisks also mark non-standard IOS. But something about that numbering is all off. According to that one 36 and 58 are off.

It did find 58 at the top, but it's a modified one.

Just format the SD and put only what you need to launch HBC installer and repost the log file. Make sure you're using the 58 from YOUR nand dump, not random ones on the internet as it may be a diff region.

The IOS36 & IOS58 was from a nand dump I made so I dont know whats going on there lol Going to redecrypt a copy of my nand dump and try them

 

[MartinDocNewland]

Having trouble installing the IOS's now. What IOS should I choose in YAWMM? 236, 249 & 250 are not working, keep getting error (ret = -1017)

 

[Deleted User]

Were you able to get a SysCheck? Just want to be sure before loading.

No luck on 251 either?

-1017 usually means a corrupted file. Can't remember the other WAD manager you can use.

 

[MartinDocNewland]

Were you able to get a SysCheck? Just want to be sure before loading.

No luck on 251 either?

-1017 usually means a corrupted file. Can't remember the other WAD manager you can use.

Well I used YAWWMM without using a base and IOS36 installed nice but then IOS58 came up with error -1022 and I know this error comes up when the IOS is signed wrong so I signed it with wwpacker and installed it but STILL getting an error saying HBC is running off IOS59 and my IOS58 is a mod one even tho i have taken IOS58 from my own nand backup! Have a look

Spoiler

HackMii v1.2 installer starting up
PVR = 00087200
running under IOS 59 rev 0x2421
46 titles are installed
Found IOS 58: revision: 0x1920*
Found IOS 0: revision: 0x0*
Found IOS 236: revision: 0xffff*
Found IOS 251: revision: 0x5212*
Found IOS 250: revision: 0x5212*
Found IOS 249: revision: 0x5212*
Found IOS 62: revision: 0x191e.
Found IOS 59: revision: 0x2421.
Found IOS 57: revision: 0x181f.
Found IOS 56: revision: 0x171e.
Found IOS 55: revision: 0x171f.
Found IOS 53: revision: 0x171f.
Found IOS 48: revision: 0x111c.
Found IOS 46: revision: 0xf17.
Found IOS 45: revision: 0xf17.
Found IOS 43: revision: 0xf17.
Found IOS 41: revision: 0xf17.
Found IOS 38: revision: 0x111c.
Found IOS 37: revision: 0x171f.
Found IOS 36: revision: 0xf18*
Found IOS 35: revision: 0xf18.
Found IOS 34: revision: 0xf18.
Found IOS 33: revision: 0xf18.
Found IOS 31: revision: 0xf18.
Found IOS 28: revision: 0x80f.
Found IOS 22: revision: 0x60e.
Found IOS 21: revision: 0x50f.
Found IOS 17: revision: 0x508.
Found IOS 15: revision: 0x508.
Found IOS 14: revision: 0x508.
Found IOS 13: revision: 0x508.
Found IOS 12: revision: 0x30e.
Found IOS 9: revision: 0x50a.
Found IOS 2: revision: 0x222.
Found IOS 80: revision: 0x1c20.
launching IOS 38 for the installer...

IOS launched...

IOS versions: Installer: 38, HBC: 0
starting preparations

I can't figure this one out as I did a dump as soon as I had HBC installed

 

[Bug_Checker_]

Having trouble installing the IOS's now. What IOS should I choose in YAWMM? 236, 249 & 250 are not working, keep getting error (ret = -1017)

THE reason why you need to compare ALL the ios's/titles from your original "virgin" vwii nand backup and the ios's/titles from your current vwii nand is to eliminate any possible IOS errors as your problem.
The md5 or sha1 of those IOS's/Titles will allow others from your region to check it with their versions. You want to find the problem before you start throwing solutions at a wall. Look under 00000007: Virtual Wii titles on
http://wiiubrew.org/wiki/Title_database

Once you find out what the problem was then we can come up with a solution that doesn't involve bricking your vwii. The vwii needs to be back as close as possible to its virgin state. Then, if problems still persist, it maybe related to a sdcard /homebrew software problem(much easier to fix).

 

[Deleted User]

how are you packing the WAD? Through ShowMiiWads? It's still showing that IOS58 and 36 are modded. The link above from BugChecker should let you compare yours with known versions. IT sounds like 58 and 36 may be fakesigned.

 

[MartinDocNewland]

how are you packing the WAD? Through ShowMiiWads? It's still showing that IOS58 and 36 are modded. The link above from BugChecker should let you compare yours with known versions. IT sounds like 58 and 36 may be fakesigned.

I know what I did wrong and again its a stupid mistake on my part. I was resigning them with a common key and not the key from my nand backup. Now I installed the IOS58 with the common key signed I can't get YAWMM, MMM or Wad Manager to load up lol

EDIT

When signing IOS58 the output file is named IOS58-v6432 [TruchaSigned], is this ok?

EDIT 2 Does anyone know a wad installer thats a .elf file so I can run it straight from the exploit?

 

[Bug_Checker_]

Well I used YAWWMM without using a base and IOS36 installed nice but then IOS58 came up with error -1022 and I know this error comes up when the IOS is signed wrong so I signed it with wwpacker and installed it but STILL getting an error saying HBC is running off IOS59 and my IOS58 is a mod one even tho i have taken IOS58 from my own nand backup! Have a look

Spoiler

HackMii v1.2 installer starting up
PVR = 00087200
running under IOS 59 rev 0x2421
46 titles are installed
Found IOS 58: revision: 0x1920*
Found IOS 0: revision: 0x0*
Found IOS 236: revision: 0xffff*
Found IOS 251: revision: 0x5212*
Found IOS 250: revision: 0x5212*
Found IOS 249: revision: 0x5212*
Found IOS 62: revision: 0x191e.
Found IOS 59: revision: 0x2421.
Found IOS 57: revision: 0x181f.
Found IOS 56: revision: 0x171e.
Found IOS 55: revision: 0x171f.
Found IOS 53: revision: 0x171f.
Found IOS 48: revision: 0x111c.
Found IOS 46: revision: 0xf17.
Found IOS 45: revision: 0xf17.
Found IOS 43: revision: 0xf17.
Found IOS 41: revision: 0xf17.
Found IOS 38: revision: 0x111c.
Found IOS 37: revision: 0x171f.
Found IOS 36: revision: 0xf18*
Found IOS 35: revision: 0xf18.
Found IOS 34: revision: 0xf18.
Found IOS 33: revision: 0xf18.
Found IOS 31: revision: 0xf18.
Found IOS 28: revision: 0x80f.
Found IOS 22: revision: 0x60e.
Found IOS 21: revision: 0x50f.
Found IOS 17: revision: 0x508.
Found IOS 15: revision: 0x508.
Found IOS 14: revision: 0x508.
Found IOS 13: revision: 0x508.
Found IOS 12: revision: 0x30e.
Found IOS 9: revision: 0x50a.
Found IOS 2: revision: 0x222.
Found IOS 80: revision: 0x1c20.
launching IOS 38 for the installer...

IOS launched...

IOS versions: Installer: 38, HBC: 0
starting preparations

I can't figure this one out as I did a dump as soon as I had HBC installed

Is wwPacker considered current/safe for use? I couldn't find any information to suggest otherwise, but I hit a slight snag when using it in conjunction with the Wii U's Wii Mode (vWii). With a NAND backup of my actual Wii and ShowMiiNand/ShowMiiWads, I created WADs of the Amazon, Netflix, Everybody Votes, and Check Mii Out channels. I unpacked each with wwunPacker, then ran each through the FakeSign bat; I copied my Common-Key from the ShowMiiWads folder for the packer. When prompted, I chose the fakesign option for title and ticket and re-packed the WADs. They installed fine, but after rebooting to the System Menu it froze (hard freeze, no music). Luckily it would always freeze about 2 seconds after the Safety Message, so I clicked to enter the HBC before those 2 seconds occurred. From there I used Anytitledeleter MOD and removed the four channels I added, fixing the freeze. Now I'm afraid to try any further, but my natural inclination tells me to try running the WADs through the Justsign bat instead. Just curious if anyone had any feedback to that regard.

Why are you signing IOS's at all until you get this figured out? Is wwpacker even vwii compatible ?

 

[MartinDocNewland]

Why are you signing IOS's at all until you get this figured out? Is wwpacker even vwii compatible ?

I have checked again with the link you gave me and my title id for IOS36 is: 00000001\00000024 but in that list the title id is: 00000007-00000024 this is what I don't get!

How can that be if I have taken the IOS's I need from my clean Nand backup?

 

[Bug_Checker_]

I have checked again with the link you gave me and my title id for IOS36 is: 00000001\00000024 but in that list the title id is: 00000007-00000024 is is what I don't get!

How can that be if I have taken the IOS's I need from my clean Nand backup?

Do NOT worry about title names only md5/sha1 values.

Btw, just to be clear (for others) vwii ios's and wii ios's are NOT compatible. vwii ios's have extra layer of encryption. Do NOT mess with official Nintendo vwii IOS's (anything under 200) [unless otherwise explicitly instructed to do so].

**************************** DETAILED DUMPS ****************************


====== Titles Added ======

Spoiler

vWii System Menu
Title ID: 00000007-00000002
Version: 0x202
Size: 23657456
TMD:
Versions: 0, CA CRL 0, Signer CRL 0, System 1-80
Title ID: 00000001-00000002 ('\x00\x00\x00\x01'-'\x00\x00\x00\x02')
Title Type: 1
Group ID: '\x00\x01'
Access Rights: 0x00000000
Title Version: 0x202
Boot Index: 8
Contents:
ID Index Type Size Hash
0000000D 0 0x1 0x40 23 d9 87 ac 69 93 3a 4c 6c cc b0 d6 d8 94 90 ba eb 47 db 1b
0000000E 1 0x1 0x732f07 6f 90 0a 01 7f a8 5c b4 3e 73 a1 a6 6c c9 f2 b2 f6 01 46 dd
00000002 2 0x8001 0x45940f f5 dd 17 b3 20 0d d4 d6 be 2b 25 b5 77 c9 9e 5f 94 1b 73 24
00000003 3 0x8001 0x28b9f4 32 b3 39 cb bb 50 7d 50 27 79 25 9a 78 66 99 5d 03 0b 1d 88
00000004 4 0x8001 0xa7984 5f 1b b7 b0 27 94 b1 4e 88 b7 22 69 a3 37 6d 23 05 1d ad 1d
00000005 5 0x8001 0x37adfc 4f ad 97 fd 4a 28 8c 47 e0 58 7f 3b bd 29 23 79 f8 70 9e b9
0000000F 6 0x8001 0x93f40 76 ab fb ea cb 2c 4c a4 eb 3f 03 64 13 c7 e0 01 fd ab 7b 26
00000010 7 0x8001 0x112c0 2f 28 d4 b6 da eb eb 15 80 14 77 c6 be bc 5f 37 c0 90 9e ae
00000011 8 0x1 0x3b0500 ec b7 89 5b 0e 02 8c 95 b8 db 43 7e 47 0f f7 31 67 ed b7 ea
TMD signed by Root-CA00000001-CP00000004 using RSA-2048: 4d 3d 91 9b 61 d3 d9 c8 01 71 13 7c 8c 61 77 2a 5d 17 75 d9 [OK]
TMD Certificates:
- CP00000004 (RSA-2048)
Certificate signed by Root-CA00000001 using RSA-2048: 8d 4f ff f1 ba f5 f0 07 b8 b4 bd f9 03 b5 00 ad e5 e8 20 fc [OK]
- CA00000001 (RSA-2048)
Certificate signed by Root using RSA-4096: 6f 47 c8 5c b1 aa ee 83 b1 1d 73 3f 19 fe 6c 7e 8e 2f e4 50 [OK]
ETicket:
Title ID: '\x00\x00\x00\x01\x00\x00\x00\x02'
Title key IV: 00 00 00 01 00 00 00 02 00 00 00 00 00 00 00 00
Title key (encrypted): 15 6b 68 f7 71 71 be 84 77 b0 82 04 94 08 ec ef
Common key index: 2
ETicket signed by Root-CA00000001-XS00000003 using RSA-2048: 04 9c e5 d1 de 18 f6 3b 2f 26 5a ae 9a e5 46 6a e1 c3 85 6b [OK]
ETicket Certificates:
- XS00000003 (RSA-2048)
Certificate signed by Root-CA00000001 using RSA-2048: d7 0a a0 54 90 af 79 3e 49 10 af 47 9a 76 0f d2 75 f5 ad 12 [OK]
- CA00000001 (RSA-2048)
Certificate signed by Root using RSA-4096: 6f 47 c8 5c b1 aa ee 83 b1 1d 73 3f 19 fe 6c 7e 8e 2f e4 50 [OK]

vWii IOS36
Title ID: 00000007-00000024
Version: 0xf18
Size: 1866320
TMD:
Versions: 0, CA CRL 0, Signer CRL 0, System 0-0
Title ID: 00000001-00000024 ('\x00\x00\x00\x01'-'\x00\x00\x00$')
Title Type: 1
Group ID: '\x00\x01'
Access Rights: 0x00000000
Title Version: 0xf18
Boot Index: 14
Contents:
ID Index Type Size Hash
00000000 0 0x1 0x40 22 35 0d fe e0 e9 9d e4 4d b6 38 6a c3 57 cb 96 2e f3 ed 72
00000001 1 0x8001 0x7ff8 e0 4f 3a be 93 ca 9b 9a 25 18 c2 dd c3 d2 73 e4 3c ae d1 f8
00000002 2 0x8001 0x6c94 e1 a7 17 94 6e f3 90 d9 ca 11 82 da e6 cb bb 61 f0 ac b0 cf
00000003 3 0x8001 0x3bf8 ad 64 23 8e d0 18 59 73 8e fb 2c f0 ba b2 38 ed 55 a6 d7 0b
00000004 4 0x8001 0x2a38 7b c0 b1 55 31 9d f9 2d 31 fa 60 63 a3 e9 56 61 55 2d 0e fb
00000005 5 0x8001 0x29f7c 61 41 c3 6f 82 5a 62 09 3b 4b a2 8b 07 05 46 80 ec d4 69 a7
00000006 6 0x8001 0x5800c 80 d7 04 96 e2 83 4e 11 6c 15 44 9e f1 be 16 da a7 ce 62 67
00000007 7 0x8001 0xf5b0 41 f6 57 42 94 b4 b3 5e 6e 40 14 35 a2 0c bd c0 9e 36 f5 3f
00000008 8 0x8001 0x85304 40 85 29 af c5 02 07 e6 4b 97 55 5e 43 a1 73 5e c8 5a e1 aa
00000009 9 0x8001 0xa64c 1d 18 53 55 81 5b f6 4c 45 71 71 35 e6 54 03 3b ab 0c 93 bc
0000000A 10 0x8001 0x7778 aa 6b 00 01 47 dd 12 c8 38 e4 0e 58 b2 5d 3f 5f 51 05 85 f8
0000000B 11 0x8001 0x4b88 e5 32 75 90 51 a4 86 be 38 5d 6a 94 85 93 d6 bd 3c 70 89 ee
0000000C 12 0x8001 0x6f38 9a 8d 1f cd 38 b7 22 cc 6b 6a ba 3f f2 12 3c 00 7c 82 e5 19
0000000D 13 0x8001 0x572cc 43 11 19 56 a2 a1 27 33 a4 9c 88 9e 74 e6 85 a7 5e bd f1 56
0000000E 14 0x8001 0x2736c f1 1d 54 5c 1a 1a 6f c1 c7 11 a4 65 28 71 e7 fb 24 9f 13 8e
TMD signed by Root-CA00000001-CP00000004 using RSA-2048: 07 fa 64 98 a7 ed c3 1f 3e 0f 14 9c 3d 95 6e 1f 48 fe 01 7e [OK]
TMD Certificates:
- CP00000004 (RSA-2048)
Certificate signed by Root-CA00000001 using RSA-2048: 8d 4f ff f1 ba f5 f0 07 b8 b4 bd f9 03 b5 00 ad e5 e8 20 fc [OK]
- CA00000001 (RSA-2048)
Certificate signed by Root using RSA-4096: 6f 47 c8 5c b1 aa ee 83 b1 1d 73 3f 19 fe 6c 7e 8e 2f e4 50 [OK]
ETicket:
Title ID: '\x00\x00\x00\x01\x00\x00\x00$'
Title key IV: 00 00 00 01 00 00 00 24 00 00 00 00 00 00 00 00
Title key (encrypted): a1 72 53 16 ff 45 3c da d6 3e 84 3a 32 ce ee 47
Common key index: 2
ETicket signed by Root-CA00000001-XS00000003 using RSA-2048: ba 56 cd 7c ac 9e f6 99 c2 26 16 56 fc bc a7 9f 98 09 1e 16 [OK]
ETicket Certificates:
- XS00000003 (RSA-2048)
Certificate signed by Root-CA00000001 using RSA-2048: d7 0a a0 54 90 af 79 3e 49 10 af 47 9a 76 0f d2 75 f5 ad 12 [OK]
- CA00000001 (RSA-2048)
Certificate signed by Root using RSA-4096: 6f 47 c8 5c b1 aa ee 83 b1 1d 73 3f 19 fe 6c 7e 8e 2f e4 50 [OK]

 

[MartinDocNewland]

Right, I'm using WinMD5Free v1.20 to check IOS36 and I get this MD5: d34b0feb9701f54929df0948550c76c1
I don't know what checker you are using but the MD5 is not the same lol but I don't get why

EDIT

I'm using showmiiwads to rip the IOS's from my Nand backup

 

[Bug_Checker_]

Right, I'm using WinMD5Free v1.20 to check IOS36 and I get this MD5: d34b0feb9701f54929df0948550c76c1
I don't know what checker you are using but the MD5 is not the same lol but I don't get why

EDIT

I'm using showmiiwads to rip the IOS's from my Nand backup

I'm assuming showmiiwads is version 1.5 mod. I am assuming you have compared ALL of your "virgin" nand and current nand titles/ios's and only have ios36 to be different. ALL other titles/ios's are the same. Are these assumptions correct? Everything under title 200 and below are identical between the virgin and current nands?

Btw,the numbers from the example I posted are not md5 numbers but sha1 numbers and more involved than this discussion requires(for now).