Heimdall错误协议初始化失败!在Ubuntu -- cyanogenmod 领域 和 samsung-galaxy-s-5 领域 和 heimdall 领域 android 相关 的问题

Heimdall Error Protocol initialisation failed! on Ubuntu


简体版||繁體版
5
vote

问题

中文

我想在我的三星Galaxy S5上安装CyanogenMod。我下载了这个版本,并从Wiki下了切换步骤。但是当我尝试用heimdall闪存时,我收到这个错误:

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

        

回答列表

6
 
vote

我遇到了同样的问题,我找到了一个解决问题的解决方案,即在 heimdall问题#228

问题是我的问题是,当我插入它时,Udev是在调制解调器中保留手机。如果你运行dmesg并看到一条说"这个设备无法自己打电话的行。它不是调制解调器。" ,那么这可以为你工作。

作为root,创建​​一个名为/etc/udev/rules.d/79-samsung.rules的文件,其中包含以下内容:

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

然后用"sudo service udev重启" 重新启动udev,然后拔掉/重新安装设备,您可以尝试再次安装。

如果这不起作用或者它是一个不同的问题,可以编辑问题以添加这些命令的输出:

  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

我也有类似的问题。我在GitHub中建议的UDEV规则添加了(上面的链接),但手机仍然不会下载。 然后我在GitHub上发现了另一个简单的解决方案:

  1. 断开USB电缆。
  2. 在heimdall前端或命令行中设置闪存。
  3. 将手机启动到下载模式。
  4. 在下载模式插上USB中,立即闪烁。

它像魅力一样。

 

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

这发生在我的v1.4.1上。有几种方法可以解决它:

  1. 确保您拥有最新&最大版本的heimdall
  2. 安装所有以下问题:
 sudo apt-get安装build-engions cmake zlib1g-dev qt5-defaul libusb-1.0-0-dev libgl1-mesa-glx libgl1-mesa-dev 
  1. 重新启动计算机
  2. 尝试连接在不同的USB端口 - 3个我的USB端口不起作用,其中一个人!
 

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

如果没有上述答案,那么答案可能会像我为我一样愚蠢。

在将头部撞入屏幕之前,您可能需要尝试两件事:

潜在修复1:在下载模式下重新引导,无需USB插入,只需在按下允许您继续开始此危险之旅(音量UP按钮)之后即可插入其中)。之后,如果您还没有这样做,请用Zadig和HeimDall替换驱动程序可能会使用。我猜这对我来说是修复,但它可能是......

潜在修复2:用zadig替换驱动程序后重新启动移动设备。是的,超级愚蠢,但这可能很容易被修复(因为第一个修复需要我重启)。

希望没有人破解头骨。

 

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

我有类似的问题,事实证明了它只用我的Linux薄荷19系统上的Heimdall v1.4.2工作

Heimdall 1.4.0:

操作系统:Linuxmint 19(Tara)内核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...   

修复:

...找到了这个有用的文章并安装了heimdall v1.4.2

如何安装Heimdall版本1.4.2在Ubuntu 16和Up

安装版本。 1.4.2执行以下操作:

  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   

检查成功
  heimdall version v1.4.2   

在此操作之后,巴哈维船更改如下:

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

在操作之前,我拔掉插块并加强平板电脑

所以我可以闪光twrp

快乐

 

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

 
 

相关问题

7  如何使用heimdall刷新自定义恢复(不触摸主系统)?  ( How to flash a custom recovery with heimdall without touching the main system ) 
在在三星Galaxy S 上安装CyanogenMod的安装是闪烁的ClockWorkMod或One的自定义恢复从复制品与命令一样: heimdall flash --kernel path/to/recovery.img 现在我觉得说明可能是误导性: 我已经完成了刚刚具有自定义恢复模式的第一步,而无需继续...

0  在Galaxy S7中,无法禁用三星重新激活锁  ( In galaxy s7 cannot disable samsung reactivation lock ) 
摘要 我正在尝试按照指令这里。当我被告知"恢复检查失败" 时,我试图使用heimdall加载恢复图像。事实证明,三星有一些被称为 reactivation lock ,但要禁用的设置我的手机上不存在。我实际上打电话给他们,他们说它已被谷歌的Android设备经理所取代,但是有明显的 阻止我加载恢复图像。 我无法由于声...

0  heimdall错误  ( Heimdall errors ) 
不起作用。 试图在三星S4 I9505上安装新的恢复ROM heimdall flash --recovery openrecovery-twrp-2.6.3.0-jgedlte.img Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Gla...

11  使用Samsung Galaxy S2,“未能检测兼容下载模式设备”  ( Failed to detect compatible download mode device on mac lion with samsung gala ) 
嗨,我正在使用cyanmodgen wiki来安装它。但我陷入了第一步。 每当我做 sudo heimdall flash --kernel zImage 我得到: Initialising connection... Detecting device... Failed to detect comp...

7  在尝试用Heimdall授权三星Galaxy S 2.3.3时,“无法访问设备”  ( Failed to access device when trying to root samsung galaxy s 2 3 3 with heimda ) 
我想在我的三星Galaxy S上安装CyanogenMod.为了做到这一点,它需要首先植根。因为我遵循了关于cyanogenmod wiki 给字母的说明。 但是,当我在命令提示符下执行 heimdall flash --kernel zImage 时,我得到以下反馈: D:SGSHeimdall>heimdal...

11  heimdall错误,“错误:无法检测兼容的下载模式设备。”  ( Heimdall errors error failed to detect compatible download mode device ) 
试图闪存Galaxy S3(ATT),我得到 错误:无法检测兼容的下载模式设备。 下面是日志, $ sudo heimdall flash --RECOVERY recovery.img Heimdall v1.4.0 Copyright (c) 2010-2013, Benjamin Dobell, Gl...

1  无法启动恢复(三星Galaxy S)  ( Cannot boot into recovery samsung galaxy s ) 
我的gt-i9000设备最近被陷入了靴子,现在我试图将cyanogenmod放入cyanogenmod在它上,希望这会解决这种情况。 我可以使用Heimdall在手机上安装ClockworkMod恢复,但截至今天,我无法启动恢复! 昨天一切正常工作,但是一旦我今天试图启动它,它就会陷入靴子上而不是要恢复! 我正在使用...

2  无法通过Heimdall将CWM恢复恢复到GS3 4.1  ( Unable to flash cwm recovery to gs3 over stock 4 1 with heimdall ) 
我想root并升级到4.1一个只有未封闭的三星Galaxy S3。 运行官方OTA更新与股票三星ROM,我试图遵循教程 here 带opensuse。 我从yast中安装了heimdall,并使用 --param 和 --recovery 选项运行 abcdefghijklmn0 选项,其中包含我为rooting的...

5  Heimdall错误协议初始化失败!在Ubuntu  ( Heimdall error protocol initialisation failed on ubuntu ) 
我想在我的三星Galaxy S5上安装CyanogenMod。我下载了这个版本,并从Wiki下了切换步骤。但是当我尝试用heimdall闪存时,我收到这个错误: Ubuntu-Laptop:~/Downloads/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte$ sudo he...

4  什么是“坑文件”?  ( What is a pit file ) 
heimdall和odin都有一个pit文件的选项。来自Heimdall的选项,您可以找到 action: print-pit 参数: [--file <filename>] [--verbose] [--no-reboot] [--stdout-errors] [--usb-log-level <non...




© 2022 it.wenda123.org All Rights Reserved. 问答之家 版权所有