Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,676,939
  • Replies Replies 17,052
  • Likes Likes 15
The only thing i can say, it works fine with Mariko (with few exceptions).

I can't say who is bEhind the development, but Right now I wonder is thiS the only Thing they cAn do... ;)
you telling you know stuff, so... hwfly can boot atmosphere but can't boot other most of the other OS like Linux distros. My question is: picofly is limited to Atmosphere or it will boot linux?
 
you telling you know stuff, so... hwfly can boot atmosphere but can't boot other most of the other OS like Linux distros. My question is: picofly is limited to Atmosphere or it will boot linux?
Just like sxos and the hwfly, these modchips are exclusively for atmosphere.
For booting the linux kernel, you would need to change the code that is injected.
But nobody is interested in running Linux on a Switch.
Not even Android is interesting enough.
 
you telling you know stuff, so... hwfly can boot atmosphere but can't boot other most of the other OS like Linux distros. My question is: picofly is limited to Atmosphere or it will boot linux?
Lol
Hwfly boots Hekate, and hekate can boot all other distros.
Picofly boot hekate 🤯
More is not needed 😉
 
Lol
Hwfly boots Hekate, and hekate can boot all other distros.
Picofly boot hekate 🤯
More is not needed 😉
While that's true, before booting in to Hekate a chain loader payload is ran from the NAND first. The chip just glitches the Switch in to running that instead of the official bootloader and then the chain loader runs Hekate. Because the chain loader runs before Hekate it has to do some hardware initialization stuff which can only be done once per boot. If done incorrectly the Linux kernel can't boot. Afaik from what I've been told by people doing hw research on the Switch the current chip firmwares (Spacecraft, HWFly-NX) all initialize the hardware incorrectly so HOS can boot but booting non-HOS firmwares is impossible. This can be fixed by replacing the chain loader on the NAND but then if the chip reflashes the NAND for whatever reason it will revert to being unable to boot Linux. The chip itself needs to contain an updated chain loading payload.
 
Ok so for those of you just tuning in here. It seems the code is already out in the wolf. You just need to install a boot loader / chain loader into your .uf2

Full src or just the beta that’s been floating around?

You mean we can throw on something like argon-nx and just go?
 
Beta? Naw it’s way past that and likely already out there you’d just need to put your little chain loader converted from binary and into the .uf2 code package. Allegedly.
Post automatically merged:

I haven’t had this much fun since … will someone mod my mf oled yesterday
 
  • Like
Reactions: peteruk
Do you think it's so easy to replace the bootloader? The main code is encrypted, as is the bootloader code. I think you can put your bootloader in emmc через hekate? Will the chip load a custom bootloader in the switch?
 
  • Like
Reactions: Xavier91ns
Ok so for those of you just tuning in here. It seems the code is already out in the wolf. You just need to install a boot loader / chain loader into your .uf2
Yall mean the china code that was leaked a few days ago and generated this discussion or did new code release in which case where is the source?
 
While that's true, before booting in to Hekate a chain loader payload is ran from the NAND first. The chip just glitches the Switch in to running that instead of the official bootloader and then the chain loader runs Hekate. Because the chain loader runs before Hekate it has to do some hardware initialization stuff which can only be done once per boot. If done incorrectly the Linux kernel can't boot. Afaik from what I've been told by people doing hw research on the Switch the current chip firmwares (Spacecraft, HWFly-NX) all initialize the hardware incorrectly so HOS can boot but booting non-HOS firmwares is impossible. This can be fixed by replacing the chain loader on the NAND but then if the chip reflashes the NAND for whatever reason it will revert to being unable to boot Linux. The chip itself needs to contain an updated chain loading payload.
For ELI5 purposes...

What @CompSciOrBust is talking about(chain loader payload) is the sdloader.enc from hwfly-nx firmware. It is inserted directly in the boot0 partition. Spacecraft-NX doesn't provide a sdloader.enc file because the firmware of the modchip writes to it instead when some conditions are met(ie. it doesn't detect the modified chainloader in boot0)

:)
 
Lol
Hwfly boots Hekate, and hekate can boot all other distros.
Picofly boot hekate 🤯
More is not needed 😉
Exactly, I'm like "what are these bozos talkin about" lol
Wish there was a better place of discussion for PikoFly that was for people a little more on the 'up n up'

(I thought I recognized your name too, haven't peaked in the server in a while but you're the NAND guy, hope everything's been well :grog:)
 
  • Like
Reactions: evil_santa
Exactly, I'm like "what are these bozos talkin about" lol
Wish there was a better place of discussion for PikoFly that was for people a little more on the 'up n up'

(I thought I recognized your name too, haven't peaked in the server in a while but you're the NAND guy, hope everything's been well :grog:)
Excuse me but no. I got this.
 
Exactly, I'm like "what are these bozos talkin about" lol
Wish there was a better place of discussion for PikoFly that was for people a little more on the 'up n up'

(I thought I recognized your name too, haven't peaked in the server in a while but you're the NAND guy, hope everything's been well :grog:)
Spoiler he's evil ;)

Just waiting for all the stuff to happen
 
  • Like
Reactions: Girtana1

Site & Scene News

Popular threads in this forum