Error de Heimdall ¡Falló la inicialización del protocolo! en Ubuntu

Yo también tuve un problema similar. Añadí la regla udev como se sugiere en GitHub (enlace anterior), pero el teléfono seguía sin descargar. Entonces encontré otra solución sencilla en GitHub:

1. Desconecte el cable USB.
2. Configurar el flash en Heimdall Frontend o en la línea de comandos.
3. Inicie el teléfono en el modo de descarga.
4. DESPUÉS de que esté en modo de descarga, conecta el USB y flashea inmediatamente.

Ha funcionado a las mil maravillas.

Yo estaba experimentando el mismo problema, y encontré una solución que me funcionó en un comentario en Número 228 de Heimdall .

El problema para mí era que udev reservaba el teléfono como módem cuando lo conectaba. Si ejecuta dmesg y ve una línea que dice "Este dispositivo no puede hacer llamadas por sí mismo. No es un módem", entonces esto podría funcionar para usted.

Como Root, cree un archivo llamado /etc/udev/rules.d/79-samsung.rules con el siguiente contenido:

ATTRS{idVendor}=="04e8", ENV{ID_MM_DEVICE_IGNORE}="1"

Luego reinicie udev con "sudo service udev restart", y desenchufe/reenchufe el dispositivo, y puede intentar instalar de nuevo.

Si eso no funciona o si es un problema diferente, puedes editar tu pregunta para añadir la salida de estos comandos:

heimdall detect --verbose --usb-log-level debug
sudo heimdall print-pit --verbose --no-reboot

Tuve problemas similares, resultó que sólo funcionaba con heimdall v1.4.2 en mi sistema linux mint 19

LA SITUACIÓN CON HEIMDALL 1.4.0:

OS:LinuxMint 19 (tara) Kernel 4.20.0-042000-generic

heimdall flash --REOVERY /home/user/Downloads/twrp-3.3.1-0-gts210vewifi.img --pit /home/user/s2a.pit --no-reboot --verbose 
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
      Manufacturer: "Sasmsung"
           Product: "MSM8952"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 82
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 01
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...

    heimdall download-pit --output s2.pit --verbose
    Heimdall v1.4.0

    Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
    http://www.glassechidna.com.au/

    This software is provided free of charge. Copying and redistribution is
    encouraged.

    If you appreciate this software and you would like to support future
    development please consider donating:
    http://www.glassechidna.com.au/donate/

    Initialising connection...
    Detecting device...
          Manufacturer: "Sasmsung"
               Product: "MSM8952"

                length: 18
          device class: 2
                   S/N: 0
               VID:PID: 04E8:685D
             bcdDevice: 0100
       iMan:iProd:iSer: 1:2:0
              nb confs: 1

    interface[0].altsetting[0]: num endpoints = 1
       Class.SubClass.Protocol: 02.02.01
           endpoint[0].address: 82
               max packet size: 0010
              polling interval: 09

    interface[1].altsetting[0]: num endpoints = 2
       Class.SubClass.Protocol: 0A.00.00
           endpoint[0].address: 81
               max packet size: 0200
              polling interval: 00
           endpoint[1].address: 01
               max packet size: 0200
              polling interval: 00
    Claiming interface...
    Setting up interface...

    Initialising protocol...
    WARNING: Control transfer #1 failed. Result: -9
    WARNING: Control transfer #2 failed. Result: -9
    WARNING: Control transfer #3 failed. Result: -9
    WARNING: Control transfer #4 failed. Result: -9
    WARNING: Control transfer #5 failed. Result: -9
    WARNING: Control transfer #6 failed. Result: -9
    ERROR: Failed to receive handshake response. Retrying...
    ERROR: Failed to receive handshake response. Retrying...
    ERROR: Failed to receive handshake response. Retrying...
    ERROR: Failed to receive handshake response. Retrying...
    ERROR: Failed to receive handshake response.
    ERROR: Protocol initialisation failed!

    Releasing device interface...

EL ARREGLO:

...encontré este útil artículo e instalé Heimdall v1.4.2

CÓMO INSTALAR LA VERSIÓN 1.4.2 DE HEIMDALL EN UBUNTU 16 Y SUPERIORES

para instalar la ver. 1.4.2 haga lo siguiente:

sudo apt purge heimdall-flash
sudo apt install build-essential cmake zlib1g-dev qt5-default libusb-1.0-0-dev libgl1-mesa-glx libgl1-mesa-dev
cd ~
wget https://gitlab.com/BenjaminDobell/Heimdall/-/archive/master/Heimdall-master.tar.gz
tar -xvf Heimdall-master.tar.gz
cd Heimdall-master/
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make
sudo mv ./bin/heimdall* /usr/local/bin

comprobar el éxito con

heimdall version
v1.4.2

Después de esta operación, el comportamiento de la bahía cambió de la siguiente manera:

heimdall flash --RECOVERY /home/user/Downloads/twrp-3.3.1-0-gts210vewifi.img --pit /home/chris/s2.pit --no-reboot --verbose 
Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
      Manufacturer: "Sasmsung"
           Product: "MSM8952"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 82
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 01
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...

Some devices may take up to 2 minutes to respond.
Please be patient!

WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.

WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Downloading device's PIT file...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
PIT file download successful.

Uploading RECOVERY
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
0%WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...

7%

14%

21%

28%

35%

42%

49%

56%

63%

70%

77%

85%

92%

99%

100%
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
RECOVERY upload successful

Ending session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...

Releasing device interface...

antes de la operación desenchufé y volví a enchufar la tablet

para poder flashear el TWRP

HAPPY

Esto me ocurrió en la v1.4.1. Hay algunas formas de solucionarlo:

1. Asegúrese de tener la última y mejor versión de Heimdall

2. Instala todo esto:

   sudo apt-get install build-essential cmake zlib1g-dev qt5-default libusb-1.0-0-dev libgl1-mesa-glx libgl1-mesa-dev

3. Reinicie su ordenador

4. Intenta conectarte en un puerto USB diferente - ¡3 de mis puertos USB no funcionaban, y uno sí!

Si ninguna de las respuestas anteriores funcionara, la respuesta podría ser tan tonta como lo fue para mí.

Dos cosas que quizá debas probar antes de golpear tu cabeza contra la pantalla:

Posible solución 1: Reinicia en modo download sin tener el USB conectado y sólo conéctalo después de haber pulsado el botón que te permite seguir embarcado en este peligroso viaje (botón de subir volumen supongo). Después, si no lo has hecho ya, sustituye los drivers por los de Zadig y Heimdall puede que funcione. Supongo que esta fue la solución para mí, pero también podría haber sido...

Posible arreglo 2: Reinicie su dispositivo móvil después de reemplazar los controladores con Zadig. Sí, super tonto, pero esto podría haber sido fácilmente la solución (ya que la primera solución me obligó a reiniciar).

Espero que nadie se rompa el cráneo.