Tutorial  Updated

Fixing system memory error 160-0103 (failing eMMC) without soldering | using redNAND with ISFShax

What is this for?



If you are encountering Error Code 160-0103 "There is a Problem with the system memory" or your Wii U is freezing at bootup or during Factory Reset it is likely that the eMMC Chip is failing.
This tutorial goes into fixing this Error 160-0103, by using the SD card in the front slot as replacement for the failing eMMC.
In this tutorial we will rebuild the MLC, which means it is empty, whithout your data. In the end I show how to salvage savegames from the failing eMMC.

Please note there are other possible causes for the 160-0103 error (like a CBHC brick). Also there are other possible solutions to this problem. To see if this Tutorial is right for you, check out the Ultimate Wii U Troubleshooting Guide

1690709917882.png


What this will do


We will first install ISFShax, which is an early exploit that runs before the operating system loads. This allows us to patch the OS to redirects the reads and writes, that normally go to the eMMC, to a partition on the SD card. So you will need to have the SD card in the Wii U to use it, as that is now it's new internal memory.
Also you need to keep the standby servcies (and with that the Quickstart menu) disabled as they don't work with ISFShax. (Your Wii U will hang once you turn it off till you remove power if standby services are enabled).
In this tutorial we are only redirecting the MLC. If you plan to try some dangerous things in the future, you can still mess up your system SLC and SLCCMPT. If you want to use this for such experiments consider using full redNAND, where all 3 devices get redirected.

Update


28.01.2024 - Wii VC games (from he eShop or VC Injects) now works from the redNAND internal memory. Keep in mind that Wii VC is more picky about the SD card. So far Sandisk cards worked for me, but Samsung cards didn't. If the card is incompatible, it will hang on a black screen after the silver Wii logo.

Choosing an SD card


I highly recommend to use an SD card, which is designed to sustain lots of writes, like Sandisk Max Endurance or at least High Endurance or Samsung Endurance. The absolute minimum size is 8GB using, 1,5GB for the FAT32 partition and the rest for the MLC partition, but it is recommend for the the card should have at least 16GB, so you can have at least 8GB for the MLC partition. The Maximum size of SD you can use is 2TB.

Since the Wii U Discs suffering from Disc rot and also for convenience, you probably want to dump all your Game Discs and install the Games from these Dumps You find detailed instructions on how to do that here: https://wiiu.hacks.guide/#/dump-games (do it after you completed this guide)
Later in that guidel you will create a second partition, which replaces the Internal Memory. You won't be able to resize that partition, without rebuilding again, so you better size everythng properly the first time.
The first partition is where all the Homebrew goes to and also where the dumps of the Wii U games go to. So this partition needs to have at least enough space to store your largest Wii U game with some extra space. If you want to use a USB Loader with vWii, you can also store the (OG) Wii games on the FAT32 partition.
The second partition (the MLC partition, which you format initally with NTFS) is where you install all your Wii U games (eShop and dumped Disc games, updates, DLC, saves...) to, including the VC Injectes. Also 5GB are used up by the Wii U system.
Make sure the the SD card can fi both these partitions.

Installing ISFShax


For installing ISFShax follow this tutorial: https://gbatemp.net/threads/how-to-set-up-isfshax.642258 but skip the "Autoboot" part for now.

Optional: Backing up savegames


If your Wii U can still run Tiramisu or Aroma: https://wiiu.hacks.guide/#/ you can use SaveMii to back up your save games.
If it can't you then you probably already used UDPIH to install ISFShax. Launch the recovery again using UDPIH and then use the Dump SLC + MLC option. Your SD card needs to have at least 64GB for that (for a 32GB console). You then need to merge mlc.bin.part files in the right order and can then extract the savegames using wfs-extract.

You can also backup your saves after setting up redNAND, even if your old system isn't booting anymore, see this post for more details: https://gbatemp.net/threads/fixing-...ing-rednand-with-isfshax.642268/post-10417998

If you lost the password to your NNID and can't recover it because the email doesn't exist anymore, you can transfer it. This is only a last resort option. If you still have the email address, it would be better to use the "Forgot Password" option now, as you won't have it on the new system.
There is also the option to use a password reset option on the PC. For that you need to create a Nintendo Account and then link the NNID to it. When linking it will ask for the password and give a reset option using the email.

Keep in mind this transfer only works on the same console and only if you don't do a Factory Reset.
To transfer the NNID It's enough to copy the account.dat file over.
You can use ftpiiu everywhere to save it to the PC for now. Just copy the whole /storage_mlc/usr/save/system/act/ folder to the PC. In that folder you find one subfolder for each user and in that subfolder you find an account.dat (it's a plain text file, you can open it with notepad). The folders are numbered in the order the users were created.

On the new rebuild mlc the numbering will start again with 80000001. If the user with the NNID had a larger number just create new users on the new system until you reach that number. Then you can copy the account.dat back and reboot.
After that you should be able to access the eShop and download the games again.


Partitioning the SD card


On Windows you need to use a third party tool like Minitool Partition Wizard or easeus, on Linux you can use gparted.
You need to have two primary partitions on the card:
  1. FAT32 - (in gparted set lba flag). This is what the PC will see and all your homebrew goes
  2. NTFS - This partition will be the MLC replacement, it should have at least 8GB. (don't assign a drive letter)
Shrink the existing FAT32 partition to make room and then create the NTFS partition after it. It's recommended to align the Partitions on 64MiB boundaries and use a multiple of 64MiB for the size. The MLC (NTFS) partition should be at least 8GB but other than that you can choose whatever sizes you like.

Configuring redNAND


Create a file minute/rednand.ini on the sdcard with the following content:
INI:
[partitions]
slccmpt=false
slc=false
mlc=true

[scfm]
disable=true
allow_sys=false

Rebuilding the MLC


  1. Download all the mlc system titles for your region from NUS. This can be done conveniently with MLCRestorerDownloader by @Xpl0itU. To use the MLCRestoreDownloader, you need to extract it and then copy the otp.bin from the SD card to it's directory. Then start the Downloader and select mlc and then your consoles region.
    You will get the output/MLC/{region} directory, which contains a directory for each title. In total there should be 52 titles totaling ~1.1GiB.
    If your console has an older firmware it might also be necessary to get the latest SLC titles.

  2. On the root of your SD card create a folder wafel_install. Then copy all 52 titles to the wafel_install folder, so it now contains the 52 subfolders, one for each title. If you want to reinstall / update SLC titles, you would also put them there.

  3. Put the wafel_setup_mlc.ipx on the SD card in /wiiu/ios_plugins.

  4. Select Patch (sd) and Boot ios redNAND in minute to start the setup of your fresh MLC.
    During the setup you won't see anything on the screen. You have to go by the power led.
    The power LED will flash blue, while it is installing the titles.
    if something goes wrong the LED will turn orange, but it will continue as long as it is blinking.
    The LED will become static once it finished. You can now power off the console.
    If the led is blinking red, something fatal happend. Ask for help.
    During the setup a short log gets written to the SD: wafel_setup_mlc.log.
    In the end it will enable the inital setup on the next boot.

  5. Remove the wafel_setup_mlc.ipx from /wiiu/ios_plugins on the SD.

  6. Select Patch (sd) and Boot ios redNAND again. If everything worked, the initial setup should launch.

  7. Follow through with the initial setup. After the "settings" part of the setup, it will drop you back into minute, just select Patch (sd) and Boot redNAND again. (no longer required with latest minute)
  8. (Optional) delete the wafel_install folder to free up space

Setting up autoboot


To automatically boot into redNAND create the file sd:/minute/minute.ini with the following content:
INI:
[boot]
autoboot=2
autoboot_timeout=1

Installing minute to SLC


If you haven't already installed minute (fw.img) to the SLC, you should do that now so In case the SD get's lost the Wii U displays at least the minute menu. Follow the "Booting without SD" section from the ISFShax tutorial for that. You only need to install the fw.img and can skip the ios_plugins part as you probably don't want to to boot the eMMC anyway.


Credits


  • smealum and WulfyStylez for redNAND
  • @shinyquagsire23 for minute, stroopwafel
  • @rw-r-r_0644 for finding and implementing isfshax
  • @GaryOderNichts and @QuarkTheAwesome for their direct contributions and help to the mlc setup
  • @V10lator for implementing Quota support and some improvements
  • @Xpl0itU for MLCRestorerDownloader
  • @vgmoose for all the support and for the Wii U that replaced the one Idestroyed during early isfshax testing
  • @Maschell for his help and all other contributions to the Wii U scene
  • @Lazr1026 for testing and some fixes
  • hexkyz for the warmboot boot1 exploit which made all of this possible
  • Salt Team for the original minute CFW
  • dimok789, FIX94 and others for the iosuhax CFW
  • fail0verflow for mini
  • and all other contributors to the Wii U scene!
 
Last edited by SDIO,

wapet1

Member
Newcomer
Joined
Oct 29, 2024
Messages
17
Trophies
0
Age
34
XP
28
Country
Korea, South
You could try without redNAND, by deleting SCFM.img and erasing the mlc and then run the setup without redNAND.
Also after the setup when you booted: did you try if it turns off again with the power button?
Else we would need to see what's going on. Either by making a plugin that forced it to write a crash log or by soldering a pico to the debug port to see it live
I tried 'Erase MLC,' and it was successful. However, when I tried 'Delete scfm.img,' it says 'Delete failed: -1.' Do you have any idea why this might be happening?
 

wapet1

Member
Newcomer
Joined
Oct 29, 2024
Messages
17
Trophies
0
Age
34
XP
28
Country
Korea, South
Maybe you shows already deleted it
hmmmm I've never delete any SLC... that might be the culprit of this whole issue ?
Post automatically merged:

LOL, I was so fed up with this issue that, before throwing away this junk Wii U, I decided to try everything I could think of. I deleted the MLC, and as I mentioned above, I tried to 'Delete scfm.img,' but it said 'Delete failed: -1.' After that, I removed ISFSHax, and of course, it got bricked with no display—LOL. So, I tried using UDPIH with the Pico, and now it won’t even let me get into the recovery menu with the purple light. It just makes the disc drive sound twice and shows a blue LED. Looks like the Wii U is totally fried now—I'm done.

Thank you for your help again. Even though I wasn’t able to fix this, I gained some insight into how the Wii U system works internally, thanks to your guidance. I really appreciate it!
 
Last edited by wapet1,

WoH

Member
Newcomer
Joined
Aug 29, 2015
Messages
9
Trophies
0
Age
29
XP
86
Country
Brazil
Hi everyone. I'm following this guide to fix a USA WiiU that freezes whenever I open any app. Every app, whether it's a app or system app, causes the WiiU to freeze (though the background music keeps playing normally). I'm trying to rebuild the MLC to see if this will bring the WiiU back to life.

I've followed all the instructions up to the "Rebuilding the MLC" part. I created two primary partitions on a 256GB SD card (FAT32 and NTFS), placed all the necessary files on the SD, and started "Patch (sd) and Boot ios redNAND."

However, my LED blinks blue continuously. I waited for 4 hours, but it just keeps blinking blue. I’ve tried again four times with the same result.

The log file shows the following:

OpenDir /vol/sdcard/wafel_install: 0 OpenMCP /vol/sdcard/wafel_install: 0 InstallInfo 000500301001010a: 00000000 Install 000500301001010a: 00000000 InstallInfo 000500301001110a: 00000000 Install 000500301001110a: 00000000 InstallInfo 000500301001210a: 00000000 Install 000500301001210a: 00000000 InstallInfo 000500301001310a: 00000000 Install 000500301001310a: 00000000 InstallInfo 000500301001410a: 00000000 Install 000500301001410a: 00000000 InstallInfo 000500301001510a: 00000000 Install 000500301001510a: 00000000 InstallInfo 000500301001610a: 00000000 Install 000500301001610a: 00000000 InstallInfo 000500301001710a: 00000000

Can someone help?
 

SDIO

Well-Known Member
OP
Member
Joined
Feb 13, 2023
Messages
3,057
Trophies
2
Age
29
XP
2,349
Country
Germany
LOL, I was so fed up with this issue that, before throwing away this junk Wii U, I decided to try everything I could think of. I deleted the MLC, and as I mentioned above, I tried to 'Delete scfm.img,' but it said 'Delete failed: -1.' After that, I removed ISFSHax, and of course, it got bricked with no display—LOL. So, I tried using UDPIH with the Pico, and now it won’t even let me get into the recovery menu with the purple light. It just makes the disc drive sound twice and shows a blue LED. Looks like the Wii U is totally fried now
Of yourse uninstalling ISFShax after erasing the MLC causes a full brick. To fix that you would need to defuse. That would also give you access to the live log, where you can see whats going on.

However, my LED blinks blue continuously. I waited for 4 hours, but it just keeps blinking blue. I’ve tried again four times with the same result.
Could be a bad a bad SD card. You can try reformatting the NTFS partition and try again. If that doesn't help I would suggest checking the sd card with h2wtest
 

alsochuckles

New Member
Newbie
Joined
Nov 26, 2024
Messages
1
Trophies
0
Age
41
XP
3
Country
Australia
Hoping to get some assistance on where to start. Successfully fixed the 160-0103 error using this guide but now i cannot successfully connect to any wifi accesspoint were i could previously. It sees the SSID and allows me to initiate the connection but when testing it fails. I have already tried using a different AP (my iphone's hotspot with compatibility on) but I get the same result.
Post automatically merged:

Hoping to get some assistance on where to start. Successfully fixed the 160-0103 error using this guide but now i cannot successfully connect to any wifi accesspoint were i could previously. It sees the SSID and allows me to initiate the connection but when testing it fails. I have already tried using a different AP (my iphone's hotspot with compatibility on) but I get the same result.
 

WoH

Member
Newcomer
Joined
Aug 29, 2015
Messages
9
Trophies
0
Age
29
XP
86
Country
Brazil
Of yourse uninstalling ISFShax after erasing the MLC causes a full brick. To fix that you would need to defuse. That would also give you access to the live log, where you can see whats going on.


Could be a bad a bad SD card. You can try reformatting the NTFS partition and try again. If that doesn't help I would suggest checking the sd card with h2wtest
Thanks for the reply.

I tried 3 more times. Same problem. Downloaded the MLC files again.

Log
OpenDir /vol/sdcard/wafel_install: 0 OpenMCP /vol/sdcard/wafel_install: 0 InstallInfo 0005001b1006c000: 00000000 Install 0005001b1006c000: 00000000 InstallInfo 0005001b10042300: 00000000 Install 0005001b10042300: 00000000 InstallInfo 0005001b10042400: 00000000 Install 0005001b10042400: 00000000 InstallInfo 0005001b10050000: 00000000 Install 0005001b10050000: 00000000 InstallInfo 0005001b10051000: 00000000 Install 0005001b10051000: 00000000 InstallInfo 0005001b10052000: 00000000 Install 0005001b10052000: 00000000 InstallInfo 0005001b10053000: 00000000 Install 0005001b10053000: 00000000 InstallInfo 0005001b10054000: 00000000 Install 0005001b10054000: 00000000 InstallInfo 0005001b10056000: 00000000 Install 0005001b10056000: 00000000 InstallInfo 0005001b10057000: 00000000 Install 0005001b10057000: 00000000 InstallInfo 0005001b10058000: 00000000 Install 0005001b10058000: 00000000 InstallInfo 0005001b10059100: 00000000 Install 0005001b10059100: 00000000 InstallInfo 0005001b10063000: 00000000 Install 0005001b10063000: 00000000 InstallInfo 0005001b10065000: 00000000 Install 0005001b10065000: 00000000 InstallInfo 0005001b10067100: 00000000 Install 0005001b10067100: 00000000 InstallInfo 0005001b10068000: 00000000 Install 0005001b10068000: 00000000 InstallInfo 0005001b10069100: 00000000 Install 0005001b10069100: 00000000 InstallInfo 000500101004a100: 00000000 Install 000500101004a100: 00000000 InstallInfo 000500101004b100: 00000000

I got a brand-new Lexar 256GB SD card, and it passed the HW2Test.
I formatted it using MiniTool Partition Wizard as follows:

  • 31.13 GB FAT32, Primary, Sectors per Cluster: 16 (8192 bytes)
  • 202.07 GB NTFS, Primary, Sectors per Cluster: 8 (4096 bytes)

    Is that correct?
I noticed that after starting the "Patch (SD) and Boot IOS redNAND" process, the system gets stuck in a loop, and when I force-shutdown the Wii U, the NTFS partition shows up as "Other" format in MiniTool Partition Wizard.

Is there another way to resolve this? Specifically, is there another way to rebuild IOS directly on the internal storage? My Wii U boots normally, but I can't open any game or app as the console freezes (though background audio keeps running).
 

SDIO

Well-Known Member
OP
Member
Joined
Feb 13, 2023
Messages
3,057
Trophies
2
Age
29
XP
2,349
Country
Germany
I noticed that after starting the "Patch (SD) and Boot IOS redNAND" process, the system gets stuck in a loop, and when I force-shutdown the Wii U, the NTFS partition shows up as "Other" format in MiniTool Partition Wizard.
That is how it is supposed to be, the Wii U formats it with its own wfs file system.

Rebuilding on internal storage works just the same, the only difference is that you don't boot rednand but the other option without redNAND. If you don't erase the MLC before that it will just install over it. If you erase the MLC before, it will do a fresh install.

But your problem could be something entirely different, so don't do that yet. If it freezes when trying to launch any app with the music still playing, that indicates a bad 2,4Ghz wifi module. It would also cause problems during the MLC rebuild. So I would say that is likely your problem.
Post automatically merged:

Hoping to get some assistance on where to start. Successfully fixed the 160-0103 error using this guide but now i cannot successfully connect to any wifi accesspoint were i could previously. It sees the SSID and allows me to initiate the connection but when testing it fails. I have already tried using a different AP (my iphone's hotspot with compatibility on) but I get the same result.
newer had that problem before. The wifi config is stored on the SLC in sys/proc/prefs/ in the NET*.xml files.
You could try deleting them via FTP or extract and restore the old ones from your SLC dump from before the rebuild.
Also be careful when messing with files on the SLC. It could cause a brick if you delete the wrong thing, but as long as you have a backup, it would be recoverable (just a little annoying).
 
Last edited by SDIO,

Dosnowin

Member
Newcomer
Joined
Dec 1, 2024
Messages
7
Trophies
0
Age
44
XP
27
Country
France
Hi all,
Thanks for the great Job writing this tutorial
I did all the tutorial on 3 different SD card and even original MLC but i always got same pb :
While setting up the Wii U juste after Wifi or sometimes after setting the mii name, i got a freeze
When i am lucky i can access to Wii menu but each time lauch a game, returning to wii menu will get me into freezing and an error.
Have you ever expérienced this behavior ? Have you an idea of how to soluce the pb ?
Thanks everyone for your help.
 

Dosnowin

Member
Newcomer
Joined
Dec 1, 2024
Messages
7
Trophies
0
Age
44
XP
27
Country
France
@WoH I think our problems sounds close no ?
Post automatically merged:

@SDIO I have just cleared Crashlog to get latest error
Before doing that i got 4 ligns of error. I thought tha clickink Display log would dump it on memory car but no.
So my log is cleared but i got a freezing with orange light after mii. I forced the reboot et asked for display grash log but it is virgin.
How can i Dump in a file the log ?
 
Last edited by Dosnowin,

Dosnowin

Member
Newcomer
Joined
Dec 1, 2024
Messages
7
Trophies
0
Age
44
XP
27
Country
France
I renamed it OLD.xx so it would not be recognized with keeping it on card
Post automatically merged:

This is a time when i managed to enter Menu wii, i ll put a game in it to see if a get a log while crashing
 

Dosnowin

Member
Newcomer
Joined
Dec 1, 2024
Messages
7
Trophies
0
Age
44
XP
27
Country
France
when i turn it off by pressing power on unit base, gamepad shut off but the fan of the base keeps functionning and wii U is blinking blue

I removed the file that was renamed.
I will launch a game hoping to get something written in log

UPDATE :
- After Launching a game i managed to return to menu without freezing wii but led is blinking orange.
- Wile trying a second disk i got a black screen with message error : 160-3204
- Nothing appears in crashLog
- Crash Log still empty but now rednand won t boot
Got the message frome minute ? :
no patch file 'ios.patch' stubbing
failed to open slc:/sys/title/00050010/1000400a/code/fw.img (5)
failed to launch ios with patches
 
Last edited by Dosnowin,

SDIO

Well-Known Member
OP
Member
Joined
Feb 13, 2023
Messages
3,057
Trophies
2
Age
29
XP
2,349
Country
Germany
You clearly still had the setup plugin as indicated by the blue and yellow blinking. Reinstalling everything while the system was running, was causing your instabilities. You seemingly also had the SLC titles in the wafel_install folder and the last time you turned it of, it was while it was reinstaling the OSv10, corrupting it in the process.

Format the MLC partition again to NTFS, to get rid of all corruption on the MLC that might have been caused by the repeated installs.
Since you corrupted the fw.img on the SLC, you now need to load it form the SD. For that extract it from your SLC.RAW backup. For That you can use the Wii U NAND Extractor: https://gbatemp.net/threads/release-wii-u-nand-tools.465386/ the fw.img is in sys/title/00050010/1000400a/code/fw.img. Rename it to ios_orig.img and put it on the SD.
The boot the Patch (sd) and boot sdmc:/ios_orig.img redNAND option.
Wait for the setup to finish, then turn the console off, delete the setup plugin and then you should hopefully be able to boot the normal redNAND option again.
 

Dosnowin

Member
Newcomer
Joined
Dec 1, 2024
Messages
7
Trophies
0
Age
44
XP
27
Country
France
Hi @SDIO ,

First thanks for you time and your answer. I followed your advices with minor changes, this is what i did.
- Instead of extracting the fm.img from SLC.Raw i decided to try to restore SLC from SLC.RAW
- I removed the SLC titles from wafel-install folder.
- I booted with option SD patch... Rednand
- I removed (and not renamed) the setup plugin file after led fixing blue

And all the procedure went perfectly well : no freeze...

Everything is functionning like it should. My Wii U is back without soldering anything.

THANK YOU !!!!!!!!!!!

Last question

Is it possible to modify/hack the rednand with same méthods as sysnand ? If i Want to install Homebrews can i follow tutorial for Sysnand or does it need modifications ?

Have a nice Day
 

neverendsDull

Well-Known Member
Member
Joined
Jan 22, 2023
Messages
211
Trophies
1
XP
436
Country
Antarctica
Hi SDIO, need your help here for a complicated issue, the process is a bit long so pls bear with me XD

One of my friends brought a Wii U with damaged NAND: blue indicator with no HDMI signal. UDPIH did not work so he turned to de_fuse and successfully made minute displayed and ISFShax installed.
But when trying to installing OS to rednand, the install process took too long with only blue flashing indicator. After around 15 min he forced power off and found the wafel_setup_mlc.log only contain 6 titles...

I told him about the issue I encountered on another console here, that you told me it is also possible the DDR memory is faulty, so he de-solder the DDR chips, bought new chips and soldered them on with different combinations and several times of installing OS to rednand, but the results are almost the same, OS installation never completed, blue indicator flashing forever:
Image_92635823657627.jpg

We refer the original 4 DDR chips as A B C D, he brought new chips, we refer them all as N.

1st install of rednand: A B C D (no memory changed): wafel_setup_mlc.log with 6 titles
2nd install of rednand: N N C D ( A and B changed): wafel_setup_mlc.log with aroud 20 titles
3nd install of rednand: N N A B ( A and B changed to C D position): wafel_setup_mlc.log with around 20 titles

3nd installation log attached FYR.

OpenDir /vol/sdcard/wafel_install: 0
OpenMCP /vol/sdcard/wafel_install: 0
InstallInfo 000500301001900a: 00000000
Install 000500301001900a: 00000000
InstallInfo 0005001b1004f000: 00000000
Install 0005001b1004f000: 00000000
InstallInfo 0005001b1005c000: 00000000
Install 0005001b1005c000: 00000000
InstallInfo 0005001b1005f000: 00000000
Install 0005001b1005f000: 00000000
InstallInfo 0005001b1006c000: 00000000
Install 0005001b1006c000: 00000000
InstallInfo 0005001b10042300: 00000000
Install 0005001b10042300: 00000000
InstallInfo 0005001b10042400: 00000000
Install 0005001b10042400: 00000000
InstallInfo 0005001b10050000: 00000000
Install 0005001b10050000: 00000000
InstallInfo 0005001b10051000: 00000000
Install 0005001b10051000: 00000000
InstallInfo 0005001b10052000: 00000000
Install 0005001b10052000: 00000000
InstallInfo 0005001b10053000: 00000000
Install 0005001b10053000: 00000000
InstallInfo 0005001b10054000: 00000000
Install 0005001b10054000: 00000000
InstallInfo 0005001b10056000: 00000000
Install 0005001b10056000: 00000000
InstallInfo 0005001b10057000: 00000000
Install 0005001b10057000: 00000000
InstallInfo 0005001b10058000: 00000000
Install 0005001b10058000: 00000000
InstallInfo 0005001b10059000: 00000000
Install 0005001b10059000: 00000000
InstallInfo 0005001b10063000: 00000000
Install 0005001b10063000: 00000000
InstallInfo 0005001b10065000: 00000000
Install 0005001b10065000: 00000000
InstallInfo 0005001b10067000: 00000000
Install 0005001b10067000: 00000000
InstallInfo 0005001b10068000: 00000000
Install 0005001b10068000: 00000000
InstallInfo 0005001b10069000: 00000000
Install 0005001b10069000: 00000000
InstallInfo 000500101004a000: 00000000

He has nand-aid on hand but has not tried it on this console yet.

SD card replaced, results are the same. He has two faulty consoles, the other one has been successfully revived using de_fuse+rednand. Obviously all these are the latest versions.

Is there any tips from you? Anything that he can try to further diagnose? As you can see he has gigs and skill to de solder memory chips so more "advanced" tricks is possible for him :) Thank you in advance.
 

SDIO

Well-Known Member
OP
Member
Joined
Feb 13, 2023
Messages
3,057
Trophies
2
Age
29
XP
2,349
Country
Germany
What do you see in the serial console from defuse happening when trying to to run the setup?
Did he check the wireless modules?
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: https://youtu.be/ZtNtSVIiitE?si=vQHuSAiWxlBVO3Yn