The mysterious cmd break solved, picofly is not the culprit afterall. Its the installer again, misunderstood something.
First time i experience with FPC connector on some laptop motherboard, i break it. Since then, if its FPC connector i will use microscope, and open it using tool (never use hands nail) very very very slowly. That FPC connector is fragile.
When installing in oled, i don't place the display again and again, since fpc connector is fragile. Not just the display, almost any fpc in there, including the power on/off. To power on just use needle to short the pin.
There is two stage on the picofly, write payload to the emmc and glitch. Those long white is the first stage which is write payload to the emmc, its only done 'one time'. The next one you wont see any long white, means picofly already detected the payload in the emmc.
My current method is installing anything except the mosfet part. And turn it on, if its work, picofly should shows blue white, then throws glitch error. If the white doesn't show then my cmd/clk/dat0 installation still have problem. If its okay, then install the most dangerous part the mosfet.
In your case, since the first stage is passed, and glitch working. Then the problem is your connection is not stable. It could be dirty, flux residue, or cold joint, etc. I've once meet the same problem with yours on oled, check the dat0 adapter diode mode value, and its slightly decrease than the usual working one. Shift little bit, check the diode mode value okay, then resolder the lock. Its works. But it could be different in your cases.
Ouch that seems difficult. Even i have all the tool, but afraid to do it, since i don't have experience on it. Need a broken dummy board to experiment the method and the heat parameter which suited.
The glitch will worked even without the display.