Hacking Hardware Picofly - a HWFLY switch modchip

LuigiGad · Jun 17, 2024

sharlimar said:
Have anyone seen the partition table like this?

View attachment 442770

Context:
- Oled using hwfly rp2040 aliexpress
- First boot hekate couldnt do backup nand, had "Partition table is empty" - purple screen ofw - creating emummc bis keys error

Did:
- Changed cmd resistors
- tried different combos of adding more resistors to dat0 / cmd
- tried and Instict Hwfly with arm cpu
Still same problem...So emummc was screwed
- NxNandManager couldn't get GPP to extract PRODINFO so I could remake nand "Input file/drive is not a valid NX Storage" error
- Fortunetly got the prodinfo with program "HacDiskMount1055" and made sthetix new level2 and fixed purple screen
- Got back to hwfly rp2040 and "Partition table is empty" happened again, had to restore again, and got stable when I put more resistance on dat0 and no more slow emmc errors

Symptoms now:
- Can get to ofw and cfw but the partition table is like I never seen before (see image).
- sometimes glitch fail "**= No eMMC block 1 read (should not happen)"

Any idea?

dat0 kamikaze adapter reball?
View attachment 442770
Your photo is perfectly normal since version 6.2.0 of Hekare is shown like this

sharlimar · Jun 17, 2024

LuigiGad said:
dat0 kamikaze adapter reball?
View attachment 442770
Your photo is perfectly normal since version 6.2.0 of Hekare is shown like this

Oh its 6.20 hekate...didn't notice that thanks!

- Just using regular 4 anchor adapter

WaiazBoy · Jun 18, 2024

Hello guys,
I've tryed to install the picofly modchip on my Switch V1(Patchable). I've modded some V2 before deciding to mod a V1. So i followed an onli e guide and i've isolated all well with the kapton tape and everything seem works fine. So i closed the switch, booted again with hekate and everything worked as a charm. Before going to sleep, i powered off my switch and restarted because i was making some tests but i had forgotten to insert the sd card into the switch and righty appared "No SD Card", after this something happened, the screen starts glitching and after that cpu temperature went high(i could feel hot on the backplate) and after that switch was compleatly dead. I opened the switch and the picofly module show me the *== error code that stands for "No eMMC CMD1 request (poor wiring, or dead CPU)", so i want to understand what is happened because i cant give myself an explanation.
Thanks in advance for the help and sorry if my english is bad.

andere · Jun 20, 2024

Hello, maybe someone can help me, my Nintendo Oled CFW is normal if I enter CFW mode but if I enter OFW mode it's stuck on my Nintendo logo. Can anyone help?

Post automatically merged: Jun 20, 2024

Hello, maybe someone can help me, my Nintendo Oled CFW is normal if I enter CFW mode but if I enter OFW mode it's stuck on my Nintendo logo. Can anyone help?

thesjaakspoiler · Monday at 2:12 AM

andere said:
Hello, maybe someone can help me, my Nintendo Oled CFW is normal if I enter CFW mode but if I enter OFW mode it's stuck on my Nintendo logo. Can anyone help?

It can be so many things, both hardware and software.
Afaik CFW does need the Boot0/Boot1 partition from the internal memory (sysnand) to boot.
So if you can boot into CFW then that part must be working and it probably doesn't have anything to do with the modchip or the resistors.

Did you do anything else in particular like restoring a very old backup of the sysnand or did an attempt to update the OFW firmware fail?

Easy things to start with :
Can you enter the official maintenance mode (pressing vol - and + and then the power button)?
What does Hekate say about your internal memory (sysnand)?

I vaguely recall that a broken /disconnected Wifi also might keep one stuck on the Switch logo.
Does your wifi work in CFW?

Jagovi · Monday at 8:28 PM

Hi!
I just installed Instinct v6s on an OLED. Everything seemed to go well. I tested that the chip would turn on and do the glitch. I closed the video console, created emuNAND, installed games, and played them. Everything was working fine until I tried to access OFW. The Nintendo logo appears, and then the screen goes black. Sometimes, the error shown in the image appears if it manages to turn on.

I have changed the CMD resistor, replaced the DAT0 adapter three times, and still nothing, the issue remains. Any ideas? Everything works perfectly in CFW; the problem is with OFW.

Post automatically merged: Monday at 8:52 PM

Jagovi said:
Hi!
I just installed Instinct v6s on an OLED. Everything seemed to go well. I tested that the chip would turn on and do the glitch. I closed the video console, created emuNAND, installed games, and played them. Everything was working fine until I tried to access OFW. The Nintendo logo appears, and then the screen goes black. Sometimes, the error shown in the image appears if it manages to turn on.

I have changed the CMD resistor, replaced the DAT0 adapter three times, and still nothing, the issue remains. Any ideas? Everything works perfectly in CFW; the problem is with OFW.

In addition, if I disconnect the flex’s cable from the instinct switch start normally without black screen. I have tested 2 different instinct

thesjaakspoiler · Tuesday at 3:05 AM

Jagovi said:
I just installed Instinct v6s on an OLED. Everything seemed to go well. I tested that the chip would turn on and do the glitch. I closed the video console, created emuNAND, installed games, and played them. Everything was working fine until I tried to access OFW. The Nintendo logo appears, and then the screen goes black. Sometimes, the error shown in the image appears if it manages to turn on.

I have changed the CMD resistor, replaced the DAT0 adapter three times, and still nothing, the issue remains. Any ideas? Everything works perfectly in CFW; the problem is with OFW.

This post from a year ago showed the same 2002-3539 error and it turned out to be the DAT0 adapter.
https://gbatemp.net/threads/oled-switch-error-2002-3539-after-hwfly-oled-v3-install.611057/

Danook28 · Tuesday at 5:24 AM

thesjaakspoiler said:
This post from a year ago showed the same 2002-3539 error and it turned out to be the DAT0 adapter.
https://gbatemp.net/threads/oled-switch-error-2002-3539-after-hwfly-oled-v3-install.611057/

Sp1 sp2 is reson also bro...

thesjaakspoiler · Thursday at 11:45 AM

Danook28 said:
Sp1 sp2 is reson also bro...

indeed, but most people manage to get that right.

Ganesha0112 · Thursday at 2:40 PM

Hello friends.

Some days ago y bought this model of picofly in aliexpress. I installed some modchips but I notice that some modchips don’t work properly it fails sometimes and don’t go to OFW only black screen.

I notice that the modchip has a big strange flash memory and this only happen when I flash the modchip with any picofly firmware that don’t come with the modchip.

The chip comes with a rare combination between Spacecraft and Picofly firmware, don’t boot OFW if one point of the chip it’s not correctly connected, you cannot go to OFW in the “NO SD” screen pressing vol + and Vol -, the error code are not accurate and that I said previously the modchip don’t work properly with another picofly FW.

So mi question is: anyone know what is this? And anyone know how can a i extract the firmware from the modchip or something like that? anyone have this firmware? I flashed 2 chips but don’t work properly and I want make work the modchips again.

Danook28 · Thursday at 9:40 PM

Is there any place for sda scl on V1 patched console near sound conector nothing like the 6.4v pdf info. I use one mosfet on cpu. It start to white then blue then 4 time yellow light. From back same *the CPU point* from back GIVE read 0.245 one mosfet near cpu GIVE read 0.545v boot to ofw.18.1.0 update.

I use 3.74 fw
I use 3.75 fw same.

0DanDan0 · Thursday at 10:01 PM

mathew77 said:
View attachment 341371

Wiring looks garbage he needs smaller aug and flux

bvang913 · Thursday at 10:36 PM

0DanDan0 said:
Wiring looks garbage he needs smaller aug and flux

You know you're responding to a post from almost two years ago right?

LuigiGad · 2024-06-29T16:37:41+0100

To be deleted posted by mistake

Nontre · 2024-06-29T18:47:25+0100

Yesterday I installed a modchip on my OLED. On my first attempt, I received a =* long-short yellow light code. I found that the DAT0 was not correctly installed (multimeter diode mode was showing an open connection between DAT0 and ground). Now I'm getting a fixed ~0.845 reading.

After "fixing" that issue, I'm getting a different error code: *=* short-long-short. I saw on the wiki that this means "no eMMC block 0." The Switch is not booting. All I can see is the modchip flashing the error code.

Even removing the entire mod kit I can't get the console to turn on, is it possible that I have broken some point of the emmc using the adapter while getting access to the DAT0 point?

Its fixable? Is my Switch dead? Should i start selling it by parts?

Thank you!

Jagovi · 2024-06-30T00:15:42+0100

Hi!!! I have installed an Instinct v6s in a Nintendo Switch OLED using the kamikaze method. I verified that everything was working and closed the console. I configured the WiFi and started installing games. After installing more than ten games, the screen froze. I turned it off by holding down the power button for 20 seconds and then turned it back on. Upon restarting, I noticed that I had no touchscreen and network connectivity (error 2110-1118).
I opened the console and found a resistor near the display flex that was out of (blue group in photo). I replaced it with a new one and restored the touchscreen functionality, but I still can't get the WiFi to work. What could have caused both functions to fail simultaneously? What should I check? The two capacitors to the left of the CPU shield have correct values (red group in photo).

Thank you very much in advance!!

Hacking Hardware Picofly - a HWFLY switch modchip

Well-Known Member

Member

New Member

New Member

Well-Known Member

Active Member

Attachments

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Attachments

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

New Member

Active Member

Attachments

Similar threads

Popular threads in this forum