Hacking Is there a way to verify that BootMii is installed as boot2 and IOS ?

[KokoseiJ]

Here are the files: https://easyupload.io/6rzqop



I did, no luck...

please try using an absolute path, too. If other ones are not the case, I can only think of it having a problem of detecting relative paths.

 

[L3gi0n0fh311]

F:\>cd nandbincheck

F:\nandBinCheck>nandbincheck nand.bin
Qt: Untested Windows version 6.2 detected!
** nandBinCheck : Wii nand info tool **
   from giantpune
   svn r: 104
   built: Jun  5 2011 21:29:38
"Error setting path to nand object"

F:\nandBinCheck>F:\nandBinCheck\nandbincheck.exe nand.bin
Qt: Untested Windows version 6.2 detected!
** nandBinCheck : Wii nand info tool **
   from giantpune
   svn r: 104
   built: Jun  5 2011 21:29:38
"Error setting path to nand object"

 

[KokoseiJ]

F:\>cd nandbincheck

F:\nandBinCheck>nandbincheck nand.bin
Qt: Untested Windows version 6.2 detected!
** nandBinCheck : Wii nand info tool **
   from giantpune
   svn r: 104
   built: Jun  5 2011 21:29:38
"Error setting path to nand object"

F:\nandBinCheck>F:\nandBinCheck\nandbincheck.exe nand.bin
Qt: Untested Windows version 6.2 detected!
** nandBinCheck : Wii nand info tool **
   from giantpune
   svn r: 104
   built: Jun  5 2011 21:29:38
"Error setting path to nand object"

No, I mean, use the absolute path for the nand file.

 

[L3gi0n0fh311]

F:\nandBinCheck>dir
 Volume in drive F is Corsair
 Volume Serial Number is 0652-FE00

 Directory of F:\nandBinCheck

03/12/2021  11:59 AM    <DIR>          .
03/12/2021  11:59 AM    <DIR>          ..
03/11/2021  06:30 PM             1,024 keys.bin
02/10/2012  09:58 PM            43,008 libgcc_s_dw2-1.dll
02/10/2012  09:58 PM           812,032 libstdc++-6.dll
02/10/2012  09:58 PM            11,362 mingwm10.dll
03/12/2021  11:53 AM       322,827,189 nand.7z
03/11/2021  04:24 PM       553,648,128 nand.bin
06/05/2011  09:30 PM           805,376 nandBinCheck.exe
02/10/2012  09:58 PM         2,513,408 QtCore4.dll
02/10/2012  09:58 PM         9,818,624 QtGui4.dll
02/10/2012  09:58 PM         1,228,800 QtNetwork4.dll
              10 File(s)    891,708,951 bytes
               2 Dir(s)  127,091,388,416 bytes free

F:\nandBinCheck>nandbincheck F:\nandBinCheck\nand.bin
Qt: Untested Windows version 6.2 detected!
** nandBinCheck : Wii nand info tool **
   from giantpune
   svn r: 104
   built: Jun  5 2011 21:29:38
"Error setting path to nand object"

 

[SaulFabre]

Here are the files: https://easyupload.io/6rzqop



I did, no luck...

Do you have installed in your computer the Qt SDK in order for get the nandBinCheck working?

In http://wiibrew.org/wiki/NandBinCheck I saw this info:
"The download link is for the Windows version. You also need some DLL files, you will find the links and notice for them on the Ohneschwanzenegger page.

Here is a Mac OS X version. You will need to install the Qt SDK from here in order to run it."

The Windows release requires Ohneschwanzenegger, the necessary DLLs in order for work, and maybe the Qt SDK in order for run it correctly.

Download links:

Ohneschwanzenegger: http://wiibrew.org/wiki/Ohneschwanzenegger
Necessary DLLs (put them on both Ohneschwanzenegger folder and nandBinCheck folder: http://www.mediafire.com/file/ow9bg9wsto5ak1w/giantpune-tools-dlls.zip/file
Nokia Qt SDK (only install it if after installation of these files it still have issues): https://download.cnet.com/Qt-SDK/3000-2069_4-75305206.html

Greetings

 

[L3gi0n0fh311]

The libs are in the same folder nandBinCheck.exe is in ... I don't think there are any dependency issues here...

 

[SaulFabre]

The libs are in the same folder nandBinCheck.exe is in ... I don't think there are any dependency issues here...

But do you have installed the program Ohneschwanzenegger?

 

[L3gi0n0fh311]

But do you have installed the program Ohneschwanzenegger?

I did but it doesn't verify nand.bins....

 

[KokoseiJ]

The Windows release requires Ohneschwanzenegger, the necessary DLLs in order for work, and maybe the Qt SDK in order for run it correctly.

You don't exactly need Ohneschwanzenegger, They just share some dll files together.

I'm on my way to check it by myself, but I'm pretty much certain that his Windows is being quirky. Windows acts like that sometimes..

EDIT: Seems like it also contains core Qt4 libraries, I doubt they have to be obtained separately.

EDIT2:

@L3gi0n0fh311 Seems like your NAND backup is actually corrupted! It works well with my NAND backup, but throws the same error with your NAND backup.

It was very wise move to try to verify your backup, time to make a new one. Since the error is caused by your improper NAND dump, It should work with future dumps unless they keep getting corrupted.

EDIT3: I also recommend you to get rid of the link to your NAND backup- people could do nasty stuffs with it.

 

[L3gi0n0fh311]

Ok I made a new backup and tested it with the checker...here are the results:

checking for lost clusters...
total used clusters 2e8d of 0x8000
found 0 lost clusters
UNK ( 0xffff ) 8 (993, 994, 995, 996, 997, 77c5, 77c6, 77c7)
free            4d2b
verifying ecc...
2 out of 832320 pages had incorrect ecc.
they were spread through 2 clusters in 2 blocks:
 (2, 6)
0 of those clusters are non-special (they belong to the fs)
verifying hmac...
verifying hmac for 611 files
0 files had bad HMAC data
checking HMAC for superclusters...
0 superClusters had bad HMAC data

Am I good now ?

Can you remove the link from your quote block as well ?

 

[KokoseiJ]

Ok I made a new backup and tested it with the checker...here are the results:

checking for lost clusters...
total used clusters 2e8d of 0x8000
found 0 lost clusters
UNK ( 0xffff ) 8 (993, 994, 995, 996, 997, 77c5, 77c6, 77c7)
free            4d2b
verifying ecc...
2 out of 832320 pages had incorrect ecc.
they were spread through 2 clusters in 2 blocks:
 (2, 6)
0 of those clusters are non-special (they belong to the fs)
verifying hmac...
verifying hmac for 611 files
0 files had bad HMAC data
checking HMAC for superclusters...
0 superClusters had bad HMAC data

Am I good now ?

Wonderful, It's all green. I think it is safe to go with it now.
Good luck!

 

[SaulFabre]

You don't exactly need Ohneschwanzenegger, They just share some dll files together.

I'm on my way to check it by myself, but I'm pretty much certain that his Windows is being quirky. Windows acts like that sometimes..

I think i saw what's the trouble.
Some necessary paths for make the CMD work correctly aren't mentioned.
It can be checked easily by going to System Properties (System Advanced Settings) by pressing Windows + R, writing sysdm.cpl, click on the Advanced tab and then click in Environment Variables button.
You will get a screen like thi

You don't exactly need Ohneschwanzenegger, They just share some dll files together.

I'm on my way to check it by myself, but I'm pretty much certain that his Windows is being quirky. Windows acts like that sometimes..

EDIT: Seems like it also contains core Qt4 libraries, I doubt they have to be obtained separately.

EDIT2:

@L3gi0n0fh311 Seems like your NAND backup is actually corrupted! It works well with my NAND backup, but throws the same error with your NAND backup.

It was very wise move to try to verify your backup, time to make a new one. Since the error is caused by your improper NAND dump, It should work with future dumps unless they keep getting corrupted.

EDIT3: I also recommend you to get rid of the link to your NAND backup- people could do nasty stuffs with it.

I agree with this @KokoseiJ, the NAND backup is severely corrupted. I recommed doing a new NAND backup with BootMii, and let it check before you can check it with nandBinCheck.

PD: I've written a solution for that trouble but i think it's now useless but maybe this will help in a future:

I think i saw what's the trouble.
Some necessary paths for make the CMD work correctly aren't mentioned.
It can be checked easily by going to System Properties (System Advanced Settings) by pressing Windows + R, writing sysdm.cpl, click on the Advanced tab and then click in Environment Variables button.
Look at hese images for see how to do that:

Once entered to those settings, you will get a screen like this:

Go to the System Variables (NOT User Variables) box, then click in Path variable (from System Variables), then click in Edit.

Now this screen will appear:

Once entered to that screen, add these routes to the PATH variable, by pressing the New button and copying and pasting these routes (one per time), and then pressing Enter for each new path entered:

%SystemRoot%
%SystemRoot%\SysWow64
%SystemRoot%\System32
C:\Program Files (x86)\Common Files\
C:\Program Files (x86)\Common Files\SIL\
%SystemRoot%\System32\Wbem
%SYSTEMROOT%\System32\OpenSSH\
%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

Be sure to use and have all of these paths, otherwise the CMD won't work correctly.

Once finished doing all the steps, save the changes by clicking OK or Accept (NOT closing the windows, NOT pressing Cancel) in all three windows as shown:

Then, open again the CMD for see if it worked.
Greetings

--------------------- MERGED ---------------------------

Wonderful, It's all green. I think it is safe to go with it now.
Good luck!

Great eyes for see how's the NAND backup @KokoseiJ

 

[KokoseiJ]

I think i saw what's the trouble.
Some necessary paths for make the CMD work correctly aren't mentioned.
It can be checked easily by going to System Properties (System Advanced Settings) by pressing Windows + R, writing sysdm.cpl, click on the Advanced tab and then click in Environment Variables button.
You will get a screen like thi

I agree with this @KokoseiJ, the NAND backup is severely corrupted. I recommed doing a new NAND backup with BootMii, and let it check before you can check it with nandBinCheck.

PD: I've written a solution for that trouble but i think it's now useless but maybe this will help in a future:

I think i saw what's the trouble.
Some necessary paths for make the CMD work correctly aren't mentioned.
It can be checked easily by going to System Properties (System Advanced Settings) by pressing Windows + R, writing sysdm.cpl, click on the Advanced tab and then click in Environment Variables button.
Look at hese images for see how to do that:
View attachment 251428

View attachment 251429

View attachment 251430

Once entered to those settings, you will get a screen like this:

View attachment 251431

Go to the System Variables (NOT User Variables) box, then click in Path variable (from System Variables), then click in Edit.

View attachment 251432

Now this screen will appear:

View attachment 251433

Once entered to that screen, add these routes to the PATH variable, by pressing the New button and copying and pasting these routes (one per time), and then pressing Enter for each new path entered:

%SystemRoot%
%SystemRoot%\SysWow64
%SystemRoot%\System32
C:\Program Files (x86)\Common Files\
C:\Program Files (x86)\Common Files\SIL\
%SystemRoot%\System32\Wbem
%SYSTEMROOT%\System32\OpenSSH\
%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

Be sure to use and have all of these paths, otherwise the CMD won't work correctly.

View attachment 251434

Once finished doing all the steps, save the changes by clicking OK or Accept (NOT closing the windows, NOT pressing Cancel) in all three windows as shown:

View attachment 251435

View attachment 251436

View attachment 251437
Then, open again the CMD for see if it worked.
Greetings

Thanks for your investigation, but We already confirmed that it was due to his corrupted dump and is now working as intended. Nothing was broken from the first place, other than his dump...

 

[L3gi0n0fh311]

Thanks for your investigation, but We already confirmed that it was due to his corrupted dump and is now working as intended. Nothing was broken from the first place, other than his dump...

What could be the cause of corruption ? Is it because I skipped the verification process ? I chkdsked the SD card and no errors were found...is there a way other than chkdsk to make sure other things are not corrupted ?

 

[SaulFabre]

What could be the cause of corruption ? Is it because I skipped the verification process ? I chkdsked the SD card and no errors were found...is there a way other than chkdsk to make sure other things are not corrupted ?

@L3gi0n0fh311 Yes, NAND backup corruption is most because you skip NAND checking / verification process after making the NAND backup.
In your next NAND backup, make sure to follow all steps and don't skip any step for make sure that your NAND backup is not corrupted.
Greetings

 

[L3gi0n0fh311]

@L3gi0n0fh311 Yes, NAND backup corruption is most because you skip NAND checking / verification process after making the NAND backup.
In your next NAND backup, make sure to follow all steps and don't skip any step for make sure that your NAND backup is not corrupted.
Greetings

I followed the www.wii.guide guide...they said there that it is ok to :

• After this step, it will verify the backup. While it is recommended, it can be skipped by pressing the EJECT button on your Wii.

Have there been other cases like this where people skip verification and end up with a corrupted nand.bin ? or is it just me ?

Hopefully, If the nand.bin was corrupted this way, it doesn't mean other files on the SD card are corrupted as well, right ?

 

[SaulFabre]

I followed the www.wii.guide guide...they said there that it is ok to :



Have there been other cases like this where people skip verification and end up with a corrupted nand.bin ? or is it just me ?

Hopefully, If the nand.bin was corrupted this way, it doesn't mean other files on the SD card are corrupted as well, right ?

Most cases of broken NAND backup (nand.bin) are if you turn off the Wii when the NAND backup is being created or if you skip the verification check on BootMii after backup.
But hopefully, if nand.bin file goes corrupted, the other files on your SD Card won't get corrputed.

 

[KokoseiJ]

Have there been other cases like this where people skip verification and end up with a corrupted nand.bin ? or is it just me ?

I mean, verification exists for reason. Things like this could happen time to time, and verification is in place to prevent things like this happen. It is possible to skip it- but it's not recommended. It's not like it takes a lot of time either, so just do yourself a favour and get one more cup of coffee.
integrity ensured backup definitely worth more than extra few minutes it takes to verify.

 

[XFlak]

I'm not clear what is meant by this
https://mobile.twitter.com/marcan42/status/1365529798865424385

Does this mean there are certain to be issues if u skip verifying your nand dump?