wait...i thought that you were able to get into recovery mode!!! how did you do the update????
and then you said this:
Will a D3-2 drive read a burnt disc in recovery mode?
I have a friend who says he uninstalled priiloader. Not entirely sure how he went about doing this, but when he was done, all that comes up is the "system files corrupted" screen. Burnt an autoboot disc, but no success loading it in the Recovery Mode. His system menu was 4.1, so using a disc w/ 4.2 and recovery mode, I was able to update it. No change. Whatever he messed up wasn't overwritten by that update. I have a few questions...
Will a D3-2 drive read a burnt disc in recovery mode? Since I jumped the gun and ran the 4.2 update, would installing an older drive to run the autoboot recovery discs even work at this point? Do I have much of a chance updating to 4.3 and fixing it? Outside of Metroid and Black Ops, what discs offer 4.3? Does Mario All-Stars have 4.3 by any chance? (Don't have to rent it to try ) Other than finding a way to restore his nand via infectus, what other recovery options are there?
Maybe my terminology is off... I used the game cube controller in the P4 port to access the black screen w/ the system menu version in the corner (4.1 at the time, this is what I was referring to as recovery mode) and inserted a disc w/ 4.2 on it (a retail version of uDraw). I could hear the drive spin up so I just left it for a half hour or so. The Wii must have rebooted at some point, because when I came back the "System Files are Corrupted" message was on screen. I used the GC controller to access that 'recovery mode' screen again, and this time the version was reported as 4.2. Prior to doing the update w/ uDraw, I attempted to boot a burnt copy of Autobooting WadManager. The guide I found originally (none WiiHacks guide, shame on me) made no mention of needing a DriveKey to make it work, whereas anything I read here, says I do need a DriveKey to use the Autoboot Discs.
Do you think updating to 4.3 using this method would help at all? Trying to do this for my neighbour so he doesn't have to spend money Have the nand.bin and keys, but pretty certain boot2 isn't an option as its an LU72... Thanks for the info btw.
If updating to system menu 4.2 didn't work then updating to 4.3 won't work either. While I realize you said this happened while uninstalling Priiloader, a bad install/uninstall of Priiloader would result in a full brick which you don't have. That being said, it sounds more like a banner brick which cannot be fixed by updating the system menu.
At this point it looks like you have three possible fixes (two of them require either a modchip preset to autoboot or to have cioscorp previously installed):
1) Speed Demon Data management (requires modchip or cioscorp)
2) Fixing a banner brick with Wii Fit (requires modchip or cioscorp)
3) NAND Programming (must have bootmii backup)
You can find the guide for the first two options here Recovery menu Brick Fixing with SaveMiiFrii &autoboot disks Speed Demon Data Management is post #5 and Wii Fit fix is post #6 in the thread.
Since I updated from 4.1 to 4.2, does that mean I no longer have the Trucha Bug?
Probably not as in it doesn't mean that or probably not as in its gone? :P
I didn't do the mod myself, so I'm not sure which guide was used. Unfortunately, the original modder and the owner are both easily confused by technology and shouldn't be doing anything more than playing games on the system.