Hacking Hardware Picofly - a HWFLY switch modchip

[trungnguyen]

I have removed all boot ofw, the screen is purple

 

[sergiochendry]

Thx guys
Finally done

 

[trungnguyen]

I removed all of them and booted into ofw and got a purple screen

 

[LogicalMadness]

I accidentally soldered emmc to rp2040 but forgot to remove the baterry. Now the switch I booted only shows a purple screen, is there a way to fix it? i have another machine that has mod hwfly can restore emmc error machine?

Post automatically merged: Apr 26, 2023

View attachment 367264

This was literally JUST discussed IN THIS PAGE. Your CMD resistor is faulty. Check it's resistance is still 4.7k and that it's soldered on both pads.

That belly in the picture is priceless...

 

[Dee87]

Reporting my RP pico successfully glitching after being cut as per @rehius and @Dee87's diagram.

Looks nice for a proof-of-concept. I came to notice that the Dat0 point on RP Pico is very fragile so I engraved a trace right next to the RP's chip, this made me keep the other side of pins that would have been otherwise cut, but I needed the ground on that side to not make it messy next to all the resistors, not to say it doesn't look messy anyways lol.
View attachment 367122
Thank you @rehius and @Dee87. You guys have been very helpful and responsive.

looks good nice u got everything working now
no problem thats for what we are here right ?

 

[Dlacica]

Wish me luck guys

 

[glagla]

Is that a good sign ?

 

[Jonas225]

Hi,
I finished my first install yesterday. I come from the Xbox360 JTAG / RGH community where I installed hundreds of modchips but WOW the Nintendo solder points are crazy small.

But everything went smooth during installation and the console boots really quick.

I have one problem that OFW does not boot. Nintendo logo and then black screen. Is there a fix for that?
I am using FW 2.66

 

[Dee87]

Hello. One question about MOSFETs:

Why do some remove the caps and solder directly to the pad? That's what Voultar is doing. Is it better?

its just easier for some people to get to the pads i always recommend leave the caps on there is always a reason it was designed that way .-)

 

[eseldiem]

*Woosh*

Huh? He's trying to advise someone on how to possibly not wait a long time for parts. The fk you on about? O.o

Piracy opinions are pretty worthless in this thread too XD

You’re right. I should have re’d to the poster, not to Dee’s reply.

Also, not everyone mods their switch for piracy.

 

[CapitolLimited]

Current issue for 2.61 is we can't boot to OFW, whether using hekate->reboot->ofw or by vol+ vol_.
But still can boot OFW via "warmboot error fix".

I am having this same problem right now. Do I need to fix Boot0 too, or does simply updating the chipset solve it?

 

[Don Killah]

I accidentally soldered emmc to rp2040 but forgot to remove the baterry. Now the switch I booted only shows a purple screen, is there a way to fix it? i have another machine that has mod hwfly can restore emmc error machine?

Post automatically merged: Apr 26, 2023

View attachment 367264

Nice summer body

 

[deeps]

I accidentally soldered emmc to rp2040 but forgot to remove the baterry. Now the switch I booted only shows a purple screen, is there a way to fix it? i have another machine that has mod hwfly can restore emmc error machine?

Post automatically merged: Apr 26, 2023

View attachment 367264

You also forgot to put on a shirt before taking this photo. Have some dignity bro

 

[wikisa]

i'm attempting to do picofly installment on oled - what resistance should I get between D0 from adapter and metal shielding around emmc? My multimeter shows me 1.84Mega Ohm, is that correct reading to believe D0 adapter is correctly mounted?

 

[QuiTim]

i'm attempting to do picofly installment on oled - what resistance should I get between D0 from adapter and metal shielding around emmc? My multimeter shows me 1.84Mega Ohm, is that correct reading to believe D0 adapter is correctly mounted?

Put the meter on diode (beep) mode, then mesure, you should have 0.4 to 0.8 something in that range.

 

[CapitolLimited]

I got my OLED back from the modder using a Xiao2040, and was following the reentry guide on setting everything up. I have my EmuNAND set up and everything with NAND backups, but I've run into an issue where if I try to boot into OFW using the "purest way" with the SD Card taken out and then pressing the volume buttons, I get the Nintendo screen then a loading icon, and then it goes back into the Pico screen. The same thing happens when I try to boot OFW from Hekate's home menu, and then Reboot.


However, if I click on Hekate and then launch, both Atmosphere CFW and "Wormboot Error Fix" load up perfectly fine with CFW working properly, and SysNAND working fine through Wormboot. I looked back through previous posts and it seems like this may be a result of old firmware bugs (especially with users having trouble going through Hekate Reboot, but I don't recall if they had issues with a "clean" boot with the volume buttons. I was wondering how to solve this or if my Boot0 is completely corrupted. Perhaps I should try upgrading pico with the latest 2.67? Thanks.

Some video links demonstrating what's happening:

Pico Boot:

OFW through Hekate:

 

[rehius]

I got my OLED back from the modder using a Xiao2040, and was following the reentry guide on setting everything up. I have my EmuNAND set up and everything with NAND backups, but I've run into an issue where if I try to boot into OFW using the "purest way" with the SD Card taken out and then pressing the volume buttons, I get the Nintendo screen then a loading icon, and then it goes back into the Pico screen. The same thing happens when I try to boot OFW from Hekate's home menu, and then Reboot.


However, if I click on Hekate and then launch, both Atmosphere CFW and "Wormboot Error Fix" load up perfectly fine with CFW working properly, and SysNAND working fine through Wormboot. I looked back through previous posts and it seems like this may be a result of old firmware bugs (especially with users having trouble going through Hekate Reboot, but I don't recall if they had issues with a "clean" boot with the volume buttons. I was wondering how to solve this or if my Boot0 is completely corrupted. Perhaps I should try upgrading pico with the latest 2.67? Thanks.

Some video links demonstrating what's happening:

Pico Boot:

OFW through Hekate:

Update the firmware. Already fixed.

 

[wikisa]

Put the meter on diode (beep) mode, then mesure, you should have 0.4 to 0.8 something in that range.

Thank you, it shows 0.708

 

[rehius]

Put the meter on diode (beep) mode, then mesure, you should have 0.4 to 0.8 something in that range.

You should measure that while the wire is NOT soldered to the pico. Otherwise you get the pico measurements, not the actual points

 

[QuiTim]

You should measure that while the wire is NOT soldered to the pico. Otherwise you get the pico measurements, not the actual points

Yes, i assumed he was trying to test the connections before connecting the Pico.
If one has already soldered to Pico it might as well give it a shot and see if it boots