Hacking Hardware Picofly - a HWFLY switch modchip

[Minkaxy]

Seems like you source the 3.3v from a wrong point.

Thank for answer

In oled i use this point same as the picture in attachment.

V1,v2 too

Post automatically merged: Sep 3, 2023

- You should use 38-40awg, no need to use thicker wire.
- 47ohm and 100ohm, no 1000ohm (maybe it was a typo).
- Most of the dat0 are shit, so if you are not sure you got the right one this can be the main issue for most of the things.
- Flex is hit and miss at this point, you are better using bare mosfet.
Add to this flux residue, cold joints, posible shorts after shield placement, possible wrong sourcing of 3v3 and gnd (especially on Lite) and you got yourself the recepie for 99% of the issues you described.
Lets see after you upload pictures...

This is what i found on my phone but tomorrow I will take a new pic. And upload again.

 

[abal1000x]

Thank for answer

In oled i use this point same as the picture in attachment.

V1,v2 too

Thats correct.

Another 3.3v alt on v1
View attachment 391888

Post automatically merged: Sep 3, 2023

Thank for answer

In oled i use this point same as the picture in attachment.

V1,v2 too

Post automatically merged: Sep 3, 2023

This is what i found on my phone but tomorrow I will take a new pic. And upload again.

You might try this firmware to emmc init failure, after successfull glitch.
i change slightly the version to differentiate, v200.74.
Use it on your own risk. I am not responsible.
I might push the code to my github today, if you want to read it.
The change is i fixed the part when the rp2040 'shutdown' after the light code.

 

[Minkaxy]

Thats correct.

Another 3.3v alt on v1
View attachment 391888

Here is what i installed on v2.

 

[QuiTim]

Thank for answer

In oled i use this point same as the picture in attachment.

V1,v2 too

Post automatically merged: Sep 3, 2023

This is what i found on my phone but tomorrow I will take a new pic. And upload again.

These look good. The 3v3 point issue is mainly on Lite models

 

[abal1000x]

View attachment 391894

Here is what i installed on v2.

Yes thats already correct.

The 47ohms on Dat0 might throws emmc slow mode on v1.

 

[Minkaxy]

Thats correct.

Another 3.3v alt on v1
View attachment 391888

Post automatically merged: Sep 3, 2023

You might try this firmware to emmc init failure, after successfull glitch.
i change slightly the version to differentiate, v200.74.
Use it on your own risk. I am not responsible.
I might push the code to my github today, if you want to read it.
The change is i fixed the part when the rp2040 'shutdown' after the light code.

Thank you. I will try that I found sometime after turn off the nintendo switch rp2040 try to glitch and after successful glitch then nothing happened. Maybe your fw can help.

The emmc init failure that I found, I found shorted on the cap around emmc and I reball emmc and it fixed the issued.

I don’t know what is the cause to make it gone bad.

Try several things past 3 month and doesn’t seem to found out.

Post automatically merged: Sep 3, 2023

Yes thats already correct.

The 47ohms on Dat0 might throws emmc slow mode on v1.

Yes it is an old pic before you suggest to use 100 ohm resistor but every solder point is kinda same.

 

[abal1000x]

Thank you. I will try that I found sometime after turn off the nintendo switch rp2040 try to glitch and after successful glitch then nothing happened. Maybe your fw can help.

The emmc init failure that I found, I found shorted on the cap around emmc and I reball emmc and it fixed the issued.

I don’t know what is the cause to make it gone bad.

Try several things past 3 month and doesn’t seem to found out.

Thats firmware is for scenario:
When you successfull glitch and goes to hekate, then get the slow emmc problem, even though already put the 100 ohms on the dat0 and/or cmd.

The cause is because the rp2040 doesn't sleep (lowering the voltage, stopping the clock, etc).
Thats made the cmds/dat0 line interfered the communication between cpu and the emmc.
The best solution of course to turn off completely the rp2040 after successful glitch.
So the line is in high impedance, so its not interfering the communication.

 

[Minkaxy]

These look good. The 3v3 point issue is mainly on Lite models

yep, I done the blue screen on lite model several day ago and don’t seem what cause it but I suggest that my hand shake when solder the 3.3 point and maybe the cap gone bad or something

Post automatically merged: Sep 3, 2023

Thats firmware is for scenario:
When you successfull glitch and goes to hekate, then get the slow emmc problem, even though already put the 100 ohms on the dat0 and/or cmd.

The cause is because the rp2040 doesn't sleep (lowering the voltage, stopping the clock, etc).
Thats made the cmds/dat0 line interfered the communication between cpu and the emmc.
The best solution of course to turn off completely the rp2040 after successful glitch.
So the line is in high impedance, so its not interfering the communication.

And do you think it can cause the heat to make cpu or emmc to be broken.

Because most of the issued that I found is fixed by reflow the cpu.

 

[Tom8823]

Sorry if this has been discussed before but I installed my chip couple of months ago and I probably have old firmware on it but something weird happened to me today.

1. My switch was in sleep mode for couple of days until the battery was completely drained
2. I connected the charger and switch woke up to Hekate on itself upon connecting cable
3. While the charger was still connected I hit power off in hekate.
4. Switch was charging almost whole day and then without waking it up and checking battery level I assumed it has to be already 100% and I disconnected it from charger for the night.
5. Today I tried to turn it on, no reaction to power button
6. I panicked and connected charger, still no reaction to cable and power button.
7. Finally I held power button for 10 seconds and pressed power button shortly again to which switch finally turned on but battery level was only at 62%

What happened? Was this old firmware bug or something? Has this been ever identified? Sorry but since I installed my chip there is at least 200 more pages in this topic and asking will be faster

EDIT: Just checked, my firmware is at 2.67

 

[Minkaxy]

These look good. The 3v3 point issue is mainly on Lite models

This is oled installed
I think the solder point is correct.
3.3v is on the correct point.
But the issued I mention before still occur on many device that I installed rp2040.
Even instinct-nx I found the issued same.

Post automatically merged: Sep 4, 2023

Sorry if this has been discussed before but I installed my chip couple of months ago and I probably have old firmware on it but something weird happened to me today.

1. My switch was in sleep mode for couple of days until the battery was completely drained
2. I connected the charger and switch woke up to Hekate on itself upon connecting cable
3. While the charger was still connected I hit power off in hekate.
4. Switch was charging almost whole day and then without waking it up and checking battery level I assumed it has to be already 100% and I disconnected it from charger for the night.
5. Today I tried to turn it on, no reaction to power button
6. I panicked and connected charger, still no reaction to cable and power button.
7. Finally I held power button for 10 seconds and pressed power button shortly again to which switch finally turned on but battery level was only at 62%

What happened? Was this old firmware bug or something? Has this been ever identified? Sorry but since I installed my chip there is at least 200 more pages in this topic and asking will be faster

EDIT: Just checked, my firmware is at 2.67

It happened to me many time I don’t know how maybe the switch itself wakes up and got stuck at black screen then it drained the battery.

Have to force shutdown and turn it on again.

 

[Sunnyboy]

any mod builders in the netherlands ?

 

[abal1000x]

yep, I done the blue screen on lite model several day ago and don’t seem what cause it but I suggest that my hand shake when solder the 3.3 point and maybe the cap gone bad or something

Post automatically merged: Sep 3, 2023

And do you think it can cause the heat to make cpu or emmc to be broken.

Because most of the issued that I found is fixed by reflow the cpu.

The reflow cpu might because you mod the mosfet on the cpu.

I myself choose the safer one which is in the back pcb.

 

[FreeLander]

Man, the tiny Looks pretty neat. My only concern is the 100 ohms on dat0. I'm going to need to order these 0201. Other than that. I love it!

 

[Minkaxy]

The reflow cpu might because you mod the mosfet on the cpu.

I myself choose the safer one which is in the back pcb.

I will try the point on the back too.

This switch v1 I installed rp2040 three days ago everything works fine after first try then sleep and today cannot turn it on. Led says bad cpu or poor wiring.

I don’t know what went wrong now. Can you suggest anything on this motherboard.

 

[abal1000x]

I will try the point on the back too.

This switch v1 I installed rp2040 three days ago everything works fine after first try then sleep and today cannot turn it on. Led says bad cpu or poor wiring.

I don’t know what went wrong now. Can you suggest anything on this motherboard. View attachment 391972

The soldering looks good.
My cheap guess is the soldering on the mosfet not solid, hence the error (bad cpu / poor wiring). The firmware not detecting any glitch at all.




Out of topic:
I think this point is the safest one, since its big pad, so the soldering will be solid, and easy.
View attachment 391974

And the mosfet on the back pcb, easy to solder and less risky.
View attachment 391976

Post automatically merged: Sep 4, 2023

I will try the point on the back too.

This switch v1 I installed rp2040 three days ago everything works fine after first try then sleep and today cannot turn it on. Led says bad cpu or poor wiring.

I don’t know what went wrong now. Can you suggest anything on this motherboard. View attachment 391972
View attachment 391973

I just know that you update the picture with the mosfet.
You need to add kapton tape to that big blob of solder on the cap.
It might bridge with the cpu case.

 

[Minkaxy]

The soldering looks good.
My cheap guess is the soldering on the mosfet not solid, hence the error (bad cpu / poor wiring). The firmware not detecting any glitch at all.




Out of topic:
I think this point is the safest one, since its big pad, so the soldering will be solid, and easy.
View attachment 391974

And the mosfet on the back pcb, easy to solder and less risky.
View attachment 391976

Thank for reply. then I should switch to use the mosfet and see If it solve the problem.
suspect the flex cable is a bad guy in my case.

 

[abal1000x]

Thank for reply. then I should switch to use the mosfet and see If it solve the problem.
suspect the flex cable is a bad guy in my case.

That big blob of solder might bridging with the cpu case.
Try to turn it on like that or add kapton tape before closing the cpu case.

 

[Minkaxy]

That big blob of solder might bridging with the cpu case.
Try to turn it on like that or add kapton tape before closing the cpu case.

Same,

reflow the cpu and everything back to normal now.

ok, let add the kapton tape then.

 

[abal1000x]

Same,

reflow the cpu and everything back to normal now.

Thats weird.
I've already assume that our behaviour is different each other.
Like chef, every of us has their own way to solder.

I've suspect that someone might solder it hot enough to melt the bga pin under it.


What is the temperature you use when solder the cap, and in average how long you heat the solder.

For me usually 350 degrees Celsius, and the touch usually i limit it to 3s maxed 5s.

 

[Minkaxy]

Same,

reflow the cpu and everything back to normal now.

Thats weird.
I've already assume that our behaviour is different each other.
Like chef, every of us has their own way to solder.

I've suspect that someone might solder it hot enough to melt the bga pin under it.


What is the temperature you use when solder the cap, and in average how long you heat the solder.

For me usually 350 degrees Celsius, and the touch usually i limit it to 3s maxed 5s.

300 degrees and 3s to 5s same.

I used to installed with sx, hwfly before and all of it work fine.
but after the instinct-nx chip came out and I try it, this issued happen.
and now I switch to use rp2040 the issued is still happen.

so I doubt maybe myself did something wrong but I don't know, try to inspect myself and every solder point and try another tools, wire. the problem still the same.

Maybe the solder point on the cpu bridge with the plate, I will try to add kapton tape there.