Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,658,809
  • Replies Replies 17,050
  • Likes Likes 15
IMO, I'd still double check everything around the APU and everything on the other side of the motherboard for the APU, visual\short test. Especially the caps, I don't see how a Lite-PFly install would mess up the APU BGA, so a reflow\reball wouldn't help.
Yep, did the visual and short test. Front side and back side showed nothing out of the ordinary. Went for a reball twice, still BSOD. Should have figured because the pressure test with fingers on the apu and ram should've showed normal boot with screen when turning it on but nothing...we hope....we hope. So, now I will be patient. Put this jumble to the side and will have to invest in a thermal cam and voltage injection tool. Might be a blessing in disguise. who knows. Still perplexed as to what it could be but I will find the flaw that I made.
 
Last edited by Takezo-San,
  • Sad
Reactions: LogicalMadness
View attachment 373070
Post automatically merged:


You might need to check this too. It seems power ic, but i still not confirmed it yet.
View attachment 373071
Post automatically merged:


For all rp2040, the procedure is the same. To flash the firmware, you need to press Boot button while power it up using cable.

I want to advise further but it seems you don't know about embedded device.
What i concern is, when the usb is connected to the pc, did the 3.3v from the board connected to the switch or not.
I do not know the effect when the 3.3v connected to the switch.
If the manufacturer doesn't give a clue or manual book about procedure to update the firmware.
If i were you, i will disconnect the 3.3v manually. Then do the update firmware as usual (press boot while inserting the usb cable to power it up).
I've done all cable connected except switch battery when doing rp2040 uf2 flash. The 3.3v won't do anything in that case.
 
View attachment 373070
Post automatically merged:


You might need to check this too. It seems power ic, but i still not confirmed it yet.
View attachment 373071
Post automatically merged:


For all rp2040, the procedure is the same. To flash the firmware, you need to press Boot button while power it up using cable.

I want to advise further but it seems you don't know about embedded device.
What i concern is, when the usb is connected to the pc, did the 3.3v from the board connected to the switch or not.
I do not know the effect when the 3.3v connected to the switch.
If the manufacturer doesn't give a clue or manual book about procedure to update the firmware.
If i were you, i will disconnect the 3.3v manually. Then do the update firmware as usual (press boot while inserting the usb cable to power it up).
Checked both Max chips' caps and resistors and they all were clear. This is super weird.
 
Does seem plausible. You reckon I should try a reflow on them two!?
There was also a post in some other thread, a guy with similar issue tried pushin down (quite hard) on RAM while booting and Switch booted OK. Afterward he did a reflow.
It might be worth trying with APU amd RAM just to see what happens
 
There was also a post in some other thread, a guy with similar issue tried pushin down (quite hard) on RAM while booting and Switch booted OK. Afterward he did a reflow.
It might be worth trying with APU amd RAM just to see what happens

Would that be caused be reflowing emmc and having the heat spread too far or depending on board go through from one side to rhe other?
 
Update: POC (Proof of Concept)

Modify the adapter little bit.
View attachment 373066

Shift it slightly to the right.
View attachment 373067

The diode value will not be different, when Dat1 Short Circuit (SC) with Dat0.
Its around 600.

When Dat1 SC with the Dat0 picofly will throws error:
=*== eMMC test failure - read failed

I've confirmed this and the picofly working until nosd shown (by shift the adapter a little bit to right).
I've been thinking about this, in other adapters the contact point protrudes more, so I would also trim the edge a bit like so. But maybe it's not needed.
 

Attachments

  • d0adapter_mod_1.jpg
    d0adapter_mod_1.jpg
    136 KB · Views: 67
Would that be caused be reflowing emmc and having the heat spread too far or depending on board go through from one side to rhe other?
In this case bsod happened because of pcb bending. I think that emmc is to far away for it to cause problem all the way to RAM during reflow but APU might be possible. Still, if you are applying heat on top of emmc and manage to break a connection on APU in the process that Emmc chip is probably dead already :D
 
  • Like
Reactions: Adran_Marit
In this case bsod happened because of pcb bending. I think that emmc is to far away for it to cause problem all the way to RAM during reflow but APU might be possible. Still, if you are applying heat on top of emmc and manage to break a connection on APU in the process that Emmc chip is probably dead already :D
I also have a Blue screen switch. I tried to reflow it and blue screen gone. It shows nintendo logo and then black screen. But it is making a buzzing sound coming from APU or RAM but speaker or fan is not connected so it is not from them. I'm also thinking about reflowing it again.

Edit: I throw my switch in a suitcase without case and we all know how the airport handle our bags😂😂😂. Lesson learned don't throw your switch without case. Because it can bend due to pressure😂😂🙂.
 
I also have a Blue screen switch. I tried to reflow it and blue screen gone. It shows nintendo logo and then black screen. But it is making a buzzing sound coming from APU or RAM but speaker or fan is not connected so it is not from them. I'm also thinking about reflowing it again.

Edit: I throw my switch in a suitcase without case and we all know how the airport handle our bags😂😂😂. Lesson learned don't throw your switch without case. Because it can bend due to pressure😂😂🙂.
For buzzin sound you should check the coils. I dont know which model you have but they look like this:
 

Attachments

  • Coil1.jpeg
    Coil1.jpeg
    85.5 KB · Views: 85
  • Coil2.jpg
    Coil2.jpg
    56.3 KB · Views: 65
Any docs or sources on how to build the payload? I'm referring to the one that's only present in header file payload.h as an array. I'd like to tweak the logo shown on boot when no SD card is inserted, maybe the Vol+ button behavior as well.
For fun, not for profit.

All I've been able to gather is that it's likely derived from sdloader in some way.
(edit: this thread is close but it applies to hwfly rather than Picofly)
 

Site & Scene News

Popular threads in this forum