A inicialização do protocolo de erro Heimdall falhou! no ubuntu -- yanogenmod campo com samsung-galaxy-s-5 campo com heimdall camp android Relacionado O problema

Heimdall Error Protocol initialisation failed! on Ubuntu


5
vote

problema

português

Eu quero instalar o CyanogenMod no meu Samsung Galaxy S5. Eu baixei a versão e fiz as etapas excactas do Wiki. Mas quando tento piscar com Heimdall, recebo este erro:

  Ubuntu-Laptop:~/Downloads/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte$ sudo heimdall flash --RECOVERY boot.img --no-reboot Heimdall v1.4.1  Copyright (c) 2010-2014 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... Claiming interface... Setting up interface...  Initialising protocol... ERROR: Protocol initialisation failed!  Releasing device interface...     

Eu não encontrei nada com o Google. Por favor ajude.

obrigado.

Inglês Original

I want to install CyanogenMod on my Samsung Galaxy S5. I'd downloaded the version and did the excact steps from the wiki. But when I try to flash with Heimdall I get this error:

Ubuntu-Laptop:~/Downloads/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte$ sudo heimdall flash --RECOVERY boot.img --no-reboot Heimdall v1.4.1  Copyright (c) 2010-2014 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... Claiming interface... Setting up interface...  Initialising protocol... ERROR: Protocol initialisation failed!  Releasing device interface...  

I didn't find anything with Google. Please help.

Thanks.

        

Lista de respostas

6
 
vote

Eu estava experimentando o mesmo problema, e encontrei uma solução que funcionou para mim em um comentário sobre Heimdall questão # 228 .

O problema para mim foi que o UDEV estava reservando o telefone como um modem quando eu conectou. Se você executar o DMESG e ver uma linha que diz "Este dispositivo não pode fazer chamadas por conta própria. Não é um modem." , então isso poderia funcionar para você.

Como root, crie um arquivo chamado /etc/udev/rules.d/79-samsung.rules com o seguinte conteúdo:

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

Em seguida, reinicie o UDEV com "Sudo Service Service Udev Reiniciar" e desconecte / replique o dispositivo, e você pode tentar instalar novamente.

Se isso não funcionar ou se for um problema diferente, você poderá editar sua pergunta para adicionar a saída desses comandos:

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

I was experiencing the same problem, and I found a solution that worked for me in a comment on Heimdall issue #228.

The problem for me was that udev was reserving the phone as a modem when I plugged it in. If you run dmesg and see a line that says "This device cannot do calls on its own. It is not a modem.", then this could work for you.

As root, create a file named /etc/udev/rules.d/79-samsung.rules with the following content:

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

Then restart udev with "sudo service udev restart", and unplug/replug the device, and you can try to install again.

If that doesn't work or if it's a different problem, you can edit your question to add the output of these commands:

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

Eu também tive um problema semelhante. Eu adicionei a regra de UDEV como sugerido no GitHub (link acima), mas o telefone ainda não baixaria. Então eu encontrei outra solução simples no GitHub:

    .
  1. Desconecte o cabo USB.
  2. Configure o flash no heimdall frontend ou linha de comando.
  3. Inicialize o telefone no modo de download.
  4. Depois de ser no plugue do modo de download no USB e flash imediatamente.

Funcionou como um encanto.

 

I also had a similar problem. I added the udev rule as suggested in GitHub (link above), but the phone still wouldn't download. Then I found another simple solution on GitHub:

  1. Disconnect the USB cable.
  2. Setup the flash in Heimdall Frontend or command line.
  3. Boot the phone into Download Mode.
  4. AFTER it's in Download Mode plug in the USB and flash immediately.

It worked like a charm.

 
 
1
 
vote

Isso aconteceu para mim no V1.4.1. Há algumas maneiras de corrigi-lo:

    .
  1. Certifique-se de ter o mais recente e amp; Maior versão de Heimdall
  2. instalar tudo isso:
 sudo apt-get install install build-essential cmake zlib1g-dev qt5-default libusb-1.0-0-Dev libgl1-Mesa-glx libgl1-mesa-dev  
  1. Reinicie seu computador
  2. tente conectar-se em uma porta USB diferente - 3 das minhas portas USB não funcionou, e uma fez!
 

This happened for me on v1.4.1. There's a few ways to fix it:

  1. Ensure you have the latest & greatest version of Heimdall
  2. Install all this:
sudo apt-get install build-essential cmake zlib1g-dev qt5-default libusb-1.0-0-dev libgl1-mesa-glx libgl1-mesa-dev
  1. Reboot your computer
  2. Try connecting on a different USB port - 3 of my USB ports didn't work, and one did!
 
 
   
   
1
 
vote

Se nenhuma das respostas acima funcionou, a resposta pode ser tão boba quanto acabou por ser para mim.

Duas coisas que você pode precisar tentar antes de bater a cabeça na tela:

correção potencial 1: reinicialização no modo de download sem ter o USB conectado e conecte-o somente após ter pressionado o botão que permite continuar a embarcar nesta jornada perigosa (botão de volume que presumo ). Depois, se você ainda não fez isso, substitua os drivers com Zadig e Heimdall poderá funcionar. Eu estou supondo que esta foi a correção para mim, mas poderia aswell ter sido ...

correção potencial 2: Reinicie seu dispositivo móvel depois de substituir os drivers com Zadig. Sim, super bobo, mas isso pode ter sido facilmente a correção (como a primeira correção exigia que eu reinicie).

Espero que ninguém fenda um crânio.

 

If none of the answers above worked, the answer might be as silly as it turned out to be for me.

Two things you might need to try before bumping your head into your screen:

Potential Fix 1: Reboot in download mode without having the USB plugged in and only plug it in after having pressed the button that allows you to continue embarking on this dangerous journey (Volume Up button I presume). Afterwards, if you haven't already done so, replace the drivers with Zadig and Heimdall might work. I'm guessing this was the fix for me, but it might aswell have been...

Potential Fix 2: Reboot your mobile device after replacing the drivers with Zadig. Yeah, super silly, but this might have easily been the fix (as the first fix required me to reboot).

Hope no one cracks a skull.

 
 
1
 
vote

Eu tinha problemas semelhantes, acabou por funcionar apenas com Heimdall v1.4.2 no meu sistema Linux Mint 19

A situação com Heimdall 1.4.0:

OS: linuxmint 19 (tara) kernel 4.20.0-042000-genérico

  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...    

a correção:

... Encontrei este artigo útil e instalado heimdall v1.4.2

como instalar Heimdall versão 1.4.2 no Ubuntu 16 e acima

para instalar ver. 1.4.2 Faça o seguinte:

  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    

Verifique o sucesso com

  heimdall version v1.4.2    

Após esta operação, o Bahavior mudou da seguinte forma:

  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 da operação que eu desligue e replugou o tablet

para que eu pudesse piscar o TWRP

feliz

 

I had similar issues, it turned out thet it only worked with heimdall v1.4.2 on my linux mint 19 system

THE SITUATION WITH 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... 

THE FIX:

...found this helpfull article and installed Heimdall v1.4.2

HOW TO INSTALL HEIMDALL VERSION 1.4.2 ON UBUNTU 16 AND UP

to install ver. 1.4.2 do the following:

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 

check success with

heimdall version v1.4.2 

After this operation the bahavior changed as follows:

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... 

before the operation I unplugged and replugged the Tablet

so I could flash the TWRP

HAPPY

 
 

Perguntas relacionadas

11  Erros de Heimdall ", falha: Falha ao detectar o dispositivo de modo de download compatível."  ( Heimdall errors error failed to detect compatible download mode device ) 
Ao tentar piscar uma galáxia S3 (ATT), eu recebo . erro: Falha ao detectar o dispositivo de modo de download compatível. Abaixo está o log, $ sudo hei...

7  Como piscar uma recuperação personalizada com Heimdall (sem tocar no sistema principal)?  ( How to flash a custom recovery with heimdall without touching the main system ) 
A primeira etapa recomendada em A instalação de CyanogenMod no Samsung Galaxy S está piscando uma recuperação personalizada como o clockworkmod ou o de repl...

5  A inicialização do protocolo de erro Heimdall falhou! no ubuntu  ( Heimdall error protocol initialisation failed on ubuntu ) 
Eu quero instalar o CyanogenMod no meu Samsung Galaxy S5. Eu baixei a versão e fiz as etapas excactas do Wiki. Mas quando tento piscar com Heimdall, recebo es...

1  Não é possível inicializar em recuperação (Samsung Galaxy S)  ( Cannot boot into recovery samsung galaxy s ) 
meu dispositivo gt-i9000 recentemente ficou preso em um bootloop , e agora estou tentando colocar CyanogenMod sobre ele, esperando que isso consertaria a sit...

0  No Galaxy S7, não pode desativar o bloqueio da Reativação da Samsung  ( In galaxy s7 cannot disable samsung reactivation lock ) 
Resumo Estou tentando instalar uma compilação personalizada de Lineageos seguindo as instruções aqui . Eu estava tentando carregar uma imagem de recuperaçã...

0  Erros de heimdall  ( Heimdall errors ) 
não funciona. Tentando instalar uma nova ROM de recuperação em um samsung s4 i9505 heimdall flash --recovery openrecovery-twrp-2.6.3.0-jgedlte.img Heimda...

2  Não é possível piscar a recuperação do CWM para GS3 sobre o estoque 4.1 com Heimdall  ( Unable to flash cwm recovery to gs3 over stock 4 1 with heimdall ) 
Eu quero roar e atualizar para 4.1 um Samsung Galaxy S3 apenas nãoboxizado. Depois de executar a atualização oficial do OTA com estoque Samsung Rom, tentei ...

11  "Falha ao detectar o dispositivo de modo de download compatível" no Mac Lion com Samsung Galaxy S2  ( Failed to detect compatible download mode device on mac lion with samsung gala ) 
Oi eu estou usando o wiki cyanmodgen para instalá-lo. Mas estou preso no primeiro passo. Sempre que faço sudo heimdall flash --kernel zImage Eu recebo: ...

7  'Falha ao acessar o dispositivo' ao tentar root Samsung Galaxy S 2.3.3 com Heimdall  ( Failed to access device when trying to root samsung galaxy s 2 3 3 with heimda ) 
Eu quero instalar o CyanogenMod no meu Samsung Galaxy S., a fim de fazer isso precisa ser enraizado primeiro, é claro. Para que eu segui o Explicação sobre o...

4  O que é um "arquivo pit"?  ( What is a pit file ) 
Tanto Heimdall quanto Odin têm opções para um arquivo pit. Da opção de Heimdall você pode encontrar, . Ação: print-pit Argumentos: [--file <filename>] ...




© 2022 pergunte.org All Rights Reserved. Casa de perguntas e respostas todos os direitos reservados


Licensed under cc by-sa 3.0 with attribution required.