The chip count is only ever a clue and does often change with multiple attempts on a bad board. A lot of times the core problem is a resistive or flaky connection that can change with temperature. So you might get 0, or a number close to the actual problem area, or a random number.
domain if I am not wrong. I agree that just re-soldering is a shot in the dark but I lack expertise and probably equipment to do anything more.
Chain 0 is now saying
"chain 0 get hashrate_reg_counter 63, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxooo"
compared to last time
chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx"
I don't know the exact meaning/format last part of these lines. The chips on the board are all connected in series in a chain, so to get a message from chip 65, it gets forwarded through every other chip on the board. If chip 63 has a problem, it normally won't forward messages from the chips further down the chain and you end up with a count of 62. So I don't know if that "xxooo" on the last domain is just ordered backwards so the two x chips are actually 65 and 64, or if the chips are both forwarding messages correctly but not responding with their own messages correctly.