Hacking Metoid Other M Baby's Cry freeze LAST THREAD

ddrhazy

Member
Newcomer
Joined
Dec 22, 2008
Messages
7
Trophies
0
XP
31
Country
United States
WiiPower said:
Seriously, if you download a game that is a DL game, and the download is only 4.x GB and it does NOT say it's a special DVD5 version, why do you expect this to work?

The ISO itself is still 7 gigs but when rared they got it down to 4.3 somehow. I know compression and the actual ripping of the game are two different things. Don't ask me why but avoid all 4 gig torrents at all cost.
 

Tanas

Well-Known Member
Member
Joined
Aug 19, 2006
Messages
2,257
Trophies
1
Website
Visit site
XP
113
Country
jmlsteele said:
Tanas said:
If you want to check if your copy of Metroid is ok, using WiiScrubber extract the movie "dm03to04.sfd" (this is the baby's cry cutscene) and play it using VLC and if the movie freezes and doesnt play until the end then the copy you have is more than likely bad.
I tried this on the WiiTard release and the movie froze at the exact same point as it does in the game, the movie plays fine when tested using a working copy.

How far into the game is Ridley's scene?

I don't suppose you, or someone else, could post an md5, or some similar checksum of the valid file could you? The one I had stutters (which I saw you said is normal), has a messed up palette, and freezes between 0:19 and 1:13, however after that 54 second freeze continues to play.

(From the Bioshock Proper Repack)

No report yet as I'm not gonna download the whole thing from my seedbox if it turns out to be broken.

These are the crc32 from the different releases.
Working P2P = D1590111
Working WiiERD = D1590111
My Non Working ind = 14DB47F2
Bad WiiTard = 77B29C01

So it looks as though if the CRC isnt D1590111 then the copy is definitely bad.

Use CheckCRC from the link below.
http://www34.brinkster.com/dizzyk/download/CheckCRC.zip
 

chickenlips

Member
Newcomer
Joined
Sep 3, 2010
Messages
20
Trophies
0
XP
163
Country
1. Not anymore!
toot.gif
I got rid of WiiTard's version, and am now using [Wii]Metroid_Other_M[NTSC][MULTi3][WiiSOS.com]
2. WBFS ... by the by, using WBFS Manager 3.0
3. cIOS222
4. Configurable USB Loader [cfg59-222]. This solved my earliest problem - BLACK SCREEN when trying to load.
5. [Wii]Metroid_Other_M[NTSC][MULTi3][WiiSOS.com]
6. No I did not.
7. I am NOT having issues now! SO far, all is well.
yaywii.gif
I have read that this release is underdumped, so I am expecting soemthing to come up .... but so far, so good!

I hope you find this useful in figuring out the general solution. For me, the WiiTard release caused the Baby's Cry freeze. And CFG Loader was the only one that could actually load games through USB. I'm using a Japanese Wii, 4.2.
 

Wiimm

Developer
Member
Joined
Aug 11, 2009
Messages
2,292
Trophies
1
Location
Germany
Website
wiimmfi.de
XP
1,519
Country
Germany
I have done 2 tests, first with a raw copy and then with a scrubbed copy:

1. no freeze
2. WBFS partition
3. Hermes 5.1 / 222 based on IOS38
4. CFG loader v57/222
5. PAL, id=R3OP01, non scrubbed, self made 1:1 dump with cfg loader
6. no, update partition is still there
7. works fine


1. no freeze
2. WBFS partition
3. Hermes 5.1 / 222 based on IOS38
4. CFG loader v57/222
5. PAL, id=R3OP01, SCRUBBED with wit
6. no, update partition is still there
7. works fine
 

frazz

Well-Known Member
Newcomer
Joined
Jun 16, 2009
Messages
46
Trophies
0
XP
82
Country
Wiimm said:
I have done 2 tests, first with a raw copy and then with a scrubbed copy:

1. no freeze
2. WBFS partition
3. Hermes 5.1 / 222 based on IOS38
4. CFG loader v57/222
5. PAL, id=R3OP01, non scrubbed, self made 1:1 dump with cfg loader
6. no, update partition is still there
7. works fine


1. no freeze
2. WBFS partition
3. Hermes 5.1 / 222 based on IOS38
4. CFG loader v57/222
5. PAL, id=R3OP01, SCRUBBED with wit
6. no, update partition is still there
7. works fine


What is the CRC of your versions
 

Wiimm

Developer
Member
Joined
Aug 11, 2009
Messages
2,292
Trophies
1
Location
Germany
Website
wiimmfi.de
XP
1,519
Country
Germany
Is the crc relevant?
The iso size depends from the WBFS block size and different iso sizes results in different crc check sums.
The size of my ISOs is : 8 514 437 120

Use the internal check sums to verify if your dump is good or bad.
 

WiiPower

Well-Known Member
OP
Member
Joined
Oct 17, 2008
Messages
8,165
Trophies
0
XP
345
Country
Gambia, The
Wiimm said:
Is the crc relevant?
The iso size depends from the WBFS block size and different iso sizes results in different crc check sums.
The size of my ISOs is : 8 514 437 120

Use the internal check sums to verify if your dump is good or bad.

You know that this is too complicated for 90%+ of the users here. A GUI version of your tools with a button "check .iso" would help a lot, and then it would tell the number of paritions, if it's scrubbed, and if data area, the area which must not be scrubbed, is ok. Or teach them how to your use tools.

I think over 90% of the issues here are:
- cIOSrev14 was used to dump the game(wiitard release)
- cIOSrev14 is used to play the game(->same issue as when using the wiitard release)
- a bad wbfs manager was used -> freeze on the
Ridley
scene or somewhere else depending if the update was removed or not

I think what really most people here don't understand is that scrubbing gets the .compressed iso maybe 1 GB smaller. But that's all you can get by scubbing this game. If the commpressed .iso is only 4.x, then this means there is content removed and not only junk. Again, if it was a special DVD5 version, then it would be fine, but these would be 4.x GB before and after decomressing(which i thought was obvious).
 

Sabin_Figaro

Well-Known Member
Member
Joined
Jul 16, 2009
Messages
226
Trophies
0
Website
Visit site
XP
27
Country
Colombia
WiiPower said:
Wiimm said:
Is the crc relevant?
The iso size depends from the WBFS block size and different iso sizes results in different crc check sums.
The size of my ISOs is : 8 514 437 120

Use the internal check sums to verify if your dump is good or bad.

You know that this is too complicated for 90%+ of the users here. A GUI version of your tools with a button "check .iso" would help a lot, and then it would tell the number of paritions, if it's scrubbed, and if data area, the area which must not be scrubbed, is ok. Or teach them how to your use tools.

I think over 90% of the issues here are:
- cIOSrev14 was used to dump the game(wiitard release)
- cIOSrev14 is used to play the game(->same issue as when using the wiitard release)
- a bad wbfs manager was used -> freeze on the
Ridley
scene or somewhere else depending if the update was removed or not

I think what really most people here don't understand is that scrubbing gets the .compressed iso maybe 1 GB smaller. But that's all you can get by scubbing this game. If the commpressed .iso is only 4.x, then this means there is content removed and not only junk. Again, if it was a special DVD5 version, then it would be fine, but these would be 4.x GB before and after decomressing(which i thought was obvious).

My brother and I have the same pirate release and same cios (rev20 base 56) and it freezes. We use the same wbfs manager. I will check if the version is different cause it works for me and it does not work on his
 

jmlsteele

Member
Newcomer
Joined
Dec 21, 2009
Messages
7
Trophies
0
XP
9
Country
Canada
Wiimm said:
Here is a little test to foind out if your image is scrubbed and/or a bad dump.

Get WIT, open a console and execute the following commands. The tests take time because the whole image must be read, decrypted and millions of hash values must be calculated and verified.[*] First assume you have a non scrubbed image.
Use the command: wit verify --raw yourimage
If the result looks like this, it's ok:
Code:
+OKÂÂÂÂ .0ÂÂUPDATEÂÂR3OP01 Metroid - Other M [R3OP01].wdf
+OKÂÂÂÂ .1ÂÂDATAÂÂÂÂR3OP01 Metroid - Other M [R3OP01].wdf

If the output looks like that, than it is scrubbed or a bad dump:
Code:
!H0-ERR .0ÂÂUPDATEÂÂR3OP01 Metroid - Other M [R3OP01].wdf
!H0-ERR .1ÂÂDATAÂÂÂÂR3OP01 Metroid - Other M [R3OP01].wdf
If only 1 line for the DATA partition is printed, the UPDATE partition was removed.
.
[*] If the previous test fails (not "+OK" for all partitions) then try the verify in scrubbed mode.
Use the command: wit verify yourimage
The command is the same as above, but without --raw.
Analyzing the output is like above. If it fails again it is a bad dump.


Thanks for the tool. Checked my dump and it came out all OK. I'll grab it and issue a report soon.

Also I love that your tools are cross platform and not just windows. Finding a (good) Linux WBFS manager was a royal PITA a while ago (I since have found something to meet my needs).
 

Shebang

Well-Known Member
Member
Joined
Mar 17, 2007
Messages
464
Trophies
0
XP
157
Country
Belgium
I only saw references to NTSC so far - I have this problem in the PAL version, too. Unfortunately I can only say I have a Wasabi 3, 4.2E and then it was soft-modded about a year ago, running under an old version of USB GX Loader.
 

Terrulin

Well-Known Member
Newcomer
Joined
Apr 19, 2009
Messages
48
Trophies
0
XP
27
Country
United States
WiiPower said:
I think over 90% of the issues here are:
- cIOSrev14 was used to dump the game(wiitard release)
- cIOSrev14 is used to play the game(->same issue as when using the wiitard release)
- a bad wbfs manager was used -> freeze on the
Ridley
scene or somewhere else depending if the update was removed or not

Im not so sure the wbfs managers version of WBFS_file was bad. I had the
Ridley scene
freeze using the manager, then the same thing when i manually used the updated wbfs_file.exe to remove the update. I passed that freeze when I left the update in the file. BUT it added the Baby's cry freeze to the beginning which I had not had when the update was removed. So if someone is willing to start the game with the update removed, they can get past the opening "Baby's Cry", but will freeze later. They can then put the update back in and get past the above scene. This is with the ones referred to as bad dumps (ind, wiitard). I havent been able to try the ones people seem to have not had problems with yet (bioshock mostly). But I guess mainly I was saying it doesnt appear to be the game manager's fault when I get the same behavior with the manager and the updated wbfs_file.exe
 

Wiimm

Developer
Member
Joined
Aug 11, 2009
Messages
2,292
Trophies
1
Location
Germany
Website
wiimmfi.de
XP
1,519
Country
Germany
A complete other scenario:
(wwt add -a mpm.wdf --id K --name 'Metroid: Other M (Clone)' --psel data)

1. no freeze
2. WBFS partition
3. Wanin 249 Rev 19 based on IOS38
4. NeoGamma R9 beta 44
5. PAL, id=K3OP01, SCRUBBED with wit,
... cloned with new ID K3OP01 (disc-head+ticket+tmd+boot.bin),
... fake signed (ticket+tmd)
6. Update partition removed with wit
7. works fine, played until meeting with federation soldiers.
 

erolz

Well-Known Member
Member
Joined
Jul 22, 2008
Messages
468
Trophies
0
XP
606
Country
Belgium
wich version does work?

Metroid Other M PAL Wii-WiiERD
Metroid.Other.M.USA.REAL.PROPER.REPACK.WII-BiOSHOCK
Metroid Other M PROPER USA WII-WiiTARD
Metroid Other M NTSC WII-XB3
 

ARISMENDY_64

Member
Newcomer
Joined
Dec 5, 2009
Messages
14
Trophies
0
XP
11
Country
United States
erolz said:
wich version does work?

Metroid Other M PAL Wii-WiiERD
Metroid.Other.M.USA.REAL.PROPER.REPACK.WII-BiOSHOCK
Metroid Other M PROPER USA WII-WiiTARD
Metroid Other M NTSC WII-XB3

WD_MTRDOM
yaywii.gif
 

erolz

Well-Known Member
Member
Joined
Jul 22, 2008
Messages
468
Trophies
0
XP
606
Country
Belgium
ARISMENDY_64 said:
erolz said:
wich version does work?

Metroid Other M PAL Wii-WiiERD
Metroid.Other.M.USA.REAL.PROPER.REPACK.WII-BiOSHOCK
Metroid Other M PROPER USA WII-WiiTARD
Metroid Other M NTSC WII-XB3

WD_MTRDOM
yaywii.gif
what is the full name of this release?
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: Spend 50 hours playing the game