I had a peek at the source code and although I don’t actually know Rust it looks like that error comes from a check for character length in the function “is_valid_body_field”. Strangely it does the same check twice against two variables “POST_BODY_MAX_LENGTH” and “BODY_MAX_LENGTH”.

The smaller of the two is BODY_MAX_LENGTH which is set at 10000, so I assume the max character limit is 10,000. There are no other checks in that function other than the character count and that’s the only place in the source code that the text “invalid_body_field” shows up so I assume it’s only sent as a response to too much text, but as I said I don’t actually know Rust so I could be wrong.

Here’s the github page for the program that’s at least partially responsible for that output.

From that page it appears detected means “Device is detected, driver is found, but not tested yet” and working means “Driver is found and operates properly (passed static or dynamic tests)”

In the case of tetracycline antibiotics the degradation products can damage the kidneys and cause Fanconi syndrome. So in that case as a medicine for people it becomes poison, as a poison for bacteria it becomes safer.

Did you try plugging it in initially after you disassembled it and reassembled it? I’ve found on chromebooks that the embedded controller doesn’t seem to wake up until the charger is plugged in after unplugging the battery. Could it be that you initially didn’t plug it in before trying it months ago, but months later you figured the battery would be low after all that time so you plugged it in finally starting the embedded controller?