I already told you in the other topic that you probably need to increase the resistors for CMD & DAT0 to 100 ohms. After the chip installation, the console MUST start in the OFW, otherwise something is wrong!
Well, you have to know which firmware the switch has and which firmware you use for the chip. With the Picofly Toolbox you can see the version of the chip.
Which chip did you install? What firmware does your switch have and what firmware does the chip have?
1744537158
With the firmware 19.0.1 and Picofly 2.75 I have had the best experiences. Then almost never had to install additional resistance again.
With such problems, a picture of your installation will help. Maybe you can already recognize the first clues there. In the removed state it worked, it could also be that you did not shield something well.
Help, help!! Have you ever soldered? Don't take it personally, but that looks very sloppy. Cheap solder and probably no flux?! Don't use video as a reference next time. There is a very good tutorial here.
First you should clean the board thoroughly!
Have you measured the individual points to see if they have the correct values? CLK check whether there is actually a connection. Perhaps you interrupted the trace.
If all this doesn't help, you have to look for short circuits.
If the values are below standard, there are only two main causes. No correct connection or you measured differently. Usually you measure in diode mode with red to ground. Most people do it the other way round and then get different values.
I have the same problem. Must have started since the last update. Before, I could just ignore it and play Doom, but now I'm forced to turn on airplane mode or change my ini. Luckily, it's only happened with Doom (2016) so far... even Eternal works perfectly.
It's certainly cleaner and maybe a little faster. But many of these flex cables can't handle a lot of heat and are of poorer quality. I use cables at the individual points and I know 100% that there won't be any problems.