Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,687,023
  • Replies Replies 17,052
  • Likes Likes 15
Try to remove the chip and test the switches. Black screen is something else. Is it booting to ofw? @.@
balck screen too on ofw but i remove the tiny and install the original rp and all work fine... i think these chips are bad but can 'i do something to recover them ?
Post automatically merged:

I use waveshaee rp2040 tiny chip, all is working. Check if you have an original rp2040 tiny and not a clone.
it work with the last pico fw too ?
 
balck screen too on ofw but i remove the tiny and install the original rp and all work fine... i think these chips are bad but can 'i do something to recover them ?
Post automatically merged:


it work with the last pico fw too ?

Check the resistors if they are 47ohms. The 3 resistors nearby pin 27 28 29.

And yes, the latest pico fw is working for the waveshare variant. Im using 2.75 for all my modding.
 
  • Love
Reactions: chronoss
ok but can i change them if no good resistors ? i think these are very tiny for desolder :(

To desolder them is easy. Just cover them in a blob of low melt solder. Just make sure not to bridge any of the nearby pin of rp2040.

After just add 47ohm on the pin header 27 28 29. Dont forget to bridge the resistor pads though otherwise you wont have continuity.
 
  • Love
Reactions: chronoss
Those all have continuity. 1 to 1 and 1-2. 3 had an ohms reading of 14. #3 was solder.
Post automatically merged:

I’m curious though. Source and drain are being connected to ground points on the apu. The caps we connect to is the ground side.
Post automatically merged:

Point 3 is not soldered to the shield like it looks. Was just sitting on top.
Post automatically merged:

There has been progress. Someone suggested to me about pulling a mosfet from a v1 flex and it worked the first time! Idk if maybe I got a bad batch of mosfet but I’ll be either ordering more or ordering some of the ones from the v1 flex. Here are the mosfets if anyone is interested.

https://www.lcsc.com/mobile/product-detail/MOSFETs_NATLINEAR-NP2016DR-N-G_C2991144.html
Its happen to me today 😭
Ordered 10pcs mosfet irh8342 from my local shop
And none of it working
I ussually use aon6414a and its working fine
I just concern about the size, thats why i try my luck use irh8342
I try single mosfet and double mosfet and its not working
When i try to switch to aon6414a its working fine
Im really sure this mosfet is defect or something
 

Attachments

  • IMG_4366.jpeg
    IMG_4366.jpeg
    4.2 MB · Views: 63
To desolder them is easy. Just cover them in a blob of low melt solder. Just make sure not to bridge any of the nearby pin of rp2040.

After just add 47ohm on the pin header 27 28 29. Dont forget to bridge the resistor pads though otherwise you wont have continuity.
Ok thanks, i will make some test !!!
 
Can u show me the resistor on the chip please....???
i can't read the schematics :(
Unfortunately i dont have the clone tiny.
You might track the DIN track of the LED using microscope.
Or just randomly check with multitester any resistor that connect with the DIN pin of the led.
 
Can u show me the resistor on the chip please....???
i can't read the schematics :(
It will be this if its following the same schematic as the waveshare one. Just measure. The line is going through gpio16
 

Attachments

  • Screenshot_20231221_165506_Samsung Internet.jpg
    Screenshot_20231221_165506_Samsung Internet.jpg
    1.1 MB · Views: 60
Its happen to me today 😭
Ordered 10pcs mosfet irh8342 from my local shop
And none of it working
I ussually use aon6414a and its working fine
I just concern about the size, thats why i try my luck use irh8342
I try single mosfet and double mosfet and its not working
When i try to switch to aon6414a its working fine
Im really sure this mosfet is defect or something
Yeah mine definitely ended up being the mosfet. Although the ones I ended up ordering on Amazon tended to be super sensitive. Had to replace 2. I think they’re just hit or miss. I’m not sure.
 
Does anyone know the value of the resistor near the cmd one??
Switch OLED
 

Attachments

  • Screenshot_2023-12-21-15-47-58-449_cn.wps.xiaomi.abroad.lite-edit.jpg
    Screenshot_2023-12-21-15-47-58-449_cn.wps.xiaomi.abroad.lite-edit.jpg
    540.3 KB · Views: 67
Picofly does not glitch with rebuild nand(original prodinfo present) but boots into ofw.

Error code:

Picofly FW 2.75 short long short
Picofly FW 2.76 long short long short


-The installed picofly glitch to hekate with corrupt nand.
-The picofly glitch to hekate with empty emmc.
-The picofly(including same flex) glitches fine in another switch where the original nand is present.

-NOT SURE: i might be remembering wrong but the picofly glitches to hekate with rebuild nand WITHOUT original prodinfo present.

I use @sthetix tutorial. I asked him what the issue could be but he unfortunately told me, that he doesn't use picofly.

Do you guys think that this is fixable by FW update for picofly?

Edit: tested with hwfly: same behavior.
 
Last edited by k28,
Picofly does not glitch with rebuild nand(original prodinfo present) but boots into ofw.

Error code:

Picofly FW 2.75 short long short
Picofly FW 2.76 long short long short


-The installed picofly glitch to hekate with corrupt nand.
-The picofly glitch to hekate with empty emmc.
-The picofly(including same flex) glitches fine in another switch where the original nand is present.

-NOT SURE: i might be remembering wrong but the picofly glitches to hekate with rebuild nand WITHOUT original prodinfo present.

I use @sthetix tutorial. I asked him what the issue could be but he unfortunately told me, that he doesn't use picofly.

Do you guys think that this is fixable by FW update for picofly?
I am in another problem with rebuild nand. I can get in hekate but can not boot into ofw with rebuild nand using sthetix rebuild lv3. My switch just flashing nintendo logo then shut off. May i ask you which burnt fuse your console are on?
Post automatically merged:

Picofly does not glitch with rebuild nand(original prodinfo present) but boots into ofw.

Error code:

Picofly FW 2.75 short long short
Picofly FW 2.76 long short long short


-The installed picofly glitch to hekate with corrupt nand.
-The picofly glitch to hekate with empty emmc.
-The picofly(including same flex) glitches fine in another switch where the original nand is present.

-NOT SURE: i might be remembering wrong but the picofly glitches to hekate with rebuild nand WITHOUT original prodinfo present.

I use @sthetix tutorial. I asked him what the issue could be but he unfortunately told me, that he doesn't use picofly.

Do you guys think that this is fixable by FW update for picofly?
And don't ever ask that guy using the term"picofly" again. The hating that dude giving to picofly is ridiculous.
 
I am in another problem with rebuild nand. I can get in hekate but can not boot into ofw with rebuild nand using sthetix rebuild lv3. My switch just flashing nintendo logo then shut off. May i ask you which burnt fuse your console are on?
Post automatically merged:


And don't ever ask that guy using the term"picofly" again. The hating that dude giving to picofly is ridiculous.
Probably because fw 17 rebuild nand issue. Running atmosphere once should fix the problem. It works because atmosspere includes a fix for this issue. But you might want to check if there is a Methode without launching atmosphere because you may be flagged for a ban...

Edit: why does he hate picofly? xD
 
  • Like
Reactions: superxoi
Probably because fw 17 rebuild nand issue. Running atmosphere once should fix the problem. It works because atmosspere includes a fix for this issue. But you might want to check if there is a Methode without launching atmosphere because you may be flagged for a ban...
Yeah my burn fuse is 19 so the one i can do is 17.0+ . i did every step sthetix showed on youtube but the switch just flashing nintendo logo then shut off. Don't know what to do next. I bought the mainboard which emmc being damaged already so banning have no effect on it anyway.
 

Site & Scene News

Popular threads in this forum