Hacking Hardware Picofly - a HWFLY switch modchip

[Hassal]

Been dealing with a OLED that stopped working after a week. Reballed the eMMC and ran a permanent wire and it boots to OFW with no issues.
Installed the zero and hekate boots fine but not ofw. Ok, no problem - add extra resistors to Dat0 and CMD. Now when trying to boot OFW, I get a 2002-3539 error right away. Removed the chip and ofw boots fine.
Any ideas what the issue might be? Read it could be the dat0 so I ran a new wire just in case but no dice.

Your OFW isn't okay. Do a system recovery and see if that help.

 

[bvang913]

Thank you. One more question.

Is it possible that we will have to update or change the file we put into rp2040 in the future? How will this process be done since we have removed the USB port?

You can always update using picofly toolbox.

 

[LuigiGad]

Today I had a new mishap, fortunately it ended well. I ask you what you think. Erista switch, rp2040-zero, 47x2.47x2.47. Everything ok, hekate boots, eMMC no problem, original boot ok. I create Emunand and I have error never seen before. I replace the microSD, nothing. I do the benckmark and freeza hekate. in original it starts and I have no errors. I eventually replace RP2040 and fix it. I lost 3 hours... What could it be?

 

[karatefeet]

Your OFW isn't okay. Do a system recovery and see if that help.

Do you mean do a factory reset? I tried that and was able to boot into OFW so put it all back together only to have it now hang at the Nintendo Switch screen.

 

[deeps]

Thank you. One more question.

Is it possible that we will have to update or change the file we put into rp2040 in the future? How will this process be done since we have removed the USB port?

you can update with the picofly toolbox payload. just download the update.bin for the new version, put it in the root of the sd card, launch picofly toolbox from hekate, and press update

 

[BlueBeans]

Not to be a dick or anything, but this IS covered in the guide.

I only ask because I’ve done dozens of them and have never encountered this before.

Not to be a dick or anything, but this IS covered in the guide.

the resistors didn’t e

I've seen this with a few cowboy fixes I've had to do.
The DAT0 is sitting partially on DAT1, with the crappy OATO adaptors the silk screen is either off center, or the DAT0 pin connector is a 'C' kind of look and not a 'u'... sometimes the C connection touches the side of DAT1.

I'd pull it, move it over to the right a mm or so (as you're facing the emmc from the switch's pcb edge) so it's touching a no connection ball under the emmc next to DAT0.

That usually sorts it.
Seeing slow mode is usually bad news and a few power ons/offs away from a corrupted emmc.

I had to fix a few by restoring a dummy emmc.
Pain in the butt.

EDIT: I've also never had to double up on any resistors on a mod still and no come backs.
It's usually a bad wiring joint.
I know it's a pain, but go through all connections and buzz them all out or redo them all, it will be something not quite right.



Ant

so it didn’t end up being the resistors or the emmc. The CMD resistor on the board took a dump. Changed that and it’s up and running.

 

[naldo29]

'your emmc is initialized in slower mode."

That means that I need to add more resistors right?
What could happen is i ignored the message and let it be?

 

[Hassal]

Do you mean do a factory reset? I tried that and was able to boot into OFW so put it all back together only to have it now hang at the Nintendo Switch screen.

Whenever you have an issue with OFW you should always check your partition table if still intact because a lot of times something can get corrupted for whatever reason. You can identify if your OFW is intact by making an emuNAND, if you have the same trouble there then your issue lies in your eMMC.

 

[LuigiGad]

'your emmc is initialized in slower mode."

That means that I need to add more resistors right?
What could happen is i ignored the message and let it be?

there is little to ignore with a message like this... if you boot in the original way there are 2 possibilities, either it doesn't start at all giving you an error, or it starts but on the home page you have an error with code...

 

[twins333]

Today I had a new mishap, fortunately it ended well. I ask you what you think. Erista switch, rp2040-zero, 47x2.47x2.47. Everything ok, hekate boots, eMMC no problem, original boot ok. I create Emunand and I have error never seen before. I replace the microSD, nothing. I do the benckmark and freeza hekate. in original it starts and I have no errors. I eventually replace RP2040 and fix it. I lost 3 hours... What could it be?

Bad or cheap sd-card? try to get one of the recommended brands.

 

[LuigiGad]

Bad or cheap sd-card? try to get one of the recommended brands.

I only use quality microSD like Samsung evo and if the customer always supplies it with quality like Kingston or Sandisk. However I changed 3 of them, still the same problem, so the microSD wasn't the problem.

 

[naldo29]

there is little to ignore with a message like this... if you boot in the original way there are 2 possibilities, either it doesn't start at all giving you an error, or it starts but on the home page you have an error with code...

yeah, thats whats weird. Everything looks normal. Like nothing is acting out of place or behaving glitchy or slow at all. Could it because mine is an erista model? anyways how would i go by fixing this issue?

 

[Hassal]

Today I had a new mishap, fortunately it ended well. I ask you what you think. Erista switch, rp2040-zero, 47x2.47x2.47. Everything ok, hekate boots, eMMC no problem, original boot ok. I create Emunand and I have error never seen before. I replace the microSD, nothing. I do the benckmark and freeza hekate. in original it starts and I have no errors. I eventually replace RP2040 and fix it. I lost 3 hours... What could it be?

In Nyx configuration

bpmpclock=1    0: Auto, 1: Fastest, 2: Faster, 3: Fast. Use 2 or 3 if Nyx hangs or some functions like UMS/Backup Verification fail.

 

[LuigiGad]

In Nyx configuration

bpmpclock=1    0: Auto, 1: Fastest, 2: Faster, 3: Fast. Use 2 or 3 if Nyx hangs or some functions like UMS/Backup Verification fail.

The problem isn't just that on-screen error, many times Hekate freezes. Why did everything work out by changing Modchip?
anyway thanks, I didn't know this one

Post automatically merged: Nov 16, 2023

yeah, thats whats weird. Everything looks normal. Like nothing is acting out of place or behaving glitchy or slow at all. Could it because mine is an erista model? anyways how would i go by fixing this issue?

On all the Erista I double the resistance on DAT and CMD. 47ohm*2 otherwise I have that problem

 

[QuiTim]

The problem isn't just that on-screen error, many times Hekate freezes. Why did everything work out by changing Modchip?
anyway thanks, I didn't know this one

Post automatically merged: Nov 16, 2023

On all the Erista I double the resistance on DAT and CMD. 47ohm*2 otherwise I have that problem

I fully agree here. From all the ones I did, I only needed to add additional resistors 2-3 times and they were all Eristas.
But nowdays I follow @deeps route and I do 100+100+47 all the time, I haven't encountred that error since.

 

[abal1000x]

Today I had a new mishap, fortunately it ended well. I ask you what you think. Erista switch, rp2040-zero, 47x2.47x2.47. Everything ok, hekate boots, eMMC no problem, original boot ok. I create Emunand and I have error never seen before. I replace the microSD, nothing. I do the benckmark and freeza hekate. in original it starts and I have no errors. I eventually replace RP2040 and fix it. I lost 3 hours... What could it be?

Do you install the same firmware version on both rp2040?
Theres issue on previous version, on powering down the rp2040.

 

[karatefeet]

Whenever you have an issue with OFW you should always check your partition table if still intact because a lot of times something can get corrupted for whatever reason. You can identify if your OFW is intact by making an emuNAND, if you have the same trouble there then your issue lies in your eMMC.

Last night I restored the eMMC from backup via hekate and no improvement - still doesn’t go past the Nintendo switch logo when booting ofw.

Just tried created the emuNand successfully so hopefully can rule out the eMMC and my reballing.

The eMMC is a sk Hynix so I’m going to try installing an Instinct chip next.

 

[jacobtc]

double 47 works too. i do 100/100/47 on all my switches.

Do you have a picture? How do you fit that many resistors? I have two Erista's with some weird error, one has a EMMC slow error, and the other, Atmosphere just errors out, or doesn't boot. Booting to OFW seems to work fine on both.

EDIT: Also, wouldn't a 240ohm resistor do the same as 100/100/47?

 

[naldo29]

I fully agree here. From all the ones I did, I only needed to add additional resistors 2-3 times and they were all Eristas.
But nowdays I follow @deeps route and I do 100+100+47 all the time, I haven't encountred that error since.

quick question, what is deeps whole route? like what else does he do differently other than this?

 

[QuiTim]

Do you have a picture? How do you fit that many resistors? I have two Erista's with some weird error, one has a EMMC slow error, and the other, Atmosphere just errors out, or doesn't boot. Booting to OFW seems to work fine on both.

EDIT: Also, wouldn't a 240ohm resistor do the same as 100/100/47?

What he is saying/doing is that he uses single 100ohm resistor on dat0, single 100ohm on CMD, and single 47ohm on CLK. So 3 resistors in total, same as always just different values so it's not a single 240ohm resistor.

Post automatically merged: Nov 16, 2023

quick question, what is deeps whole route? like what else does he do differently other than this?

Nothing else as far as I remember, he is just good at what he does and I think that after encountering this slow emmc error a couple of times he started using 100/100/47 as default and never had any issues with this setup.