Peter-Easton/android-debug-cable-howto

Trying this on Redmi Note 11

Opened this issue · 3 comments

daeiron commented

Hi,
I have been trying this on my Redmi Note 11.
I have tried 3 different usb-serial adapters (ft232, cp2102,pl2303). Also changed cable and flipped connection.

Enabled these configs in kernel configuration:
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CONSOLE=y
CONFIG_USB_SERIAL_CP210X=y
CONFIG_USB_SERIAL_PL2303=y
CONFIG_USB_SERIAL_FTDI_SIO=y

But fastboot for this device doesn't have an enable UART option. So can't do that.
Any idea what else to try? Or where to go from here.

I want to be able to debug a non booting kernel.

samueldr commented

DO NOT

samueldr commented

The way this cable operates is through using SBU (sideband use) lanes on the Type-C connection.

These lanes can be connected (or not) to anything in any way. At worst, you can cause permanent damage to circuitry by using a cable not meant to be used on a particular device.

At best (when they add negotiation and such things) they do nothing.

The only way cables with SBU can be used, like this one, is if the device was made specifically for the cable. The "cereal" cable scheme used by Pixel devices is, as far as anyone knows, only used by pixel devices starting with the Pixel 2.

Guilher89 commented

Hi,
I have been trying this on my Redmi Note 11.
I have tried 3 different usb-serial adapters (ft232, cp2102,pl2303). Also changed cable and flipped connection.

Enabled these configs in kernel configuration:
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CONSOLE=y
CONFIG_USB_SERIAL_CP210X=y
CONFIG_USB_SERIAL_PL2303=y
CONFIG_USB_SERIAL_FTDI_SIO=y

But fastboot for this device doesn't have an enable UART option. So can't do that.
Any idea what else to try? Or where to go from here.

I want to be able to debug a non booting kernel.

Dear [daeiron],

I hope this message finds you well. I'm contacting you for information and guidance on compiling the SPES kernel. I am interested in understanding the compilation process and its specificities.

So that I can gain a more comprehensive understanding, I would like to ask you a few specific questions:

  1. Toolchain Used: Which toolchain (set of compilation tools) did you use to compile the SPES kernel? Was it a specific toolchain recommended by the manufacturer or one of your choice?

  2. Compilation Script: During the compilation process, did you use any custom kernel compilation script or a manufacturer-supplied script? If yes, could you share details about this script or its settings?

  3. Specific Settings: Were there any special settings or adjustments you needed to make when compiling the SPES kernel, especially related to specific hardware or optimizations?

  4. Issues or Challenges: While compiling the kernel, did you face any specific issues or challenges that you would like to highlight? How did you resolve these issues, if any?

If you are willing to share your experiences and knowledge about compiling the SPES kernel, I would be extremely grateful. Your information will be invaluable to my own compiling journey.

Please know that any details or guidance you can provide will be highly appreciated. If you prefer to share this information in a more private setting, I am happy to exchange private messages or emails, whichever is most convenient for you.

Thank you in advance for your help and collaboration. Your knowledge will be of great benefit.

Yours sincerely,
[K0WHITE]