Hacking Hardware Picofly - a HWFLY switch modchip

[jkyoho]

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=131
noticker=0
autohosoff=1
autonogc=0
updater2p=0
bootprotect=0

{-- Custom Firmwares --}

[AMS (EmuMMC+Incognito)]
cal0blank=1
atmosphere=1
emummcforce=1
fss0=atmosphere/package3
kip1patch=nosigchk
icon=bootloader/res/icon_ams_emu_inc.bmp
{}


[Official Firmware]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/icon_switch_logo.bmp
{}

Post automatically merged: Jun 29, 2023

in this case I'm trying to access OFW

I assume your error code shows after you select in Launch section?
If that error code shows when you entering hekate, update your PAYLOAD.BIN to latest HEKATE aswell

 

[aleciobr]

I assume your error code shows after you select in Launch section?

yes

 

[jkyoho]

yes

https://github.com/Atmosphere-NX/Atmosphere/releases

try atm1.5.4
I don't see any issue on latest HOS 16.0.3 from HEKATE605+ATM154

 

[aleciobr]

I assume your error code shows after you select in Launch section?
If that error code shows when you entering hekate, update your PAYLOAD.BIN to latest HEKATE aswell

nothing, still the same error

what I'm most nervous about is that I made the backup, created the emunand and now it's giving me an error to enter the ofw

 

[jkyoho]

what I'm most nervous about is that I made the backup, created the emunand

those did nothing on HOS/OFW, only CFW on sysnand may have effect on

 

[impeeza]

post your hekate_ipl.ini

And remember to update the file SD:/payload.bin

 

[abal1000x]

Update for Lite

View attachment 380754

Multiple glitch.
View attachment 380756

I have no oled and v2 right now.

Maybe next week i will get v2.

If you have oled, please confirm, whether this works or not.
So the community might take the advantegous of this.

 

[snaker]

very cool! eristas usually glitch really fast though, I would love to see this tested on a Mariko for comparison.

I can see this becoming the method of choice especially for oleds since you have to remove the motherboard anyway. On lite/v1/v2 removing the motherboard will be an additional inconvenience. Maybe better than removing apu shield and cleaning thermal paste, though?

I have not done lot of marikos but for those i installed rp 2040 with 2.73 the boot times are almost instant. I cant say the same for oleds except for those with samsung nands.

 

[Dandan0404]

does removing the resistor 47 ohms bad in DAT0? mine got lose contact/cold solder and proabably burned the resistor trying to connect it back. so i had to remove it and directly connected to picofly and it works. im questioning about the long run, if there are any issues it will happen in the future?( ie burning something, overloading the board, etc etc) so far glitch is good

 

[chronoss]

v2.74 + 300 mhz precision rp2040 may be not stable at 300mhz

@rehius ????

 

[cgtchy0412]

Hi @abal1000x , confirmed for lite .. tested also .. as always with aon mosfet.. now just need to tidy things up. Thanks for the research.

 

[deeps]

does removing the resistor 47 ohms bad in DAT0? mine got lose contact/cold solder and proabably burned the resistor trying to connect it back. so i had to remove it and directly connected to picofly and it works. im questioning about the long run, if there are any issues it will happen in the future?( ie burning something, overloading the board, etc etc) so far glitch is good

without added resistance the noise of the rp2040 interferes too much with emmc communication. So you will most likely have issues booting into ofw now.

 

[chronoss]

Then check and make sure all cables connected and nothing is grounded
Specially dat0 cmd and clk

I breack my dat0 point, there is an alternative ?

 

[QuiTim]

I breack my dat0 point, there is an alternative ?

Well now you know (unfortunately) :/ https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10184170
This will work https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10184138

End result of how it should be done: https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10185204

 

[chronoss]

Well now you know (unfortunately) :/ https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10184170
This will work https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10184138

End result of how it should be done: https://gbatemp.net/threads/picofly-a-hwfly-switch-modchip.622701/post-10185204

Good thanks but i have no good cutting tools tu cut the shell
After that, i need to connect the chip to the adaptater ?

 

[aleciobr]

Does anyone know how to solve this problem?

View attachment 380745

Good morning, I was talking to jkyoho and he said to remove the cable that goes to pikofly, I removed it and it booted normally in ofw, which could be the error that persists when you have pikofly

 

[Dandan0404]

without added resistance the noise of the rp2040 interferes too much with emmc communication. So you will most likely have issues booting into ofw now.

Oh so its in Ofw, the cfw seems to be good

 

[QuiTim]

Good thanks but i have no good cutting tools tu cut the shell
After that, i need to connect the chip to the adaptater ?

You need to get the dat0 connection from under the emmc (as you would in an Oled) then bridge/fix the via/trace you damaged so the switch is working again.
Then if you want to install the mod you can solder the dat0 to the alternative point on the right side of the board (you have pictures on those post from abal1000x)

 

[chronoss]

You need to get the dat0 connection from under the emmc (as you would in an Oled) then bridge/fix the via/trace you damaged so the switch is working again.
Then if you want to install the mod you can solder the dat0 to the alternative point on the right side of the board (you have pictures on those post from abal1000x)

if no bridge, switch not working without the chip ?

 

[jkyoho]

if no bridge, switch not working without the chip ?

No bridge NO work

Post automatically merged: Jun 29, 2023

Good morning, I was talking to jkyoho and he said to remove the cable that goes to pikofly, I removed it and it booted normally in ofw, which could be the error that persists when you have pikofly

show your solder work