Hacking Hardware Picofly - a HWFLY switch modchip

[superxoi]

Hello @psycho-neon. Have chips manufactured with component assembly. I put three, all three flashed correctly. The first chip rarely does not turn on with the console, the second went well and the third directly does not turn on with the console. Have they given you any problems? I'm thinking about throwing them away and sticking with my Rp2040s, which never fail me.

Chips work fine friend. This is the 2nd batch. You have to check cpu pins to see if there is any bridge on your board.

 

[CarlosCruz]

@psycho-neon
This one?

 

[psycho-neon]

@psycho-neon
This one?

Yes.

 

[CarlosCruz]

Yes.

OKAY. I will try. Thx

 

[Danook28]

All this chip is bcp made???? No in AliExpress like this???? Ready program!!

 

[deeps]

All this chip is bcp made???? No in AliExpress like this???? Ready program!!

You my friend have the bestest English.

I'll do an attempt at translating for the others:
"Is this chip custom made, and delivered assembled and ready to be programmed? Not possible to purchase on Aliexpress?"

The answer is: Yes. You use the files from this post: https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/page-750#post-10367725
and make an order at JLCPCB with assembly included.

 

[naldo29]

Getting stuck on the logo can only mean one thing, there's a problem in your system partition. Though I'm not sure how you managed to cripple both since its usually one and not the other since they are separate entities.

You probably made a mirror of your sysNAND when its on the brick going bust.

its 100% something hardware related. Just tried restoring my console by following level 1 and level 2 of sthetix guide and even wiping the entire nand and replacing it with a new one resorted with the same exact issue. Could there be something in the hardware side that could cause this? becuase it would be the only explanation onto why both emunand and sysnad both stopped working on the same time and why rebuilding my nand didnt work either and just produced the same issue

 

[thesjaakspoiler]

its 100% something hardware related. Just tried restoring my console by following level 1 and level 2 of sthetix guide and even wiping the entire nand and replacing it with a new one resorted with the same exact issue. Could there be something in the hardware side that could cause this? becuase it would be the only explanation onto why both emunand and sysnad both stopped working on the same time and why rebuilding my nand didnt work either and just produced the same issue

When Nintendo released firmware 17.0.0 they caused some problems.
https://gbatemp.net/threads/switch-stuck-at-nintendo-logo.651058/post-10380256
The question was whether your nand backup was completely clean or that you already used it with a CFW?
Would resorting to a factory reset maybe fix such issues?
Another thing I was wondering is whether the BOOT0 and BOOT1 partition are used from the sysnand.
I saw someone that posted a message that he could not use the emummc without a physical sysnand/emummc.
That would imply that if for some reason there a some data corruption that affect BOOT0 or BOOT1 then you would habe problems with both your sysnand and emummc.

 

[Danook28]

its 100% something hardware related. Just tried restoring my console by following level 1 and level 2 of sthetix guide and even wiping the entire nand and replacing it with a new one resorted with the same exact issue. Could there be something in the hardware side that could cause this? becuase it would be the only explanation onto why both emunand and sysnad both stopped working on the same time and why rebuilding my nand didnt work either and just produced the same issue

Try new mmc chip... If not change that may hardware problem....

 

[naldo29]

When Nintendo released firmware 17.0.0 they caused some problems.
https://gbatemp.net/threads/switch-stuck-at-nintendo-logo.651058/post-10380256
The question was whether your nand backup was completely clean or that you already used it with a CFW?
Would resorting to a factory reset maybe fix such issues?
Another thing I was wondering is whether the BOOT0 and BOOT1 partition are used from the sysnand.
I saw someone that posted a message that he could not use the emummc without a physical sysnand/emummc.
That would imply that if for some reason there a some data corruption that affect BOOT0 or BOOT1 then you would habe problems with both your sysnand and emummc.

hmm, that could be the case, if boot0 and boot1 are damaged then that could make sense on how both broke at the same time.

Also the only nand backup i did was AFTER my switch got fucked. Just incase i fucked it up even more while trying to restore it back.

Unfortunately i tried restoring this console using all 3 levels of sthetix guide and none worked. I frankly dont know what else to try

Post automatically merged: Apr 30, 2024

Try new mmc chip... If not change that may hardware problem....

its an oled. That would requiere to reball. Sadly i dont know how to do that rip lol.

 

[Danook28]

hmm, that could be the case, if boot0 and boot1 are damaged then that could make sense on how both broke at the same time.

Also the only nand backup i did was AFTER my switch got fucked. Just incase i fucked it up even more while trying to restore it back.

Unfortunately i tried restoring this console using all 3 levels of sthetix guide and none worked. I frankly dont know what else to try

Post automatically merged: Apr 30, 2024

its an oled. That would requiere to reball. Sadly i dont know how to do that rip lol.

Are the sd card exfat or fat32???

 

[naldo29]

Are the sd card exfat or fat32???

FAT32

 

[Danook28]

Are the update fw that you rebuild the nand is fw support with cfw files in sd is it 18.0.0???

FAT32

 

[naldo29]

Are the update fw that you rebuild the nand is fw support with cfw files in sd is it 18.0.0???

yes, they are straight from 1.7.0

 

[Danook28]

You

yes, they are straight from 1.7.0

Need boot1 boot0 and prod info. For Orginal your oled... If no chip on motherboard are fulty and is mmc reson so buy Samsung mmc and send to repaire shop only...

 

[abal1000x]

yes, they are straight from 1.7.0

Have you check trivial hardware like the cmd resistor, or the resistor around the emmc, for short circuit?

 

[Danook28]

Have you check trivial hardware like the cmd resistor, or the resistor around the emmc, for short circuit?

I finsh mod V2 console 18.0.0 fw and chose emummc it is working fine with hats pack 17.0.2 and when try go cfw it show error msg host pkgl... Ofw after nintendo logo black secreen.

 

[naldo29]

Have you check trivial hardware like the cmd resistor, or the resistor around the emmc, for short circuit?

what resistor near the emmc? i only see caps. But yes ive checked them and none are shorted.

 

[abal1000x]

what resistor near the emmc? i only see caps. But yes ive checked them and none are shorted.

Every cmd has resistor to pull up.

 

[naldo29]

Every cmd has resistor to pull up.

wdym by pull up? also werent you talking about resistors near the emmc, not the cmd?