Serial debugging:Cable schematics
This page contains schematics for serial cables, as well as device support tables and basic build instructions. For more information about serial debugging, visit the Serial debugging page.
- 1 microUSB/Carkit debug cable
- 2 Nexus debug cable
- 3 Mediatek USB debug cable
- 4 Suzy-Q debug cable
- 5 Per manufacturer/series
- 6 Specific devices
- 7 See also
microUSB/Carkit debug cable
Many devices with microUSB ports have the serial port multiplexed with the micro/mini USB connector, initially implemented as part of carkit standard. The Replicant project has a page dedicated to serial on Galaxy Nexus using this cable.
NOTE: "TX" and "RX" on this image refer to the TX and RX pins on your UART board.
Note that some devices and MUICs require a resistor with a different resistance than 150KΩ. To find the correct resistor value, check your device's wiki page, the MUIC page or follow the guide in Serial debugging#Finding the UART ports on your device.
|Tip: If you don't have the exact resistor you need for the cable, you can combine multiple similar resistors (for example 3 56kΩ for ~150kΩ). MUICs typically have a small margin of error where they'll still detect the correct resistance and switch to the right mode even if the value is a bit off.|
Nexus debug cable
Some Nexus phones, as well as Pixel phones with headphone jacks, multiplexed the serial debug lines with the headphone audio lines. To switch it into serial mode you have to supply -3V to the mic port. The UART lines themselves are 1.8V. If you use a 3.3V usb-to-uart adapter the signal from the phone will probably work, for the TX side you have to add a resistor divider to lower the voltage for the phone. Here's the schematic for a Nexus debug cable:
This cable has been tested with:
- Google Nexus 5 (lg-hammerhead)
- Google Nexus 5X (lg-bullhead)
- Google Pixel (google-pixel)
- Google Nexus 9 (htc-flounder)
It should work fine with:
- Nexus 7 2013 (flo)
- Google Pixel 3a and 3a XL (sargo/bonito)
- Google Pixel 4a (sunfish)
- Google Pixel 4a 5G (bramble)
The Nexus 7 2012 (grouper) does not work with this setup and likely does not have any serial UART capabilities at all.
Google open sourced their own debug cable design in the AOSP repository.
NT: You will have a better luck with FTDI based serial cable.
Mediatek USB debug cable
Some Mediatek devices expose an 3.3V uart interface at the usb port when a special Mediatek debug cable is attached to the device while booting
The schematic for this debug cable is the same as the Nexus USB debug cable above, except that the ID pin shouldn't be connected.
Suzy-Q debug cable
The Suzy-Q debug cable isn't strictly a serial debug cable, it accesses the Closed Case Debugging system, it can access multiple busses on the device. This system was originally developed to debug chromebooks but has been used in the newer Pixel phones. Details for the Closed Case Debugging system can be found at https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging.md
The official SuzyQable from Google has an 2 port USB hub into the cable itself, one port connects to the normal usb lines in the USB-C connector and the other port connects to the CC1/RFU1 pair like the diagram above, this way you can use both interfaces at the same time. The debug mode with the cable also only works on one of the two orientations in the USB-C socket. The official cable has a "DBG" mark on the C connector that should be facing up when plugged into the device. The other way around it will act as a normal USB cable.
That cable can be used with ChromeOS based devices for serial access.
See this page.
Some Motorola Devices
On here, find your device, and download and extract the file,then:
- open the one contains schematics.
- search keyword
*_DBG_UART_*) and see where it goes to(usually it's
- in some device(like
motorola-harpia),tx and rx will connect to a test pad(
TP_*),which makes it easier to access.
- in some device(like
- find it in board layout and on the device.
The Flame has open UART pads that are accessible underneath the outer and inner covers.
- TX - red
- GND - green
Pull-ups/downs are unnecessary, hook straight up to any FTDI/USB-to-serial.
See the following links:
Samsung Galaxy S7 and S5
See this guide. It worked almost exactly for the S5, only kernel MUIC driver was in another directory.
Motorola Droid 4
A off-the-shelf USB-TTL Adapter with 3.3V signal level can be used together with a MicroUSB connector to access the phone's UART. By using a standard MicroUSB <-> USB A cable and just combine a USB jack with a cheap chinese USB-TTL adapter is space-saving and allows you to use the same MicroUSB cable to access the device in USB mode
Much like other devices, solder to the Tx test point as shown, as well as a ground point (I used a screwhole). You should see bootloader logs. this commit enables UART output from the mainline kernel.
Google Pixel "Android Debug Cable"
While reported online that a "Suzy-Q" cable can be used for Android-based Pixel devices, the cable available from Sparkfun, the SuzyQable, is not the right cable for debugging Pixel phones. They are using a different incompatible scheme[How?]. On Pixel 2 devices they will not work at all, and on Pixel 3, it is reported they show the console of the Titan M chip only.
Serial access for the Pixel 2, 3 and 4 (unverified with 5) can instead be achieved using the following Android Debug Cable. Note that using a pass-through breakout board is not mandatory, but is helpful to keep the serial console active while using ADB.
This cable has been tested with:
- Google Pixel 2 XL (google-taimen)
- Google Pixel 4 XL (coral)
This cable should work fine with:
- Google Pixel 2 (walleye)
- Google Pixel 3/3 XL (blueline/crosshatch)
- Google Pixel 4 (flame)
This cable might work with:
- Google Pixel 5 (redfin)