Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,672,614
  • Replies Replies 17,052
  • Likes Likes 15
Pray forgive that even with search tools it's difficult to find things in a thread this large.
Confirms the suspicions, DE 62.
Apparently the two normal Pi Picos I have on hand are B2 and E6 6 so perhaps it's time to try horrible things.
 
That cap is way too damn small to be using as a permanent point though, going to have to find another option.
lite_33.jpg


P.S. the firmware preparations for triple-chip support are done (xiao, zero & RPI Pico), another kind of magic.
 
Wowwwwwwwwww

That was literally it. VCC must have been switching at that point, or maybe it was interrupting the 3.3V input to the SD card. That cap is way too damn small to be using as a permanent point though, going to have to find another option.

Thanks a bunch!
As a side note, 30AWG isn't small enough for this 0201 cap. Need like 36 or 40AWG from the looks of it. I broke the cap, but it isn't vital anyway. I took the cap off and then scratched off the solder resist on large power trace going to it, outlined below in red. This is much more secure than just using the cap, though also obviously more destructive. Certified "Works For Me" though.

sketch-1680350456458.png
 
@everyonesweird, it's been partially answered before

- multi-board support (RPi, xiao, zero, one) within the single fw
- OFW support fixes
- brick-proof firmware update through hekate
- sdloader power fixes, should also improve glitch
- maybe some glitch algo improvements
Post automatically merged:

Can i ask questions. can i uses IRH8342 instead of IRFSH8342 for the mosfet?
they are the same mosfets. third letter means its origin (manufacture)
 
After installing Piko, when I tried to dump the key, this happened. The OFW version is 16.0.1 for v2mariko. Did I do something wrong?
lockpick_rcm.png


The secure boot key was filled with 'f'... I thought I had been very careful about it :(



It seems to be normal behavior on V2 Mariko! :)
https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/page-189#post-10117261

This issue has been resolved. It was simply due to my lack of complete understanding, as I had not flashed the unlock.uf2 file. After flashing it, I was able to successfully dump the key again. Sorry for the trouble.
 
Last edited by handsom_tomato,
  • Like
Reactions: SkylerTakashi
It just mean your is poorly trained, mine boot like instantly.


View attachment 362432


View attachment 362433

View attachment 362434

How do you train the switch to boot faster?
Do you just keep reinstalling the firmware and have it train?

I installed a original sxlite in my oled and have been using spacecraft nx the second release (took almost an hour to train)
(the hwfly-nx firmwares did not seem to finish training even after a few hours).
My boot times can take between 30 sec to 2 minutes to get into hekate.
Very rarely it boots in a few seconds
 
  • Like
Reactions: Danook28
@everyonesweird, it's been partially answered before

- multi-board support (RPi, xiao, zero, one) within the single fw
- OFW support fixes
- brick-proof firmware update through hekate
- sdloader power fixes, should also improve glitch
- maybe some glitch algo improvements
U ARE THE MANN!!!!!!!
 
Can any one tell me wich type of nintendo switch better for pico and is better buy hwfly chip and oled or pico and nintendo switch v1 or v2... I can buy chips and console i love nintendo so much. Thank you ❤️
 
How do you train the switch to boot faster?
Do you just keep reinstalling the firmware and have it train?

I installed a original sxlite in my oled and have been using spacecraft nx the second release (took almost an hour to train)
(the hwfly-nx firmwares did not seem to finish training even after a few hours).
My boot times can take between 30 sec to 2 minutes to get into hekate.
Very rarely it boots in a few seconds

You can try to reset the chip so you boot into OFW, then the next reboot you will get the retraining.
 
  • Like
Reactions: Ricky_25
@everyonesweird, it's been partially answered before

- multi-board support (RPi, xiao, zero, one) within the single fw
- OFW support fixes
- brick-proof firmware update through hekate
- sdloader power fixes, should also improve glitch
- maybe some glitch algo improvements
Post automatically merged:


they are the same mosfets. third letter means its origin (manufacture)
Congratulations Sir, you are the winner of the Internet 2023 :bow:
 
After installing Piko, when I tried to dump the key, this happened. The OFW version is 16.0.1 for v2mariko. Did I do something wrong?View attachment 362496

The secure boot key was filled with 'f'... I thought I had been very careful about it :(
switch in version 16.x.x having this problem is not the first one I've seen :(
 
As of now, I have flashed the flash_nuke.uf2 and then fw_2.5_nw_toshiba_fix.uf2 before installing Piko. Therefore, I have not yet flashed unlock.uf2. The resistor is properly attached
 

Site & Scene News

Popular threads in this forum