Stupid question maybe already answered but I'm not a tech guy. Is a bad nand chip completely replaceable with a better one and then rewrite everything to slc, new mmc etc using a previous full dump?
By default after power on the lines of the eMMC should be in open-drain mode so they won't interfere much if at all. Source:Can we tristate the eMMC on the Wii-U and/or make it go HI-Z so that we can leave it on the Wii-U?
GreatPretty sure the eMMC spec for what's in the Wii U tops out around 100MB/s, so anything is fine, really.
Limitted. Also pretty sure it's less than 100 MB/s (the chips might top out at that but the bus and stuff seems to be slower, more like around 26 MB/s).Would there be any potential speed increase in using a faster card, or is the console bandwidth limited?
Hm, well. Dumped my (Hynix) NAND to SD.
5 retries, which, sad.
Extracting it, I get this
View attachment 360698
Which doesn't seem too bad?
Dumped again just to make sure with a similar result.
i've finally extracted the logs. i actually did it both ways... anyway, not sure how best to identify issues there are a ton of logs to sort through.I meant the logs in the slc in /sys/logs. You can either extract them from the slc backup you did with the Wii U NAND Extractor or copy them from your Wii U with FTPiiU everywhere
That's what I thought. Good to know, I would go for the high endurance cards then. I just didn't want the system to get any slower than it already isLimitted. Also pretty sure it's less than 100 MB/s (the chips might top out at that but the bus and stuff seems to be slower, more like around 26 MB/s).
I think I have enough working Wii Us, I search for the broken ones. So thanky, but no, I don't need it at the moment.@SDIO I might have a spare WiiU if you need one for testing. Just let me know and I can send it over.
Yes, my whole post is about that. You can relace it either with another eMMC chip or and SD Card.Stupid question maybe already answered but I'm not a tech guy. Is a bad nand chip completely replaceable with a better one and then rewrite everything to slc, new mmc etc using a previous full dump?
The SDIO bus has a 4 bit data bus and the Wii U is running it at 52Mhz SDR. So you are limted to 26MB/s by the bus. You should focus more on the access time.If it comes to that and we need to replace the eMMC with an SD card, are there any read/write speed bottlenecks that should be taken into consideration?
I was looking at high endurance cards that can sustain many more writes from SanDisk and Samsung and both are about 100/30MB/s, are those fast enough?
5 retries sounds bad and it would worry me, but luckily it doesn't seem like files became corrupted. These files there are all db, so I assume they were just recently written and are still in the SLC cache. You can try to dump them through FTP to be totally sure, but I don't see a problem with the file system.Hm, well. Dumped my (Hynix) NAND to SD.
5 retries, which, sad.
Extracting it, I get this
View attachment 360698
Which doesn't seem too bad?
Dumped again just to make sure with a similar result.
Can transfer these just fine with FTP.
@Ferris1000 then you need to dump the eMMC through Hardware and replace it with an SD Card.
Post automatically merged:
you could try the recovery menu with udpih and see if the led turn purple, but I don't expect it to work
You can just dd to it. But if your cardreader supports it, you can run blkdiscard before on the card, so the controller can earase everything in advance. If the card is discarded before it might also make sense to skip FF blocks, but I think dd can only skip zeros. But I am not really sure if the hassle would be worth itAre there any preparations to do to the SD card, or do you just dd the mlc.bin you get from the dumper and that's that?
If your eMMC produces consistently read errors, it's perfect to test the error handling of my dumper code.I did do a second dump. The second dump also had 5 retries, but in a different spot.
You are the man. I can do this on a WiiU I have that crashes with 160-0103 on the setup when I go to create the Mii. Would this be helpful at all? I plan on doing the SD card Mod but dumping the eMMc was the most worrying part for me. This would help me out greatly.the eMMC you dump through the hardmod could still be good enough. I would recommend doing multiple dumps and compare them.
Without a NAND backup you just have to be super careful to not mess up the SLC cache.
I woudln't be suprised if we can get it to boot again to a error message and from there on we can use udpih to fix the broken files
Post automatically merged:
You can just dd to it. But if your cardreader supports it, you can run blkdiscard before on the card, so the controller can earase everything in advance. If the card is discarded before it might also make sense to skip FF blocks, but I think dd can only skip zeros. But I am not really sure if the hassle would be worth it
Post automatically merged:
If your eMMC produces consistently read errors, it's perfect to test the error handling of my dumper code.
It would be helpful for me, if you could run a dump with it and show me the output and the generated mlc.log.
Please don't trust the generated dump, but it would be good to see what wfs-extract thinks about it.
You need to run it through UPIH. It replaces the recovery menu.