Error code 105-1505

  • Thread starter Thread starter Mewiimii
  • Start date Start date
  • Views Views 2,817
  • Replies Replies 28
you can use udpih and the recovery_menu to dump logs. Then we can se e what's going on.

EDIT: If you have an SD in or a usb device connected remove that and see if it changes something
 
you can use udpih and the recovery_menu to dump logs. Then we can se e what's going on.

EDIT: If you have an SD in or a usb device connected remove that and see if it changes something
I am a new member so I'm not supposed to post links, but the logs are in this zip file.
 
I see corruption on the slc and the mlc. But the mlc one is whats currently causing your problem. But I can't tell if it is a hardware problem or just corrupted data. I wiuld suggest you do a full nand dump and watch out for errors during the dump.

EDIT: looked at the slc error in more detail and now I understand what was happening: Data in the slc was corrupting and it was a page used by scfm. IOSU gave up on some point on recovering the data in the slc. So now the data returned by the scfm was bad. That's why we are now seeing DATA CORRUPTION on the mlc, without MEDIA ERRORs. So the eMMC is probably fine, but the slc might be failing.

So I still suggest doing the full backup and then we take a look at the slc image to see if there is more corruption, There is no easy way to replace the SLC, so if it is failing the only solution I would see would be redNAND or really replacing it for a similar chip, if you find one. But maybe you are lucky and this is just a one of error
 
Last edited by SDIO,
I see corruption on the slc and the mlc. But the mlc one is whats currently causing your problem. But I can't tell if it is a hardware problem or just corrupted data. I wiuld suggest you do a full nand dump and watch out for errors during the dump.

EDIT: looked at the slc error in more detail and now I understand what was happening: Data in the slc was corrupting and it was a page used by scfm. IOSU gave up on some point on recovering the data in the slc. So now the data returned by the scfm was bad. That's why we are now seeing DATA CORRUPTION on the mlc, without MEDIA ERRORs. So the eMMC is probably fine, but the slc might be failing.

So I still suggest doing the full backup and then we take a look at the slc image to see if there is more corruption, There is no easy way to replace the SLC, so if it is failing the only solution I would see would be redNAND or really replacing it for a similar chip, if you find one. But maybe you are lucky and this is just a one of error
On Voultar's "Wii-U NAND-AID - eMMC Recovery and Replacement Interposer Public Test" post, page 7, Skawo describes 3 ways to dump the Nand. I don't understand what to do with the file from his link or how to dump the nand via UDPIH. Is dumping the OTP + SEEPROM what I am looking for or do I need to do somthing with Skawo's file? Do I need to hard mod and dump with de_fuse or emmc reader?

edit: figured it out, gonna dump the memory tonight.
 
Last edited by Mewiimii,
first dump otp + seeprom, then slc + mlc and then remove power from the console and only turn it on again, after we decided what the next steps are
 
first dump otp + seeprom, then slc + mlc and then remove power from the console and only turn it on again, after we decided what the next steps are
Alright, dumped all of that. Got lots of errors on the SLC dump. No errors for the MLC.
 
If you used the recovery to dump, then SLC errors are expected.

EDIT: I can't do anything with the SLC dump, without the otp.bin
 
Are you sure that is the right otp from the same console? I am getting a lot of hmac errors, indicating the key in the otp.bin is not matching the slc.bin
 
Are you sure that is the right otp from the same console? I am getting a lot of hmac errors, indicating the key in the otp.bin is not matching the slc.bin
I only have one Wii u. I may have restarted the console in between the SLC+MLC and the opt dump. I can't remember.
 
I may have restarted the console in between the SLC+MLC and the opt dump
The OTP doesn't change, that shouldn't be a problem.

Maybe try dumping the otp again and compare, maybe something went wrong. If it is the same, dump the slc again.
Post automatically merged:

Oh wait, I was stupid. The recovery doesn't dump the ECC info, that's why it gave me the errors.
I will have a look later gain, you don't have to dump again.
Post automatically merged:

@Mewiimii I made a new release for you: https://github.com/jan-hofmeier/recovery_menu/releases/tag/v0.5.0-2
I added an "SLC Checker" option. Please run that and show the slc_checker.txt log
 
Last edited by SDIO,
Ok, so we have no other slc corruption, so this migt be a one off thing.
I suggest you also run the MLC Checker to see if there is more corruption on the MLC caused by scfm. If that is just this one folder, I would suggest we just rename it using the wupclient:
Code:
w.mv('/vol/storage_mlc01/usr/save/system/nim/nup','/vol/storage_mlc01/usr/save/system/nim/corrupted-nup')
(See step 8 here: https://gbatemp.net/threads/using-n...emmc-fix-160-0103-system-memory-error.636361/)
Please keep in mind, you can't do a factory reset, because it would hang, when it tries to delete ths corrpted folder. The only way to get truly rid of it, is a complete format and reinstall of the mlc: https://gbatemp.net/threads/how-to-upgrading-rebuilding-wii-u-internal-memory-mlc.636309/ So probably not worth is. Just don't do a factory reset.
 
Ok, so we have no other slc corruption, so this migt be a one off thing.
I suggest you also run the MLC Checker to see if there is more corruption on the MLC caused by scfm. If that is just this one folder, I would suggest we just rename it using the wupclient:
Code:
w.mv('/vol/storage_mlc01/usr/save/system/nim/nup','/vol/storage_mlc01/usr/save/system/nim/corrupted-nup')
(See step 8 here: https://gbatemp.net/threads/using-n...emmc-fix-160-0103-system-memory-error.636361/)
Please keep in mind, you can't do a factory reset, because it would hang, when it tries to delete ths corrpted folder. The only way to get truly rid of it, is a complete format and reinstall of the mlc: https://gbatemp.net/threads/how-to-upgrading-rebuilding-wii-u-internal-memory-mlc.636309/ So probably not worth is. Just don't do a factory reset.
Checked the MLC. I only got the one error. I got an error on the wupclient.
"moving /vol/storage_mlc01/usr/save/system/nim/nup to /vol/storage_mlc01/usr/save/system/nim/corrupted-nup failed : 0xfffcffe5"
 
Then try renaming the nim folder
What is the command?

edit: I figured out what you were trying to say,
"moved /vol/storage_mlc01/usr/save/system/nim/ to /vol/storage_mlc01/usr/save/system/corupted-nim/"
is the console good to boot?
 
Last edited by Mewiimii,

Site & Scene News

Popular threads in this forum