what kinda drugs are the chromebook people on. who thinks this is a reasonable flashing procedure. (it doesn't work with the device i have and i've spent a hour so far figuring out why)
13
18
172
Conversation
6
17
150
Q4 is a transistor in WLCSP, because you must suffer not only while flashing it (exactly once, you can enter DFU mode via software later on) but -also- while assembling it.
this design is like a crash course in making the least accessible OSHW you can possibly imagine
2
2
55
spent almost two hours figuring out exactly where the galaxy brain scheme went wrong. in the end the workaround was to cut the trace anyway, sigh
2
1
38
this is kind of cute but it would be a lot more cute if not for the preceding frustration
ah well. i went with an OSHW device that had some serious flaws because i knew we could fix them, and we'll just get onto that now
2
2
36
Replying to
Fun fact: Pixel phones switched to Suzy-Q debug cables for the Pixel 2 and later but if you use a ChromeOS implementation of the cable, you'll only get status information from the firmware and secure element.
The phones use an undocumented extension for debugging Android itself.
1
3
github.com/Peter-Easton/a is our documentation on that. It's pretty simple when you actually know what you're supposed to do.
As far as I know, they still haven't pushed documentation to somewhere like android.googlesource.com/device/google/ (covers the old style Nexus and Pixel 1 debug cable).
1
1
There was something special of applying 3.36V to the microphone pin of an analog audio jack and having it turn into a serial console. I think various vendors copied it and it's probably still in use. Almost miss the random byte corruption from poor quality analog debug cables.
1
2
There was an anecdote I heard from a Google employee about how the manufacturers of the Nexus devices thought they were completely nuts for having them implement this. They couldn't understand having the option of enabling debugging on a production device, especially like this.