Hacking Hardware Picofly - a HWFLY switch modchip

  • Thread starter Thread starter mathew77
  • Start date Start date
  • Views Views 3,681,761
  • Replies Replies 17,052
  • Likes Likes 15
Looks like hardware issue then. Could it be the battery is old and worn?
In hekate panel it shows correct value of capacity so probably no :( Do you guys have maybe idea of using different power rail? If yes which one you think can be turned off when standby
 
  • Like
Reactions: estm13
In hekate panel it shows correct value of capacity so probably no :( Do you guys have maybe idea of using different power rail? If yes which one you think can be turned off when standby
I read yesterday in another thread on GBATempm that somewhere around FW19 / FW20 Nintendo broke something in the software that also causes a battery drain when the Switch is in sleep mode.
So maybe this is a software issue rather than a hardware issue.
 
I read yesterday in another thread on GBATempm that somewhere around FW19 / FW20 Nintendo broke something in the software that also causes a battery drain when the Switch is in sleep mode.
So maybe this is a software issue rather than a hardware issue.
If it were that issue, it wouldn't happen while airplane mode is on.
 

Attachments

  • IMG_3667.jpeg
    IMG_3667.jpeg
    2.2 MB · Views: 42
Just the quick update: finally I detached modchip completely, and issue still persist. So I guess that's not picofly connected
 
Hi guys, I got a quick and simple question. I got Mariko with dead APU and I already bought reballed used APU over ebay. I haven't soldered it yet as I realized it won't work. My question is will it work if I do some kind of hardware hack as you're talking here about? Thanks!
 
Hi guys, I got a quick and simple question. I got Mariko with dead APU and I already bought reballed used APU over ebay. I haven't soldered it yet as I realized it won't work. My question is will it work if I do some kind of hardware hack as you're talking here about? Thanks!
The encryption of the NAND/emmc is tied to the keys in the APU.
There were some threads in the past about rebuilding the NAND with a donor NAND image from another Switch.
It was mentioned that the OFW will therefore never be able to connect to the Nintendo servers.
But you should be able to get the CFW going.
So all that remains is the pirate life for this Switch. *harharhar*
 
The encryption of the NAND/emmc is tied to the keys in the APU.
There were some threads in the past about rebuilding the NAND with a donor NAND image from another Switch.
It was mentioned that the OFW will therefore never be able to connect to the Nintendo servers.
But you should be able to get the CFW going.
So all that remains is the pirate life for this Switch. *harharhar*
I cannot rebuild NAND image because I don't have donor NAND, I just bought APU itself. So that's not problem if I want to use CFW or rebuilding NAND is mandatory? If I solder APU properly
and nothing else has gone bad I can run CFW but I need to do hardware mode as well? What exactly do I need? Can you point me please?
 
Someone correct me if I'm wrong but if you get the APU running, you should be able to dump the NAND that is present in Switch.
Hekate should boot because the BOOT0/BOOT1 partitions are not encrypted with the console keys.
 
Someone correct me if I'm wrong but if you get the APU running, you should be able to dump the NAND that is present in Switch.
Hekate should boot because the BOOT0/BOOT1 partitions are not encrypted with the console keys.
that is true. you should be able to rebuild the nand with generic keys that the console will accept. obviously you cannot get online anymore, but the console will work. I think sthethix has a guide for that. if you have a donor console, you can get the keys and use those. or you can picofly the current console/nand and see if you can extract the keys from there. good luck!
 
You must follow the level 3 guide of Stethix. Even if you have nothing, if the hardware works, you can get it back up and running without online services.
 
Last edited by LuigiGad,
  • Like
Reactions: twins333
I have a somewhat unusual question. Over time, I noticed that the Picofly bypass system (vol+ + vol-) at console startup doesn't always work on all Switches. On some OLEDs, despite everything working perfectly in general (I'm talking about OLEDs with Kamikaze), the bypass procedure gives an *== error. I imagine it's a firmware issue; have you noticed it? Obviously, the reboot--OFW function works perfectly
 

Site & Scene News

Popular threads in this forum