Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,672,049
  • Replies Replies 17,052
  • Likes Likes 15
can i get a preview of the hekate image on the picofly chip? I see on YouTube there are people who install picofly. but the initial view is hekate. not a pico image
Thats already the default, you just need to put hekate files on sdcard root. Then rename the hekate**.bin file into payload.bin.
After that insert it into the switch and just press power button
 
  • Love
Reactions: impeeza
From the installation guide at https://gbatemp.net/download/a-definitive-picofly-install-guide.37968/download :

"If the LED flashes Red once, GREAT, you don't need to do anything special, however, if you see a single Green flash, then you need to permanently bridge the RGB jumper with solder on the rear of the RP2040"

Then the picture shows how to bridge GP25 to GND (not sure why the guide talks about a "RGB jumper", GP25 is not connected to anything on the RP2040 zero).

Anybody knows why? My guess would be that the firmware attempts to detect if it's running on a pi pico or not by checking GP25, which is connected to the onboard LED of the pi pico, but floating on the RP2040 zero.

Is it better to bridge it anyway, even if we get the red LED flash?
 
can i get a preview of the hekate image on the picofly chip? I see on YouTube there are people who install picofly. but the initial view is hekate. not a pico image
After you setup the SDCard the initial view is hekate.
You only get Pico logo when there is no sd present.
But really, what is a purpose of tricking someone that a different chip is installed?
I would understand wanting a TeamXecuter logo (as the original creators of mod), but HWFLY who basically made an exact copy of someone elses work....
 
i2c for Lite - tested
i2clite.jpg

Post automatically merged:

Did i mistakes on some step
wrong points
Post automatically merged:

Was the issue fix when you update sysnand ofw via online, and it reboots but instead of training and glitching into hekate, it will train and boot into ofw?
that is required for proper fuse burning. not a bug.
 
New firmware helped me to resolve the issue.
On old 2.67 the picofly shows green light and boot into OFW. I check rst point and cleaned and everything no fix. It always blue and then green and boot into OFW.

On new 2.7 firmware picofly gives the error =* which is Dat0 is not connected properly. New firmware is better to diagnose the situation.

if you're facing a issue on green light still don't find any problem. Try 2.7 to see what error it gives. But according to rehius this firmware is in alpha stage. So, do it at your own risk.

Thanks to Rehius for developing this new firmware.
 
Last edited by bilalhassan341,
  • Like
Reactions: Phantomas77
Hi all,

Could somebody give me some pointers?
I have done a shed load of lites, v1, v2 and oleds without issue using APU flex cables... however, tonight I thought I would have a stab at the mosfet thing on a V2 on 16.0.3...

It glitched and went white, then blue, the the usual green.
This time it just booted OFW???

It does the same thing everytime, no 'NO SD CARD' prompt at all.
Odd? Included photos...

I have followed the following diagram too...



Thanks,
Ant
take the kapton off like @lightninjay said then u will have cyan
shorten thos mosfet to apu cap wires and the issue will probally be solved, if that doesnt solve it check mosfet to cpu pin wire
 
New firmware helped me to resolve the issue.
On old 2.67 the picofly shows green light and boot into OFW. I check rst point and cleaned and everything no fix. It always blue and then green and boot into OFW.

On new 2.7 firmware picofly gives the error =* which is Dat0 is not connected properly. New firmware is better to diagnose the situation.

if you're facing a issue on green light still don't find any problem. Try 2.7 to see what error it gives. But according to rehius this firmware is in alpha stage. So, do it at your own risk.

Thanks to Rehius for developing this new firmware.
im waiting the official one
nice job
Rehius:grog::toot:
 
  • Like
Reactions: bilalhassan341
Hi guys, no one answered, I have a question about the use of installing the new firmware and the 2 cables, would that make all the switches work with a single mosfet?
 
People, I put the firmware 2.67 and the rp2040 turns on a red light, but on the same chip when I put version 2.70 the green light turns on, is that correct?
 
thanks rehius, I ask you, is the extra connection of 2 cables used so that now all the switches work with a single mosfet?
yes, with i2c connection single mosfet should be enough
actually it's a rare case, even without i2c single mosfet is usually working
 
Hello. I smoothly installed Picofly on a Lite. All is fine. Blue then green light with the forbidden fruit's no sd card logo. However, When I insert an SD card loaded with Hekate I get a black screen, it does not boot into Hekate. The SD card is working fine on OLED and inserting an empty SD card shows "failed to boot payload" I'm assuming both the SD card and slot are working, not sure what's the issue.
 
Hello. I smoothly installed Picofly on a Lite. All is fine. Blue then green light with the forbidden fruit's no sd card logo. However, When I insert an SD card loaded with Hekate I get a black screen, it does not boot into Hekate. The SD card is working fine on OLED and inserting an empty SD card shows "failed to boot payload" I'm assuming both the SD card and slot are working, not sure what's the issue.
Maybe it's related: https://gbatemp.net/threads/need-so...-hwfly-lite-installation.613354/post-10099766
 

Site & Scene News

Popular threads in this forum