Instalar Lineage OS no Samsung Galaxy S4 e S5, Heimdall Problemas -- rom-flashing campo com samsung-galaxy-s-4 campo com stock-android campo com samsung-galaxy-s-5 campo com lineageos camp android Relacionado O problema

Install Lineage OS on Samsung Galaxy S4 and S5, heimdall problems


1
vote

problema

português

Estou tentando instalar o sistema operacional Lineage no meu Samsung Galaxy S4 e S5, seguindo as instruções sobre https://wiki.lineagos.org/devices/jfltexx/install

Eu instalei a linhagem com sucesso para um S4 antes, usando estas instruções, então eu não entendo o que está acontecendo.

Ambos S4 e S5 exibem o mesmo problema.

Estou preso em um estágio muito cedo (passo 4): em vez de 'substituir o driver' eu recebo a legenda 'reinstalar o driver' no botão (Zadig v2.0.0.147). Eu acho que é porque eu fiz isso antes e está usando o mesmo driver (também para o S5 ???). Então talvez tudo bem.

Nas instruções, não há nada sobre alterar o driver de destino e posso instalar qualquer um deles com sucesso. No entanto, nenhuma das opções funciona ao chegar ao próximo passo, executando heimdall print-pit

Aqui está o resultado para cada driver:

winusb v6.1.7600.16385

  Initialising connection... Detecting device...       Manufacturer: "Sasmsung"            Product: "MSM8960"              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 libusbx: error [windows_transfer_callback] detected I/O error 87: [87] The param eter is incorrect. ERROR: Failed to send data: "ODIN" Releasing device interface...    

libusb0 (v1.2.5.0)

  Initialising connection... Detecting device...       Manufacturer: "Sasmsung"            Product: "MSM8960"              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: -1 WARNING: Control transfer #2 failed. Result: -1 WARNING: Control transfer #3 failed. Result: -1 WARNING: Control transfer #4 failed. Result: -1 WARNING: Control transfer #5 failed. Result: -1 WARNING: Control transfer #6 failed. Result: -1 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...    

libusbk v3.0.4.0

  Initialising connection... Detecting device...       Manufacturer: "Sasmsung"            Product: "MSM8960"              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...    

Eu tentei isso em outra máquina Windows também e recebo o mesmo problema. Então, entre dois computadores e dois telefones eu sempre fico preso no mesmo lugar. Que só deixa a raiz do problema para se sentar entre as costas da cadeira e o teclado - o que estou fazendo de forma errada?

Outras pesquisas sugerem problemas de driver USB, mas que aponta para Zadig / Heimdall, não é?

english

I'm trying to install Lineage OS onto my Samsung Galaxy S4 and S5, following the instructions on https://wiki.lineageos.org/devices/jfltexx/install

I've successfully installed Lineage to an S4 before, using these instructions, so I don't understand what's going on.

Both S4 and S5 exhibit the same issue.

I'm stuck at a very early stage (step 4): Instead of 'Replace Driver' I get the caption 'Reinstall Driver' on the button (Zadig v2.0.0.147). I figure that's because I did it before and it's using the same driver (also for the S5???). So perhaps that's fine.

In the instructions there is nothing about changing the target driver and I can install any of them successfully. However, none of the options work when getting to the next step, running heimdall print-pit

Here is the result for each driver:

WinUSB v6.1.7600.16385

Initialising connection... Detecting device...       Manufacturer: "Sasmsung"            Product: "MSM8960"              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 libusbx: error [windows_transfer_callback] detected I/O error 87: [87] The param eter is incorrect. ERROR: Failed to send data: "ODIN" Releasing device interface... 

libusb0 (v1.2.5.0)

Initialising connection... Detecting device...       Manufacturer: "Sasmsung"            Product: "MSM8960"              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: -1 WARNING: Control transfer #2 failed. Result: -1 WARNING: Control transfer #3 failed. Result: -1 WARNING: Control transfer #4 failed. Result: -1 WARNING: Control transfer #5 failed. Result: -1 WARNING: Control transfer #6 failed. Result: -1 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... 

libusbK v3.0.4.0

Initialising connection... Detecting device...       Manufacturer: "Sasmsung"            Product: "MSM8960"              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... 

I've tried this on another Windows machine as well and I get the same issue. So between two computers and two phones I always get stuck in the same place. That only leaves the root of the problem to sit between back of the chair and the keyboard - what am I doing wrongly?

Further research suggests USB driver problems, but that points back to Zadig/heimdall, doesn't it?

              
     
     

Lista de respostas

0
 
vote
vote
Melhor resposta
 

Se você estiver em uma máquina Windows, não há necessidade de mexer com Heimdall - use odin em vez disso. É software proprietário, mas funciona quase fora da caixa (contanto que você tenha o driver oficial USB instalado).

odin3 v3.13.1 (download fornecido por Sammobile)

 

If you're on a Windows machine, there's no need to mess with Heimdall - use Odin instead. It's proprietary software but works almost out-of-the-box (as long as you have the official USB driver installed).

Odin3 v3.13.1 (download supplied by SamMobile)

 
 

Perguntas relacionadas

1  Alterar permissões de ADB para RW? [duplicado]  ( Change adb permissions to rw ) 
. Esta pergunta já tem respostas aqui : (2 respostas) ...

1  Instalando Lineageos  ( Installing lineageos ) 
Eu tenho uma guia S2 preso no 5.02 Eu queria atualizar o software para Lineagos Há muitas informações lá fora, mas nada que possa me ajudar. Algumas coisas pr...

2  Os aplicativos isentos da otimização de fundo serão afetados pela poupança de energia acionada com baixa bateria?  ( Will apps exempted from background optimization be affected by low battery trigg ) 
Eu desabilite a otimização para o WhatsApp. Eu quero limitar o WhatsApp somente se a bateria estiver baixa. O LineAgeos 14 ignora o whitelist na bateria fra...

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

2  O Cyanogen 13 atualizará para Lineage 14 e preservará aplicativos, dados etc?  ( Will cyanogen 13 update to lineage 14 and preserve apps data etc ) 
Eu tenho um s5 com touchwiz (isto é, rom) quero mudar, mas não quero ter que limpar e reinstalar tudo duas vezes mais. Há um cianogênio estável 13, e uma li...

1  O LT03WIFIUE constrói o mesmo que n1awifi?  ( Is the lt03wifiue build the same as n1awifi ) 
Eu tenho um SM-P600, quando download twrp mostra lt03wifiue para o nome de compilação. Quando eu baixei Linegeos, mostra n1awifi para o nome de compilação...

11  A entrada do Google Pinyin (IME) continua pedindo permissão de conta do Google  ( Google pinyin input ime keeps asking for google account permission ) 
Google Pinyin Entry é um método de entrada (IME) para chinês. continua me pedindo permissão de conta do Google. Eu nego o tempo todo, mas sempre volta e...

61  Onde os Lineageos armazenam arquivos de atualização?  ( Where does lineageos store update files ) 
Voltar em CyanogenMod, as atualizações foram baixadas para o diretório CMUpdater. Então eu poderia usar facilmente a recuperação do TWRP para instalar a atua...

2  Tela liga quando eu colero o telefone  ( Screen turns on when i bump phone ) 
Eu tenho um Moto E 2015 LTE (Surnia) executando Lineage OS, Android 7.1.1. Toda vez que eu colero o telefone, a tela liga-me para me dizer a hora. Não consigo...

0  SM-P600, LTE, WIFI ou 3G?  ( Sm p600 lte wifi or 3g ) 
Estou tendo um problema onde toda vez que eu inicializo uma rom em um SM-P600, eu recebo uma saída. Eu gostaria de saber como verificar qual versão eu tenho. ...




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