Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,691,347
  • Replies Replies 17,052
  • Likes Likes 15

Attachments

  • IMG_20230821_132043.jpg
    IMG_20230821_132043.jpg
    1.3 MB · Views: 62
Guys. I am in a serious situation. I have a Switch V1 and i want it to mod chipped. I sent my switch to someone who know how to fix / install picofly but today he sent me a picture
IMG-20230821-WA0051.jpg

showing the error 2002-3539 with the remarks that the health of the sysnad is critical so it is giving this error. Also told me that emunand is working fine but sysnand is not working properly. Whats should i do??
 
How many did u buy and what did u pay for I would like to get 1 or 2 off of u to see what the issue is with them
Post automatically merged:


"Normally"
They should also work
Bought 5 and including delivery and tax cost $30.
 
Guys. I am in a serious situation. I have a Switch V1 and i want it to mod chipped. I sent my switch to someone who know how to fix / install picofly but today he sent me a picture
View attachment 389486
showing the error 2002-3539 with the remarks that the health of the sysnad is critical so it is giving this error. Also told me that emunand is working fine but sysnand is not working properly. Whats should i do??

he needs to use 100 ohm resistors for dat0+cmd. or add another 47 ohm for a total of 94 ohm.
 
Another permanent dat0 drilling method.
Samsung s23 ultra photos.
 

Attachments

  • Screenshot_20230821_213029_Gallery.jpg
    Screenshot_20230821_213029_Gallery.jpg
    1.8 MB · Views: 70
  • Screenshot_20230821_213035_Gallery.jpg
    Screenshot_20230821_213035_Gallery.jpg
    2 MB · Views: 74
  • Screenshot_20230821_213047_Gallery.jpg
    Screenshot_20230821_213047_Gallery.jpg
    609.3 KB · Views: 69
  • Screenshot_20230821_213051_Gallery.jpg
    Screenshot_20230821_213051_Gallery.jpg
    656.9 KB · Views: 78
  • Screenshot_20230821_213055_Gallery.jpg
    Screenshot_20230821_213055_Gallery.jpg
    577.8 KB · Views: 81
  • Screenshot_20230821_213059_Gallery.jpg
    Screenshot_20230821_213059_Gallery.jpg
    668.6 KB · Views: 70
  • Screenshot_20230821_213112_Gallery.jpg
    Screenshot_20230821_213112_Gallery.jpg
    2 MB · Views: 74
  • Screenshot_20230821_213107_Gallery.jpg
    Screenshot_20230821_213107_Gallery.jpg
    754.7 KB · Views: 73
  • Screenshot_20230821_213103_Gallery.jpg
    Screenshot_20230821_213103_Gallery.jpg
    640.4 KB · Views: 80
  • Screenshot_20230821_213118_Gallery.jpg
    Screenshot_20230821_213118_Gallery.jpg
    2.1 MB · Views: 77
  • Screenshot_20230821_213123_Gallery.jpg
    Screenshot_20230821_213123_Gallery.jpg
    666.8 KB · Views: 75
  • Screenshot_20230821_213128_Gallery.jpg
    Screenshot_20230821_213128_Gallery.jpg
    726.8 KB · Views: 83
  • Screenshot_20230821_213133_Gallery.jpg
    Screenshot_20230821_213133_Gallery.jpg
    2 MB · Views: 67
Update on OLED - I had a V2 with a normal rp2040 and swapped that out and put it on the oled and the oled tiny rp2040 into the v2. The v2 trained and glitched instantly (like normal). The OLED however, also gave the same =*== code and boots into ofw. So i definitley did something wrong. I reballed fine (by hand). That all went smooth. The only thing i can think of is the clk resistor. Because I did knock it when exposing the clk point. Not sure if got damaged but it gave a reading of 666ohms. Anyone know what reading it should be? Thinking of replacing that, maybe that resistor is damaged internally and not allowing the emmc check to go through and read? Not sure, any ideas? Atleast the tinys are legit, so theres that. yay. but the oled is still booting into ofw. noooooo.
 
  • Like
Reactions: twins333 and QuiTim
Update on OLED - I had a V2 with a normal rp2040 and swapped that out and put it on the oled and the oled tiny rp2040 into the v2. The v2 trained and glitched instantly (like normal). The OLED however, also gave the same =*== code and boots into ofw. So i definitley did something wrong. I reballed fine (by hand). That all went smooth. The only thing i can think of is the clk resistor. Because I did knock it when exposing the clk point. Not sure if got damaged but it gave a reading of 666ohms. Anyone know what reading it should be? Thinking of replacing that, maybe that resistor is damaged internally and not allowing the emmc check to go through and read? Not sure, any ideas? Atleast the tinys are legit, so theres that. yay. but the oled is still booting into ofw. noooooo.

clk resistor? u mean the resistor next to the clk ?


if u mean the resistor next to clk line then its 100ohm
 
Last edited by Dee87,
  • Like
Reactions: QuiTim
Update on OLED - I had a V2 with a normal rp2040 and swapped that out and put it on the oled and the oled tiny rp2040 into the v2. The v2 trained and glitched instantly (like normal). The OLED however, also gave the same =*== code and boots into ofw. So i definitley did something wrong. I reballed fine (by hand). That all went smooth. The only thing i can think of is the clk resistor. Because I did knock it when exposing the clk point. Not sure if got damaged but it gave a reading of 666ohms. Anyone know what reading it should be? Thinking of replacing that, maybe that resistor is damaged internally and not allowing the emmc check to go through and read? Not sure, any ideas? Atleast the tinys are legit, so theres that. yay. but the oled is still booting into ofw. noooooo.
I dont think there is any CLK resistor unless you talking about this 100 ohm one next to the CLK trace
1692653784292.png
 
  • Like
Reactions: QuiTim and Dee87
I dont think there is any CLK resistor unless you talking about this 100 ohm one next to the CLK trace
View attachment 389587
yep sorry, i meant the resistor near the clk point. So I tried measuring it but it wouldn't settle on a value. Set my dmm to 200hm mode and it shows readings of 45ohm. Then taking my probe on and off it would show 167ohm. sometimes 115ohm and then 87ohm. But never settles and just flashes these readings not staying on screen. Not sure whats going on here. I just hope it isn't a trace repair job. then im screwed. If it is this resistor, then i can change it no probs. Any idea on if its this resistor or not guys?
Also whats the function of that resistor? Linked to what exactly?
 
Last edited by Takezo-San,
yep sorry, i meant the resistor near the clk point. So I tried measuring it but it wouldn't settle on a value. Set my dmm to 200hm mode and it shows readings of 45ohm. Then taking my probe on and off it would show 167ohm. sometimes 115ohm and then 87ohm. But never settles and just flashes these readings not staying on screen. Not sure whats going on here. I just hope it isn't a trace repair job. then im screwed. If it is this resistor, then i can change it no probs. Any idea on if its this resistor or not guys?
Also whats the function of that resistor? Linked to what exactly?

Check ur batteries from ur dmm if it fluctuates so much.

Otherwise change it with a 100ohm resistor then ull see if it works.
Check if u ripped a trace ifso try to fix.

No clue what its for sorry.
 

Site & Scene News

Popular threads in this forum