Yeah, lots of them. ![]()
Which of it is Test-Point pins?
All, respectively none of them! ![]()
Seriously, real test-points would be labelled TPx.
What you see are five groups of pads:
- The two pads in front of the SD-card slot:
BOOTandBOOT-PWR(boot power) - Four pads to the right of the internal SIM-card slot:
GND(ground),DN(D-),DP(D+) andVBUS(bus voltage)
This is most likely a USB 2 port, if you measure betweenGNDandVBUSwith a multimeter, there should be ~ 5 volts. - Three pads in front of the camera module:
TX(transmit),RX(receive) and GND
This is a serial interface, most likely RS232-alike. The issue with serial interfaces of smartphones is, that you don’t know (without documentation), which voltage levels it is using (sure not the specified +12V / -12V, but it can be +5V / 0V, +3,3V / - 3,3V etc.), and if the signals on Rx & Tx are inverted or not. - Behind the battery connector, there are
VBAT(battery voltage),GNDandTEMP(temperature, which is connected to a PTC resistor to measure the battery’s internal temperature).
These pads are directly connected to the three pins of the battery connector. - There are three more pads slightly hidden under the flat ribbon cable in the small connector to the right: I can read
PWK, but not the other two, and have no idea what they are for.
As the device is currently under the control of an MDM (mobile device management), and you do not seem to have a way to ask it to be switched off, you are looking for a way to re-flash it. Either of the first three groups of pads (the USB-port, the serial interface and the two boot-pads) may provide a way to achieve that, but it has to be properly documented. If you are doing something wrong (e.g., applying a too high voltage to the Rx pad, but you don’t know what constitutes “too high” without documentation) you might hard-brick the device (i.e., destroy its electronics). The safest of the three is the USB interface: You may connect it to a computer and see what is there (e.g., by lsusb on Linux); still you would have to have an idea what to do with the USB-device (maybe it replies to fastboot run on an attached computer).
HTH