Modded switch won't boot

[impy101]

I got a modded V2 here that refuses to boot. Hekate boots up fine, so that means the modchip and the wiring is all fine, but as soon as I try to launch emummc or even reboot to OFW it won't do anything. It just hangs there on a black screen.

I thought it could be a bad emmc, but I did a benchmark and it passed.

When I boot using Launch -> sysnand I get an error saying unknown pkg1 version hos version not supported.

I've never had this before. Anyone have any idea what's wrong?

 

[Deleted member 681324]

Need more context, but sounds like conflicting versions of Atmosphere and hekate.

 

[impy101]

Need more context, but sounds like conflicting versions of Atmosphere and hekate.

Both are latest versions

Post automatically merged: Oct 16, 2024

Besides, it doesn't even boot in OFW. Even when I disconnect the modchip to boot directly to OFW it does nothing..

 

[vLTD]

What versions are your OFW and CFW?

 

[impy101]

What versions are your OFW and CFW?

Not the latest, but they are both the same version. I can't check since the switch won't both to either..

 

[Deleted member 681324]

Like I said, you're missing context... why touch the chip if it's working correctly? When did the switch get modded? Was it ever working correctly? What changed from working to not?

 

[impy101]

Like I said, you're missing context... why touch the chip if it's working correctly? When did the switch get modded? Was it ever working correctly? What changed from working to not?

Quite a while back. It was working fine. I don't know what changed to be honest..

 

[Deleted member 681324]

Hmm, vague you are. Dishonest, you must be.

I still believe you have conflicting Atmosphere and/or hekate version files within themselves. Best get updated versions from git

 

[randy_w]

if you can't do reboot - ofw, then it's probably a problem with the modchip/ribbon cable. I've seen many poorly designed rp2040 chips that would cause interference on emmc data lanes and stops console from booting or even cause emmc corruption.

First go to emmc info and make sure the gpp partition table is good. Try to remove the emmc module from the modchip and connect it to motherboard directly, see if the console boots to ofw

 

[impy101]

if you can't do reboot - ofw, then it's probably a problem with the modchip/ribbon cable. I've seen many poorly designed rp2040 chips that would cause interference on emmc data lanes and stops console from booting or even cause emmc corruption.

First go to emmc info and make sure the gpp partition table is good. Try to remove the emmc module from the modchip and connect it to motherboard directly, see if the console boots to ofw

I have the Picofly installation method. Not the HWFly with the ribbon cable etc.

Post automatically merged: Oct 16, 2024

View attachment 465271
Hmm, vague you are. Dishonest, you must be.

I still believe you have conflicting Atmosphere and/or hekate version files within themselves. Best get updated versions from git

Not possible. If that was the problem then the switch would've worked and booted to OFW when I disconnected the modchip and the MicroSD card.

 

[Deleted member 681324]

You're right, sorry... I fixated on no CFW boot.

 

[randy_w]

I have the Picofly installation method. Not the HWFly with the ribbon cable etc.

Might as well post a picture cause i don't know what chip you are using. There are many revisions of picofly/rp2040 chips, some are like sx core/hwfly core that clips to the emmc connector, some require soldering to motherboard/emmc module like hwfly oled/instinct v6. You said you are using a v2 so i assume it's something like sx core.

Anyway since you can't boot to ofw with everything disconnected your emmc might be corrupt, restore your backup if you made one