Use the homebrew version and not the firmware version, it isn't updated. And for compiling the homebrew you don't need fw.img.
(And I am pretty sure that the Makefile of iosuhax download fw.img, so just replace the keys and run make)
Thank you, not sure what I was thinking there, I added the keys to getfwimg.py and it did in fact download the needed files, thanks for your help!
If I am able to open my SLC dump in to NAND extract (browse and extract the contents like system.xml) with the opt.bin I pulled from my redNAND sd card, I should be good to go to be able to restore my brick with my redNAND, right?
Yes. But as I said, before flashing it, dump you current SLC before and verify it with nandDumpCheck! So if the redNAND dump won't work you could just fix it with the cbhc remover tool.
Sound's good. I ordered the teensy and will report back once I start getting it all wired up. Will the CBHC remover tool work if the brick was caused by formatting-the-sysNAND-with-CBHC brick?
*EDIT* I was doing some critical thinking in the shower and it makes sense that it should fix it. Correct me if i'm wrong but, the reason my unit is bricked is because I formatted the sysNAND which actually just erases the MLC but has my Brain Age DS game on it. My unit is loading the SLC which is trying to look for Brain Age via the system.xml title ID and can't find it which is why it's bricked. That also explains why the default_title_id on my redNAND backup is the correct title ID; the redNAND image was from before CBHC was installed!
Also, just checking, is this what I should get when running BinCheck, Fixer, and then BinCheck on the fixed file?
*EDIT* I was doing some critical thinking in the shower and it makes sense that it should fix it. Correct me if i'm wrong but, the reason my unit is bricked is because I formatted the sysNAND which actually just erases the MLC but has my Brain Age DS game on it. My unit is loading the SLC which is trying to look for Brain Age via the system.xml title ID and can't find it which is why it's bricked. That also explains why the default_title_id on my redNAND backup is the correct title ID; the redNAND image was from before CBHC was installed!
Also, just checking, is this what I should get when running BinCheck, Fixer, and then BinCheck on the fixed file?
Attachments
Last edited by Brenex,
Yeah, that is what CBHC remover does, change default_title_id (or to be more precise, restore the configuration that was backed up during cbhc installation)
And that output is as expected... Running the check on not full dump is meaningless.
And that output is as expected... Running the check on not full dump is meaningless.
Adds missing ECC and HMAC data, afaik.
** EDIT : Maybe the correct way to state this is it adds the missing ECC data and corrects the HMAC data?
Last edited by GraFfiX420,
Also, using CBHC remover doesn't work. There is no syshax.xml file in sys/config. See the following picture. I did use nandextract to see what was saved in the default ID for the system.xml and it's 0005000010179b00 which corresponds with brain age training. Why don't you just have CBHCremover search for default title id and just replace whatever is written there with the default 0005001010040100 ?
Attachments
Many thanks for these tools. Is there some documentation somewhere (other than looking in the source) regarding nandbincheck and how to interpret its output?
I've used your homebrew NAND dumper to dump the NANDs for my Wii U and ran nandbincheck over the slc.bin and slccmpt.bin for interest. This is from a Wii U that is working fine as far as I know. I would like to know if the following output is normal. I ran the NAND dump homebrew a couple of times, a day or two apart, to compare.
I know you've said that the bad HMAC on scfm.img is fine, but what about on fw.img? What do the "UNK" entries mean and why are they so different between the two dumps? What is going on with the vWii errors?
First dump, SLC:
Second dump, SLC:
Both dumps, SLCCMPT - both dumps gave same nandbincheck output, probably because I hadn't booted into vWii between the two dumps:
I've used your homebrew NAND dumper to dump the NANDs for my Wii U and ran nandbincheck over the slc.bin and slccmpt.bin for interest. This is from a Wii U that is working fine as far as I know. I would like to know if the following output is normal. I ran the NAND dump homebrew a couple of times, a day or two apart, to compare.
I know you've said that the bad HMAC on scfm.img is fine, but what about on fw.img? What do the "UNK" entries mean and why are they so different between the two dumps? What is going on with the vWii errors?
First dump, SLC:
Code:
** nandBinCheck : Wii nand info tool **
from giantpune
built: Mar 24 2017 23:49:06
NAND Type: SLC (WiiU)
checking boot1...
Boot1 hash: "3806d41a5c5f139f5b09bbe5b74a5ec45e0f5507"
Boot1 OK!
checking for lost clusters...
total used clusters 3094 of 0x8000
found 0 lost clusters
UNK ( 0xffff ) c1 (738, 739, 73a, 73b, 73c, 73d, 73e, 73f, 9c0, 9c1, 9c2, 9c3, 9
c4, 9c5, 9c6, 9c7, 1248, 1249, 124a, 124b, 124c, 124d, 124e, 124f, 12f8, 12f9, 1
2fa, 12fb, 12fc, 12fd, 12fe, 12ff, 13b0, 13b1, 13b2, 13b3, 13b4, 13b5, 13b6, 13b
7, 13b8, 13b9, 13ba, 13bb, 13bc, 13bd, 13be, 13bf, 13c0, 13c1, 13c2, 13c3, 13c4,
13c5, 13c6, 13c7, 13c8, 13c9, 13ca, 13cb, 13cc, 13cd, 13ce, 13cf, 13d0, 13d1, 1
3d2, 13d3, 13d4, 13d5, 13d6, 13d7, 13d8, 13d9, 13da, 13db, 13dc, 13dd, 13de, 13d
f, 14f0, 14f1, 14f2, 14f3, 14f4, 14f5, 14f6, 14f7, 14f8, 14f9, 14fa, 14fb, 14fc,
14fd, 14fe, 14ff, 17a0, 17a1, 17a2, 17a3, 17a4, 17a5, 17a6, 17a7, 1878, 1879, 1
87a, 187b, 187c, 187d, 187e, 187f, 18d8, 18d9, 18da, 18db, 18dc, 18dd, 18de, 18d
f, 196f, 197d, 197e, 197f, 1998, 1999, 199a, 199b, 199c, 199d, 199e, 199f, 19a0,
19a1, 19a2, 19a3, 19a4, 19a5, 19a6, 19a7, 19a8, 19a9, 19aa, 19ab, 19ac, 19ad, 1
9ae, 19af, 19c0, 19c1, 19c2, 19c3, 19c4, 19c5, 19c6, 19c7, 19c8, 19c9, 19ca, 19c
b, 19cc, 19cd, 19ce, 19cf, 19d0, 19d1, 19d2, 19d3, 19d4, 19d5, 19d6, 19d7, 19d8,
19d9, 19da, 19db, 19dc, 19dd, 19de, 19df, 1a00, 1a01, 1a02, 1a03, 1a04, 1a05, 1
a06, 1a07, 5e5b, 5e5c, 5e5d, 5e5e, 5e5f)
free 479b
verifying ecc...
1 out of 921408 pages had incorrect ecc.
they were spread through 1 clusters in 1 blocks:
(2302)
1 of those clusters are non-special (they belong to the fs)
verifying hmac...
verifying hmac for 608 files
hmac bad (1)
"fw.img" is adc200 bytes ( 2b8 ) clusters
00000000 ffadf577 03f2813c 022055db a7901111 ...w...<. U.....
00000010 6f72658f d0adf577 03f2813c 022055db ore....w...<. U.
00000020 a7000000 00000000 00000000 00000000 ................
00000030 640f9b00 0209fd06 85067a09 180ce703 d.........z.....
00000000 ff901111 6f72658f d0000000 00000000 ....ore.........
00000010 00000000 00000000 00000000 00000000 ................
00000020 00000000 00000000 00000000 00000000 ................
00000030 b00bb00b 1800e70f 2a092a09 a702580d ........*.*...X.
00000000 ebd68614 971c86cd 4c524fa7 3da7dba3 ........LRO.=...
00000010 e69b1279 ...y
bad HMAC for "/sys/title/00050010/100040ff/code/fw.img"
hmac bad (1)
"scfm.img" is 8004000 bytes ( 2001 ) clusters
00000000 ff000000 00000000 00000000 00000000 ................
00000010 00000000 00000000 00000000 00000000 ................
00000020 00000000 00000000 00000000 00000000 ................
00000030 00000000 00000000 00000000 00000000 ................
00000000 ff000000 00000000 00000000 00000000 ................
00000010 00000000 00000000 00000000 00000000 ................
00000020 00000000 00000000 00000000 00000000 ................
00000030 00000000 00000000 9601690e 9b0d6402 ..........i...d.
00000000 d77444c0 6e1d28fb e45bd324 3ff6b662 .tD.n.(..[.$?..b
00000010 cbc0345e ..4^
bad HMAC for "/scfm.img"
2 files had bad HMAC data
checking HMAC for superclusters...
0 superClusters had bad HMAC dataSecond dump, SLC:
Code:
** nandBinCheck : Wii nand info tool **
from giantpune
built: Mar 24 2017 23:49:06
NAND Type: SLC (WiiU)
checking boot1...
Boot1 hash: "3806d41a5c5f139f5b09bbe5b74a5ec45e0f5507"
Boot1 OK!
checking for lost clusters...
total used clusters 309b of 0x8000
found 0 lost clusters
UNK ( 0xffff ) 9e (262, 263, 264, 265, 266, 267, 7e4, 7e5, 7e6, 7e7, 810, 811, 8
12, 813, 814, 815, 816, 817, 818, 819, 81a, 81b, 81c, 81d, 81e, 81f, 820, 821, 8
22, 823, 824, 825, 826, 827, 82c, 82d, 82e, 82f, 850, 851, 852, 853, 854, 855, 8
56, 857, 858, 859, 85a, 85b, 85c, 85d, 85e, 85f, 8b2, 8b3, 8b4, 8b5, 8b6, 8b7, 8
b8, 8b9, 8ba, 8bb, 8bc, 8bd, 8be, 8bf, 8c0, 8c1, 8c2, 8c3, 8c4, 8c5, 8c6, 8c7, 8
e8, 8e9, 8ea, 8eb, 8ec, 8ed, 8ee, 8ef, 8f0, 8f1, 8f2, 8f3, 8f4, 8f5, 8f6, 8f7, 9
e0, 9e1, 9e2, 9e3, 9e4, 9e5, 9e6, 9e7, 9f8, 9f9, 9fa, 9fb, 9fc, 9fd, 9fe, 9ff, a
a8, aa9, aaa, aab, aac, aad, aae, aaf, b00, b01, b02, b03, b04, b05, b06, b07, b
18, b19, b1a, b1b, b1c, b1d, b1e, b1f, b48, b49, b4a, b4b, b4c, b4d, b4e, b4f, b
50, b51, b52, b53, b54, b55, b56, b57, b58, b59, b5a, b5b, b5c, b5d, b5e, b5f, 2
3b6, 23b7)
free 47b7
verifying ecc...
1 out of 919616 pages had incorrect ecc.
they were spread through 1 clusters in 1 blocks:
(2302)
1 of those clusters are non-special (they belong to the fs)
verifying hmac...
verifying hmac for 614 files
hmac bad (1)
"fw.img" is adc200 bytes ( 2b8 ) clusters
00000000 ffadf577 03f2813c 022055db a7901111 ...w...<. U.....
00000010 6f72658f d0adf577 03f2813c 022055db ore....w...<. U.
00000020 a7000000 00000000 00000000 00000000 ................
00000030 640f9b00 0209fd06 85067a09 180ce703 d.........z.....
00000000 ff901111 6f72658f d0000000 00000000 ....ore.........
00000010 00000000 00000000 00000000 00000000 ................
00000020 00000000 00000000 00000000 00000000 ................
00000030 b00bb00b 1800e70f 2a092a09 a702580d ........*.*...X.
00000000 ebd68614 971c86cd 4c524fa7 3da7dba3 ........LRO.=...
00000010 e69b1279 ...y
bad HMAC for "/sys/title/00050010/100040ff/code/fw.img"
hmac bad (1)
"scfm.img" is 8004000 bytes ( 2001 ) clusters
00000000 ff000000 00000000 00000000 00000000 ................
00000010 00000000 00000000 00000000 00000000 ................
00000020 00000000 00000000 00000000 00000000 ................
00000030 00000000 00000000 00000000 00000000 ................
00000000 ff000000 00000000 00000000 00000000 ................
00000010 00000000 00000000 00000000 00000000 ................
00000020 00000000 00000000 00000000 00000000 ................
00000030 00000000 00000000 690e690e ba0d4502 ........i.i...E.
00000000 ca53f49b 0fef9f03 a96ac018 950cd85e .S.......j.....^
00000010 5a0bd40d Z...
bad HMAC for "/scfm.img"
2 files had bad HMAC data
checking HMAC for superclusters...
0 superClusters had bad HMAC dataBoth dumps, SLCCMPT - both dumps gave same nandbincheck output, probably because I hadn't booted into vWii between the two dumps:
Code:
** nandBinCheck : Wii nand info tool **
from giantpune
built: Mar 24 2017 23:49:06
NAND Type: SLCCMPT (vWii)
vWii - not checking boot
checking for lost clusters...
total used clusters 4282 of 0x8000
found 0 lost clusters
UNK ( 0xffff ) 0 ()
free 393e
verifying ecc...
4 out of 1158784 pages had incorrect ecc.
they were spread through 4 clusters in 4 blocks:
(427, 1040, 3607, 3696)
3 of those clusters are non-special (they belong to the fs)
verifying hmac...
verifying hmac for 370 files
hmac bad (1)
"00000005.app" is 1e92f40 bytes ( 7a5 ) clusters
00000000 ff81113c b0eb2a80 79aa2566 ea9477b2 ...<..*.y.%f..w.
00000010 22a4386a 1b81113c b0eb2a80 79aa2566 ".8j...<..*.y.%f
00000020 ea000000 00000000 00000000 00000000 ................
00000030 a904560b 7c0f7c0f ab0fab0f 4506ba09 ..V.|.|.....E...
00000000 ff9477b2 22a4386a 1b000000 40200099 ..w.".8j....@ ..
00000010 40000000 00200499 40000000 102004f1 @.... ..@.... ..
00000020 9c000000 00000000 00000000 00000000 ................
00000030 7f0f8000 8601790e 4c01b30e eb08eb08 ......y.L.......
00000000 0ed3e7c1 220845c9 3d6600ad 550763ed ....".E.=f..U.c.
00000010 6bca4485 k.D.
bad HMAC for "/title/00010001/4e415250/content/00000005.app"
hmac bad (1)
"00000002.app" is 17ee0b3 bytes ( 5fc ) clusters
00000000 ff7924ec 069e298a 569cbbb9 95846744 .y$...).V.....gD
00000010 81fb33cb 6f7924ec 069e298a 569cbbb9 ..3.oy$...).V...
00000020 95000000 00000000 00000000 00000000 ................
00000030 62069d09 230b230b ee0bee0b f20ff20f b...#.#.........
00000000 ff846744 81fb33cb 6f000000 40200099 ..gD..3.o...@ ..
00000010 40000000 00200499 40000000 102004f1 @.... ..@.... ..
00000020 9c000000 00000000 00000000 00000000 ................
00000030 ba06ba06 60036003 5b0f5b0f 9d089d08 ....`.`.[.[.....
00000000 98ebcb93 71b20d06 7247afed d2f7bbd4 ....q...rG......
00000010 b4fe18c5 ....
bad HMAC for "/title/00010001/584a4550/content/00000002.app"
hmac bad (1)
"00000015.app" is 17fde0 bytes ( 60 ) clusters
00000000 ff804315 376a91cd 81e492c0 87cbd1f1 ..C.7j..........
00000010 26c9599f 22804315 376a91cd 81e492c0 &.Y.".C.7j......
00000020 87000000 00000000 00000000 00000000 ................
00000030 ba04450b 26002600 320ecd01 7702880d ..E.&.&.2...w...
00000000 ffcbd1f1 26c9599f 22000000 00000000 ....&.Y.".......
00000010 00000000 00000000 00000000 00000000 ................
00000020 00000000 00000000 00000000 00000000 ................
00000030 aa0b5504 0101fe0e 83067c09 75018a0e ..U.......|.u...
00000000 59fe2224 7db50748 c8b94ef5 078689c7 Y."$}..H..N.....
00000010 f1bd0c48 ...H
bad HMAC for "/shared1/00000015.app"
3 files had bad HMAC data
checking HMAC for superclusters...
0 superClusters had bad HMAC data
Last edited by pelago,
Ah just saw this earlier post. So it seems that the dump looks all good. Nice!
Hi everyone! I recently had an issue with my Wii U and was wondering if there's a way to fix it...
In a nutshell, here's what happened:
-I went to the "Data Management" area to delete a game from memory but it gave me an error (can't recall what the error code was).
-Then I decided to format my drive in order to get things to a clean state and go from there
-Finally I went to "Delete All Content and Settings" and proceeded to format the drive
-The system restarted and started with the format but at some point it froze. Now its stuck on a loop (Turn on > Format starts > Console freezes) that I can't seem to get out of...
Is there any way out of this? Anyway to tell the console to ignore the format command and do a regular boot?
In a nutshell, here's what happened:
-I went to the "Data Management" area to delete a game from memory but it gave me an error (can't recall what the error code was).
-Then I decided to format my drive in order to get things to a clean state and go from there
-Finally I went to "Delete All Content and Settings" and proceeded to format the drive
-The system restarted and started with the format but at some point it froze. Now its stuck on a loop (Turn on > Format starts > Console freezes) that I can't seem to get out of...
Is there any way out of this? Anyway to tell the console to ignore the format command and do a regular boot?
We're you using CBHC?Hi everyone! I recently had an issue with my Wii U and was wondering if there's a way to fix it...
In a nutshell, here's what happened:
-I went to the "Data Management" area to delete a game from memory but it gave me an error (can't recall what the error code was).
-Then I decided to format my drive in order to get things to a clean state and go from there
-Finally I went to "Delete All Content and Settings" and proceeded to format the drive
-The system restarted and started with the format but at some point it froze. Now its stuck on a loop (Turn on > Format starts > Console freezes) that I can't seem to get out of...
Is there any way out of this? Anyway to tell the console to ignore the format command and do a regular boot?
D
Deleted User
Guest
Wii U tried to format HDD or you tried to do a system Format?
If you tried to format HDD, it shouldn't leave OS. Only System format needs to leave OS to do it's thing.
Similar threads
-
Xdqwerty
what are you looking at? -
Mondooooo
- S salazarcosplay
-
BakerMan
The snack that smiles back, Ballsack!
