LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)
-   -   issues with Heimdall on Arch Linux (https://www.linuxquestions.org/questions/linux-general-1/issues-with-heimdall-on-arch-linux-4175599836/)

TheEzekielProject 02-15-2017 02:02 PM

issues with Heimdall on Arch Linux
 
Hello all,

I am having a couple issues using Heimdall on Arch Linux and am hoping someone with more experience than I can help. I am trying to flash a kernel on my Galaxy S5 (kltetmo)
The first command I ran was:

Code:

heimdall flash --KERNEL zImage  --verbose
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...
Protocol initialisation successful.

Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...

Note that I only included the errors and removed duplicates of them. Also note that my phone is apparently detected as an S4. I would think this could be part of the problem but I could find nothing about Heimdall detecting phones improperly or how to fix such an issue

After this failed I uninstalled Heimdall from the main package repository of my distribution and then compiled and installed Heimdall via the AUR (Arch User Repository) and tried the same command again as I saw some users had better success with their own compilations of Heimdall. At this point it was successful in downloading the PIT, but I still received the same WARNING and ERROR in addition to
Code:

ERROR: Partition "kernel" does not exist in the specified PIT.
Ending session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...

I tried this command with both --kernel and --KERNEL as I saw in other threads of similar problems that heimdall is case sensitive, this made no difference however.
I then ran
Code:

heimdall print-pit
and found that there is indeed no partition with the name kernel or KERNEL.
I then tried downloading a PIT from elsewhere and tried to flash adding the --PIT option to my command but received the same output as above.
After a little more research I found that the partition name might be something else, but I found no way of determining what it might be. Obviously I can look through the output of print-pit, but I am not sure which is the proper partition and don't want to flash blindly.

Does anyone have any ideas? Or know the proper name of the partition for the Galaxy S5?

TheEzekielProject 02-15-2017 03:21 PM

After reading about other related issues, it seems that the operation of Heimdall has indeed changed and the partition name is not necessarily "kernel" for my device. But I am still unsure of how to determine what partition I need to flash. Will update as I learn more


All times are GMT -5. The time now is 03:46 AM.