Picofly AIO Thread

[cilione]

My friend, could you tell me how to get the boardview of the Nintendo Switch models, please? It would be extremely useful in my daily life.
TIA

Do you have the board view file (the black and red picture that you've posted)??

I've used the files from here:

https://files.zzattack.org/img/console/switch/

I imported all the layers into Photoshop.

 

[RedDragon777]

Hi all.

When i connect powersupply connector to motherboard The led flashes as you can see in the video.When i push the power button,the chip is not glitching.The console booting to ofw.The picofly programed with 2.76 fw.Whats the problem?

 

[QuiTim]

Hi all.

When i connect powersupply connector to motherboard The led flashes as you can see in the video.When i push the power button,the chip is not glitching.The console booting to ofw.The picofly programed with 2.76 fw.Whats the problem?

CLK not connected
Might be RST not connected as well but since I don't have a reference for timing you should check both.

 

[cilione]

Hi all.

When i connect powersupply connector to motherboard The led flashes as you can see in the video.When i push the power button,the chip is not glitching.The console booting to ofw.The picofly programed with 2.76 fw.Whats the problem?

Looks like "RST not connected" to me.
Have you checked diode readings?
Unplug the battery.
Put multimeter in diode mode, black probe on ground (for example, on charging connector).

Probe each connection on the Pico with the red probe and post the values here.

 

[RedDragon777]

Hi.


The diode values is:
C/DAT0 0.743
A/CMD 0.736
D/CLK 0.739
B/RST 1.585
CPU (dual mosfet):0.364

 

[Jehmyson]

Just complementing what has been said:

Maybe could be a short circuit on the board. It shouldn't be like this because the Switch needs to turn on and off with the power button. Cleaning the residual flux at the soldering points can solve this problem of booting after connecting the battery or check that the button isn't shorted

 

[Hassal]

Hi all.

When i connect powersupply connector to motherboard The led flashes as you can see in the video.When i push the power button,the chip is not glitching.The console booting to ofw.The picofly programed with 2.76 fw.Whats the problem?

Which schematic did you follow?

 

[ancylow]

Hi all.

When i connect powersupply connector to motherboard The led flashes as you can see in the video.When i push the power button,the chip is not glitching.The console booting to ofw.The picofly programed with 2.76 fw.Whats the problem?

Where is fw 2.76?

 

[nukeru84]

Hi,
Before my switch oled work fine with picofly clone ,i updated CFW to 17.0 and keep OFW to 16.0 and worked fine before.Now i get 2 yellow led blinking (Long + short) and booting to OFW .When i remove the sd card ,i get always same issue (no screen "No SD") and boot into OFW.Could someone help.thanks

 

[QuiTim]

Hi,
Before my switch oled work fine with picofly clone ,i updated CFW to 17.0 and keep OFW to 16.0 and worked fine before.Now i get 2 yellow led blinking (Long + short) and booting to OFW .When i remove the sd card ,i get always same issue (no screen "No SD") and boot into OFW.Could someone help.thanks

Nothing to do with the fw version. Dat0 point was not set correctly so it moved/lost contact. Need to reseat the dat0 adapter or even better set a permanent point by reballing/reflowing the emmc.

Post automatically merged: Nov 27, 2023

Which schematic did you follow?

@RedDragon777 i want to know this aswell

 

[Jehmyson]

Where is fw 2.76?

All the files are on the GitHub page but I didn't find FW 2.76

 

[abal1000x]

Hi all.

When i connect powersupply connector to motherboard The led flashes as you can see in the video.When i push the power button,the chip is not glitching.The console booting to ofw.The picofly programed with 2.76 fw.Whats the problem?

Your 3.3V point seems wrong. CMIIW.

 

[Magnetic87]

I've lost (yes, lost) the WiFi chip cover shield on my V2 Switch.

WiFi/Bluetooth still work.

Where can I get a new one?

 

[mviper28]

Where is fw 2.76?

All the files are on the GitHub page but I didn't find FW 2.76

here (sorry i can't post links yet)

 

[Moneyforthecash]

(sorry i can't post links yet)

https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10264390

But not really trustworthy from my point of view. Why should you update. 2.75 runs very well. And this strange 2.76 version doesn't even offer a changelog. Strange results if i translate "abal version"
I advise everyone not to use this.

 

[LuigiGad]

https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10264390

But not really trustworthy from my point of view. Why should you update. 2.75 runs very well. And this strange 2.76 version doesn't even offer a changelog. Strange results if i translate "abal version"
I advise everyone not to use this.

I'm sorry to contradict you but I use it regularly and I've never had any problems on the contrary...

 

[Jehmyson]

here (sorry i can't post links yet)

Tnks bro.

https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10264390

But not really trustworthy from my point of view. Why should you update. 2.75 runs very well. And this strange 2.76 version doesn't even offer a changelog. Strange results if i translate "abal version"
I advise everyone not to use this.

I agree with your thinking, in a way.
I would like to find a changelog to check these changes, but I have not been successful. Does anyone know what improvements these latest versions bring? I always used fw 2.73 in everything I did and I didn't have any errors yet.

 

[abal1000x]

https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10264390

But not really trustworthy from my point of view. Why should you update. 2.75 runs very well. And this strange 2.76 version doesn't even offer a changelog. Strange results if i translate "abal version"
I advise everyone not to use this.

Seems you are not read that post correctly.

v200.75 is my version.
The source code is in 'abal_version' branch.
The difference is miniscule, only in the 'shutdown' mechanism.
Trustworthy or not is irrelevant, since the code is open source.
Its not about trustness, just read the commit code and you know the change.

v2.76 is from the original source code (rehius github).
But theres no compiled version on the release, i've compile it.
https://github.com/rehius/usk/blob/6530fd9fe58980ea03d47905bad5e871b9439b7a/config.h#L7
For the changelog, i've share my point of view on it:
https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10292066

But of course you might choose whatever version you want.
For me i prefer v200.76, since i know what i am doing.
For other i advise using v2.76, since i know what rehius doing.

 

[k28]

i went ahed and ordered picoflys somewhere else and im having the same issue. could the replacment emmc modulissue?

I doubt it. The glitch is working before any firmware loaded. So it doesn't have any dependency on the firmware. Theoretically, if you have zeroed emmc, the picofly still works. You could imagine it as a bootloader.


Seems not possible.

The known flow of boot, will run the code ON the emmc. The picofly inject the sdloader to the emmc (hence the nosd). The function of the sdloader is to transfer the running code from the emmc to the sdcard. Which then we could run any program we put on the sdcard, such as hekate.

i went ahed and ordered picoflys somewhere else and im having the same issue. could the (3rd party)replacment emmc modul issue(maybe in combination with fw 17? i revive consoles with faulty emmc modules. the picofly boots into hekate with them etc. but upon replacing the emmc modul the switch boots straight into ofw. i flashed picofly firmware 2.76(the one you compiled) and gives me long short long short error and boots into ofw.

EDIT: Flashed bacl the rebuild nand to the stock emmc modul which was originaly installed by nintendo. picofly glitches and i can boot into cfw sysnand. when i reboot into OFW via hekate the switch stuck at nintendo logo. when i remove the picofly and and install the stock emmc modul to directly onto the mainboard the switch boots into OFW. wtf is going on ;( also tried and old HWfly chip with the original stock emmc and the 3rd party emmc. there it lights light blue then red imidietly and red and boots into ofw. maybe the 3rd party is incompatible and the stock nand is partialy faulty? will try different original emmc modules and next i will test a donor nand as i think i revived a console with dead emmc modul and it bootet to ofw and cfw via hekate and fw 17.

 

[Crung]

SOOO. i have a V1 acting up. Sometimes the chip does not turn on (no light on the LED),and it opens OFW.
I have replaced gnd and 3.3v wires to 30 awg,same result.
I have "reflowed" the solder on the connections and still same result.
Here are some pictures