Hacking Hardware Picofly - a HWFLY switch modchip

thesjaakspoiler · Monday at 9:39 AM

LuigiGad said:
I also recovered this OLED perfectly. among the tests I did I increased the dat0 and CMD resistance and replaced the cmd resistance. perfect result. but too much time wasted. then to start the stock I had to do a boot with a patch on sysnand
Ok there could be a poor connection on DAT0, but if you unsolder the problem disappears in stock. Even unsoldering the whole screen is black for me, then fiddling here, fiddling it gets back on its own... I can't figure it out. If 6/7 points I'm 100% sure, a point that in the end was still valid gave me a lot of headaches

here is the gallery of horrors

That NYX error might indicate some data corruption on your SD card.

LuigiGad · Monday at 3:57 PM

thesjaakspoiler said:
That NYX error might indicate some data corruption on your SD card.

With a cool head I think I understood what made me confused during the various tests. I made the big mistake of testing the ofw not by completely disconnecting the picofly, but by disconnecting only the cmd so as to mislead the boot and have the original boot. Unfortunately the DAT0 remained connected to the 47ohm resistor and this led me to have a black screen in stock while in reality it was not stock. This led me to look for the mistake where there was none and in fact waste a lot of time. You never stop learning

jkyoho · Monday at 4:41 PM

LuigiGad said:
With a cool head I think I understood what made me confused during the various tests. I made the big mistake of testing the ofw not by completely disconnecting the picofly, but by disconnecting only the cmd so as to mislead the boot and have the original boot. Unfortunately the DAT0 remained connected to the 47ohm resistor and this led me to have a black screen in stock while in reality it was not stock. This led me to look for the mistake where there was none and in fact waste a lot of time. You never stop learning

I thought after failed glitching modchip always redirect bootloader back to official Nin BL and straight into OFW, at least my WaveShare RP2040 pico/ONE/ZERO/tiny does that normally.

Tom8823 · 2024-09-26T01:19:53+0100

Anybody had this before?

I installed my chip with mosfet more than a year ago.

Everything was working fine for months except that twice already I had a situation where after I upgraded switch firmware my chip failed to boot up. I updated to 18.1.0 yesterday and I shut down console and pressing power button does nothing. No LED light on chip, nothing, dead. I managed to start console by holding power button for 30 seconds and hekate started. I opened picobox and reset switch and after shutting down console it booted up but on another shutdown again black screen and I have to hold power button long to fix it. Then on another boot up hekate starts but starting CFW ends up with "failed to init emmc" error. The only way to permanently fix it is to open console and disconnect battery and reconnect. Then it will act fine and until next time it happens which can take months. I am not 100% sure it's related to firmware update but that's what I did yesterday.

My soldering is good becaue like I say it will work fine for months until this happens. Then I have to open console to reconnect battery. It's so annoying

Also my console crashed after echoes of wisdom so maybe it's emmc error.

LuigiGad · 2024-09-26T05:33:55+0100

try changing the cmd resistance, you have to do some cross tests to find the problem.

linkref · 2024-09-26T23:14:52+0100

Does anyone found a solution for the short short long error (**=), the latest firmware did not help.
Occurs only on some OLEDs, error occure 1 times out of 10, rest of the time it's okay glitching.

I fix this with instinct nx but now i do not have any nx left...

lightautodark · 2024-09-27T02:20:36+0100

linkref said:
Does anyone found a solution for the short short long error (**=), the latest firmware did not help.
Occurs only on some OLEDs, error occure 1 times out of 10, rest of the time it's okay glitching.

I fix this with instinct nx but now i do not have any nx left...

Yup. It was the kamikaze point soldering. Check my previous post.

Even though the dat0 value measured fine, just redo your soldering, I managed to correct my 2 units that have this exact problem.

twins333 · 2024-09-27T04:45:00+0100

lightautodark said:
Yup. It was the kamikaze point soldering. Check my previous post.

Even though the dat0 value measured fine, just redo your soldering, I managed to correct my 2 units that have this exact problem.

It's the dat0 connection in general. it happened with a dat0 adapter as well.

Hacking Hardware Picofly - a HWFLY switch modchip

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum