SOLVED - Had to replace RST resistor and change the CMD and DAT0 resistors on my picofly for 100 ohm resistors
I've installed picofly on a 2019 model switch. It seemed to work smoothly, only to realize that while performing the backups it started popping out warnings about emmc being in slow mode. Usually it does it right at the start, but this time it was after it had finished doing the backups. Luckily i do at least have full emmc backups as it did manage to finish, as now I've got a really big issue.
I poked around the resistors and replaced the ones near the solder points, knowing of the dreaded CMD resistor problem on the oled switch. But the issue wouldn't go away, sometimes failing to glitch altogether. I realized that as long as the modchip wires were soldered, even if I removed the 3v3 wire to prevent the chip from working, it would prevent booting to OFW. Removed the modchip, and it started working again... until it didn't: decided to leave it in sleep mode for a while and check on it occasionally, by the fourth time I checked it actually had turned off; and now it doesn't turn back on at all.
Any idea what could be happening? I suspect there might be something still occasionally causing the emmc to only work in slow mode and making the console unable to function properly. I tried using another emmc chip (working) to see if that too would initialize in slow mode, and it does! So the issue is definitely on the motherboard. Sometimes it would give me 2002-3539 errors, or the modchip would output *=* or ** error codes. They are "No eMMC block 0 read (eMMC init failure?)", and "RST is not connected" respectively. RST is very much connected however.
It does charge and takes 15V @ ~0.5A both ways.
Please help me, haha. While I can afford to replace this for the person who asked me to perform the mod, I really would rather not. Please don't shame me for working on someone else's device, I have a lot of experience with this stuff, I wasn't negligent. I must just have f*ed up somewhere, as it happens to everyone... or maybe I was just very unlucky.
I've installed picofly on a 2019 model switch. It seemed to work smoothly, only to realize that while performing the backups it started popping out warnings about emmc being in slow mode. Usually it does it right at the start, but this time it was after it had finished doing the backups. Luckily i do at least have full emmc backups as it did manage to finish, as now I've got a really big issue.
I poked around the resistors and replaced the ones near the solder points, knowing of the dreaded CMD resistor problem on the oled switch. But the issue wouldn't go away, sometimes failing to glitch altogether. I realized that as long as the modchip wires were soldered, even if I removed the 3v3 wire to prevent the chip from working, it would prevent booting to OFW. Removed the modchip, and it started working again... until it didn't: decided to leave it in sleep mode for a while and check on it occasionally, by the fourth time I checked it actually had turned off; and now it doesn't turn back on at all.
Any idea what could be happening? I suspect there might be something still occasionally causing the emmc to only work in slow mode and making the console unable to function properly. I tried using another emmc chip (working) to see if that too would initialize in slow mode, and it does! So the issue is definitely on the motherboard. Sometimes it would give me 2002-3539 errors, or the modchip would output *=* or ** error codes. They are "No eMMC block 0 read (eMMC init failure?)", and "RST is not connected" respectively. RST is very much connected however.
It does charge and takes 15V @ ~0.5A both ways.
Please help me, haha. While I can afford to replace this for the person who asked me to perform the mod, I really would rather not. Please don't shame me for working on someone else's device, I have a lot of experience with this stuff, I wasn't negligent. I must just have f*ed up somewhere, as it happens to everyone... or maybe I was just very unlucky.
Last edited by Karichi1919,
