Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,667,398
  • Replies Replies 17,052
  • Likes Likes 15
I'm sorry but what does that mean? The theory I have in mind is that the dat0 adaptor was shifted to another point and got shorted. I remember seeing @rehius says something like that.
But does that issue cause this error code? *=*?

Maybe the ultimate solution is to use this :
Post automatically merged:


Hello. Thanks for bing initiative.
Yes, no shorts.
Yes, it was removed. I even tried another.
Apprearny, the code is actually *=*. eMMC int failure which got mee to thinking that maybe the dat0 adaptor was shifted and got shorted. What do you think?
The code is *==
Here is your video in slow motion, you can check again
 

Attachments

  • SlowP.mp4
    7.3 MB
  • Like
Reactions: jkyoho
Can anyone help diagnose the flashing lights to help me fix.. I am not getting glitch. Flashing blue.. I thought it was supposed to be yellow.
Do you remember what fw on your rp2040? lower than 2.7 fw has blue blingking when glitching, and only 2.7+ fw has yelloe led for error code troubleshoot
 
The code is *==
Here is your video in slow motion, you can check again
Will diode test on dat0 still show up correct even if it’s shifted to the next spot over?
Post automatically merged:

Do you remember what fw on your rp2040? lower than 2.7 fw has blue blingking when glitching, and only 2.7+ fw has yelloe led for error code troubleshoot
I just grabbed the new firmware today. The one that was uploaded two days ago to GitHub… I was surprised to see blue.
 
Will diode test on dat0 still show up correct even if it’s shifted to the next spot over?
Post automatically merged:


I just grabbed the new firmware today. The one that was uploaded two days ago to GitHub… I was surprised to see blue.
I had the issue of shifted dat0 and it showed the correct diode value even though it was not in position.
 
Thanks. What do you think is the reason? CPU? eMMC?
I don't know. If it was emmc it would likely be blue, and there is no good reason for cpu to be dead.
I'm still thinking that the resistor on cmd could be the problem.
If you were soldering with 320° i'm afraid that it took longer then it should to solder that point. Could you try to replace that one with 4.7k or even bigger?
Post automatically merged:

Any chance you can help me figure out what high error I’m getting my eyes go crossed trying to figure it out. 🙏🏼😆
Nuke the pico, get the firmware from page 78 here, flash it again. Or get another pico and flash the firmware and lets see what happens
 
I don't know. If it was emmc it would likely be blue, and there is no good reason for cpu to be dead.
I'm still thinking that the resistor on cmd could be a problem.
If you were soldering with 320° i'm afraid that it took longer then it should to solder that point. Could you try to replace that one with 4.7k or even bigger?
Post automatically merged:


Nuke the pico, get the firmware from page 78 here, flash it again. Or get another pico and flash the firmware and lets see what happens
Blue flashing indicates possibly something wrong with firmware since it should be flashing yellow? I have about 5 pico on hand. I can flash another and wire it up to see. Will have to be tomorrow when I can get back to my shop. Thanks!
 
Hello,
Nothng on docking. Single led flash when docked.
value of CMD is 3.7k.
If there was something wrong with that resistor, shouldn't;t there be a purple scene?

This is my first installation with my new soldering station, Sugon A9. I did the job on 320C just to make sure I don't burn anything. Didn;t help apparently.
If I remember correctly, probably it's a good value. But...if you measure it on pcb then it is the resistance of the path all-around this CMD 4k7, not the resitance of the resitore itself (the other path has lower resistance so you cant measure it in this case).
 
Last edited by Takezo-San,
  • Like
Reactions: QuiTim
I don't know. If it was emmc it would likely be blue, and there is no good reason for cpu to be dead.
I'm still thinking that the resistor on cmd could be the problem.
If you were soldering with 320° i'm afraid that it took longer then it should to solder that point. Could you try to replace that one with 4.7k or even bigger?
Post automatically merged:


Nuke the pico, get the firmware from page 78 here, flash it again. Or get another pico and flash the firmware and lets see what happens
@FreeLander do you have the usb voltage tester? Did you check for voltage change/reset when connecting the charger?
 
Totally agree, waiting for this one to arrive.

View attachment 374919
What's the best way to go about fitting a wire underneath the emmc? I tried with 34 awg magnet wire but it was just a little too thick and raised the corner of the emmc.

Solder balls or paste?

I've just been practicing with donor boards and can consistently reball the emmc but not with a wire attached.
 
What's the best way to go about fitting a wire underneath the emmc? I tried with 34 awg magnet wire but it was just a little too thick and raised the corner of the emmc.

Solder balls or paste?

I've just been practicing with donor boards and can consistently reball the emmc but not with a wire attached.
flatten the wire with a hammer against somethings like a vice, then cut it to make sure the wire isn't too wide
Post automatically merged:

flatten the wire with a hammer against somethings like a vice, then cut it to make sure the wire isn't too wide
You should use uv soldermask to make sure the wire doesn't move. I would recomend clear soldermask, as some of the coloured soldermask doesn't cure all the way through, since it's meant to be applied in a very thin layer.
 
  • Like
Reactions: QuiTim

Site & Scene News

Popular threads in this forum