You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using redNAND, wudump works up to the point where "Done!" is printed to the screen after the user selects what device to dump to. After that nothing else happens, and the system must be hard reset to get it working again.
Disabling redNAND, and running wudump from sysNAND allows wudump to work normally. Given that, I'm assuming that redNAND has broken fatInitDefault(). As that is the next thing to occur in wudump's code after "Done!" is printed. I'm not sure if it can be worked around in wudump if fatInitDefault() is broken in redNAND, but I figured I'd post this here just in case someone runs into the same issue.
The text was updated successfully, but these errors were encountered:
this is indeed an issue I know of since v1.0 and I cant really do a whole lot against that because of code overlapping with disc patches used in wudump itself, so all I can really say is to just not use rednand for wudump, there is no point in doing so anyways luckily.
When using redNAND, wudump works up to the point where "Done!" is printed to the screen after the user selects what device to dump to. After that nothing else happens, and the system must be hard reset to get it working again.
Disabling redNAND, and running wudump from sysNAND allows wudump to work normally. Given that, I'm assuming that redNAND has broken fatInitDefault(). As that is the next thing to occur in wudump's code after "Done!" is printed. I'm not sure if it can be worked around in wudump if fatInitDefault() is broken in redNAND, but I figured I'd post this here just in case someone runs into the same issue.
The text was updated successfully, but these errors were encountered: