Hacking Is this Wii savable? (Syscheck added)

  • Thread starter Thread starter BvanBart
  • Start date Start date
  • Views Views 15,235
  • Replies Replies 142
Can't we just use memtest86+ via wii linux?
mentest86(+) has nothing to do with linux
it runs directly on the bare metal like a os and has to be coded to support this hw
unfortunatly its for x86 (like the name suggests)

but if you run linux on your wii ther are other (generic but less effective) memory testers that might be used
eg memtester
 
Damn... i hate being on the other side of the world right now -.-

Just sending my package with a Wii (approx 2 Kilo's) will cost me 88 for North America and somewhere else in the world (so i guess south America) would be 110 Euro.

So sending is not an option :(. Because you can buy a new Wii for about 120 Euro. Thanks anyway for offering the help!


EDIT: Lol... i would have to pay that twice... or else it would not come back :blink:
 
mentest86(+) has nothing to do with linux
it runs directly on the bare metal like a os and has to be coded to support this hw
unfortunatly its for x86 (like the name suggests)

but if you run linux on your wii ther are other (generic but less effective) memory testers that might be used
eg memtester
It's a regular binary which can be launched via linux too but yeah your right, it's x86 and not this powerpc eabi or what the wii processor is.

@[member='B4rtj4h']:
Damn that's bad, I'm sorry for you....
 
Damn... i hate being on the other side of the world right now -.-

Just sending my package with a Wii (approx 2 Kilo's) will cost me 88 for North America and somewhere else in the world (so i guess south America) would be 110 Euro.

So sending is not an option :(. Because you can buy a new Wii for about 120 Euro. Thanks anyway for offering the help!


EDIT: Lol... i would have to pay that twice... or else it would not come back :blink:
That doesn't seem right to me. I had someone send me 5 wii's from brazil for $22 USD, and I had sent Marcan a PS3 to spain and it only cost me about $50 USD. Your countries postal system must really be treating you people like suckers if that's what they are charging for shipping.

You could always just remove the motherboard and just send that and then it only weighs about 6 ounces.
 
No, it's much worse than that. From the dlog.txt dump the device certificate is apparently missing the signature from Nintendo and was issued by Root-CA00000000-MS00000000 (instead of every other wii in existence which gets issued by Root-CA00000001-MS00000002). This would indicate the entire seeprom is blank. Yet somehow it passes the boot2 version check when starting up, as well as various other checks in the hackmii installer that should fail with a broken device certificate. Data can't both exist and not exist at the same time unless the RAM is faulty, which is exactly what ninty already said.

Most likely the RAM was already faulty and the 4.3 upgrade failed because of that. Not the other way around. You might be able to use the wii flawlessly for hours, days, maybe even months but it's always going to have the risk of random crashes or data corruption.

Just a suggestion, but what about if Nintendo *already* removed those checks in case of a seeprom failure (blank or corrupted physically)? I mean not every chip issues a blank certificate dump, and this way, the wii would boot up even if physically damaged. And since the chip lives inside the hollywood, it would be, nearly impossible to remove/replace it (because the wii would be unbooteable anyway) or the whole hollywood would be damaged.

Also, that app you did, would be interesting if it was merged onto dop-mii as a "certificate health check" option.
 
It is known from looking at boot1's code that it wouldn't let the wii boot if the SEEPROM was blank. If anyone wants to sacrifice a wii to try and prove otherwise I can arrange something.

That test app I made just calls ES_GetDeviceCert and prints the result.
 
Ok. We've seen boot 2 modified wiis refusing to run because of different hashed boot1.

1. Is seeprom rewritable through Wii? (risky as hell i know)

2. what about if the cert inside got corrupted? Because if the cert has some info, unfinished, boot1 would recognize even pieces of data of it? Or just a wrong hash will refuse boot1 to run?

Would be interesting to repeat this issue the OP had. We have the unfinished seeprom dump info. And yes, it'll probably kill the Wii, beyond repair.

So my current guess.. Maybe earlier wiis boot1 didn't do as many checks as newers or a bug saved this guy?
 
With RAM it could be even just one bit that is dead/stuck. That one bit might only get used during certain instructions and almost never every other time.

Try running tueidj's app a few more times to see if it ever gives a different output.

I really wish you could just send me this wii so we could get down to the root of the issue.
 
I just found out that my 4.3E wii is missing some channels?! (Wii vote channel for example)

+ i can make a Nand dump with the Simple FS Dumper. Is that anything we can do something with?


@ Deadlyfoez - I am still looking if there is no cheaper way for sending my mobo to you. I will keep you informed!
 
I just found out that my 4.3E wii is missing some channels?! (Wii vote channel for example)

+ i can make a Nand dump with the Simple FS Dumper. Is that anything we can do something with?


@ Deadlyfoez - I am still looking if there is no cheaper way for sending my mobo to you. I will keep you informed!
Missing channels don't mean a damn thing.
IIRC, Simple FS Dumper only dumps the files, not the raw nand, and it especially does not dump the keys which is most important. You can dump the keys using XYZZY, but that is an old old app and I'm not sure if it will run correctly on an updated wii. I think it needed DVDX installed for it to work, but I forget.

Even if you sent your wii to me it would be a crap shoot. I would be able to send it back to you, but I could not promise that it would come back in any better condition... but at this point you don't have much to lose.
 
Hey guys,

Might I have the same problem? My dlog is pretty empty but not as empty as his.

Output file dlog.txt opened for writing

Got device ID, 040419B9

Get device certificate, Dump:
0000: 00 01 00 02 00 D4 08 12 04 05 40 90 00 00 00 00
0010: 08 04 00 00 20 00 00 00 00 00 00 00 00 60 00 00
0020: 00 00 00 00 40 00 20 0A 14 00 00 00 00 04 00 00
0030: 00 00 10 50 02 80 00 40 00 00 00 00 00 10 00 00
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0080: 52 6F 6F 74 2D 43 41 30 30 30 30 30 30 30 30 2D
0090: 4D 53 30 30 30 30 30 30 30 30 00 00 00 00 00 00
00A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00C0: 00 00 00 02 4E 47 30 34 30 34 31 39 62 39 00 00
00D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0100: 00 00 00 00 00 00 00 00 01 65 EC 66 C7 84 CD D8
0110: 9B A7 9C 93 35 CF BD C9 0B D8 86 AF 6F 34 6C 52
0120: A9 A1 25 12 48 78 01 F2 C6 AF 59 3C 70 1E 88 38
0130: 51 1C 5E 63 38 CD 30 75 53 4E 42 42 03 28 39 1F
0140: 69 42 3D C3 00 00 00 00 00 00 00 00 00 00 00 00
0150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


Got SRAM, Dump:
0000: C2 6A 3D 92 00 00 00 00 00 00 00 00 0B 72 B6 BC
0010: 00 00 00 3C E6 BC EE FF BF EF ED BF FE 7D F7 FE
0020: 76 98 FF 6E BB FF 7B 1C 5E DE 3F DF AF F7 CB DD
0030: 00 00 00 00 00 00 00 00 DE 58 7A B4 2A 59 F6 2F

All done!


SEEPROM PROBLEM. Not fixed but identified. THANKS ALL!
 
XYZZY requires IOS36v1042, which does not work on "recent" Wiis. A fully patched IOS36 might work, but i think i tried that and it ran into some error. Worth trying for sure, but don't expect too much.
 
I don't expect this to miraculously resolve your issues. Nevertheless I do have a bluesky suggestion. An older version of something long since forgotten gave me this same problem by introducing the korean keys into my system in some way apparently not kosher with my wii. I shared all of your symptoms with installing, and no one could help me. I tried all available means at the time and got impossible responses from diagnostic apps. After removing anything korean key related, my wii immediately functioned fine. Later when the corp packages included korean key, I tried them and had no problems. I only mention this because I noticed your OP have some select k-only ios. I haven't had much wii tinkering in quite a while. Best of luck.
 

Site & Scene News

Popular threads in this forum