Unable to flash SGS 5 #203
Comments
|
@gumbi2400 What Heimdall version? |
|
This would be using the latest Git build (1.4.1) as well as the stable 1.4.0. |
|
Could you please included the complete verbose output? Also, have you installed Kies on your Mac in the past? |
|
I haven't installed Kies (its a relatively fresh OSX install). Below is the pastebin with the verbose output: |
|
A quick update. I fired up USB Prober and got a bit more detailed logs from OSX. Not sure if it helps, but here you go: May 30 13:11:29.887 [1] AppleUSBEHCI::Found a transaction past the completion deadline on bus 0x1d, timing out! (Addr: 6, EP: 1) It looks like it's reaching out to the phone, and after setting up the connection, the phone stops responding. Again, not sure if it helps, but just thought I would throw that out there. |
|
Oh and I forgot to mention that it is being improperly identified as "MSM8960" When in reality it should be "MSM8974AC" |
|
@gumbi2400 The misreporting of the chipset is due to Samsung not updating the value in their secondary bootloader. This is surprisingly common, however it does not have any impact on the ability to flash your device. However, I've just made a new commit that might help help. Please pull the latest changes on the master branch, compile, and let me know if it works.. |
|
I gave it another try. I see the code change, it looks like it's probably the same issue. Here is the newest verbose output: I'll see if I can get more info from the OSX system logs. |
|
Finally got the system USB logs. AppleUSBEHCI::Found a transaction past the completion deadline on bus 0x1d, timing out! (Addr: 6, EP: 1) This just repeats quite a few times. Hope it helps. |
|
Same on Linux, logs: |
|
@ulidtko Your problem is different than gumbi2400's. Your flash is failing during protocol initialisation, whilst gumbi2400 gets past that point. This makes me think your problem is a result of a faulty USB cable or USB port/hub. If you could please try again with a different cable and USB port that would be great. If you continually get failures during protocol initialisation then please open another issue and include as much detail as possible (in particular your device model). |
|
@gumbi2400 Can you please try the latest commit on the master branch, I've made a change which I'm hoping will solve your problem. |
|
@Benjamin-Dobell tried with another cable, result is the same. Also, Your latest commit doesn't help too. Also, but yeah, that doesn't tell much. |
|
Looks like still the same error: Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna This software is provided free of charge. Copying and redistribution is If you appreciate this software and you would like to support future Initialising connection... iMan:iProd:iSer: 1:2:0 interface[0].altsetting[0]: num endpoints = 1 interface[1].altsetting[0]: num endpoints = 2 Initialising protocol... Beginning session... Some devices may take up to 2 minutes to respond. WARNING: Empty bulk transfer after sending packet failed. Continuing anyway... Downloading device's PIT file... Let me know if you want system logs as well. |
|
I've captured the USB traffic of the Heimdall session with my SGS5 using Wireshark: https://gist.github.com/ulidtko/f34303b9ef5c05e0faa4 The gist contains Heimdall's log with libusb debug logging enabled, a textual export of Wireshark capture, and the binary capture file itself. |
|
While this patch works for me with print-pit and flashing recovery, download-pit appears to be broken still. |
|
Regarding the timeout (-7) problem upon protocol initialization, that seems to be a driver related issue: With my G900F (S5), the problem goes away if I run wireshark/usbmon while trying to run heimdall. That's only a workaround and probably won't help resolving this bug, but maybe this information helps others... |
|
I also have problems getting heimdall to work with various GS5 (model SM-G900F) that I use. Protocol initialization and session start work for me, but the PIT download fails. My heimdall is my own build of the latest master, without the GUI. I am willing to provide timely updates on this as this is work-related for me. Complete log: |
|
@promovicz did you try the patch referenced above #225? |
|
@sshimko I just did and it worked flawlessly! Thanks for the tip! |
|
Chiming in again: I was able to download the pit file for my T-Mobile Samsung Galaxy S5 (SM-G900T aka kltetmo) using the fork of @sshimko (nice - btw is there a reason his changes haven't been pulled to master yet?) - however - flashing did not succeed. Here is the output - please let me know what I can provide that would help otherwise! (Apologies if this is old hat) |
|
@Astragalus based on the last line this is Linux right? Probably won't help, but could you try pull request #231? I was focused on OS X fixes for that one, but I was testing on both Fedora 20 and OS X and the fixes on OS X required further fixes to work on Fedora. Resolving those conflicts might impact other init problems. |
|
I am indeed on linux (Mint, fwiw) - I was working from your gs5 branch but so far none of the silly things I've tried have stopped it from timing out when waiting for the handshake response. I'll try merging in your osx stuff now and see what I can do... Many thanks @sshimko ! |
|
SM-G900T OSX Mavericks Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna This software is provided free of charge. Copying and redistribution is If you appreciate this software and you would like to support future Initialising connection... iMan:iProd:iSer: 1:2:0 interface[0].altsetting[0]: num endpoints = 1 interface[1].altsetting[0]: num endpoints = 2 Initialising protocol... Beginning session... Some devices may take up to 2 minutes to respond. Session begun. Downloading device's PIT file... ERROR: Failed to send request to end PIT file transfer! ERROR: Failed to send end session packet! Downloaded latest libusb, compiled and installed; again, same result. |
|
Hi @ALL, for what it's worth: A self-compiled heimdall from current master (as of 28.7.2016 - sorry, no commit ID...) had absolutely no problems with my SM-G900F (S5 international version/klte). I did have a bad USB port/cable combination (USB device resetting after every open()), but changing cables did the trick. What I did:
Hope this helps anyone! |
|
FYI I just had success using the commandline (not frontend) compiled from source 1.4.1 on Samsung Galaxy S5 G900F #348 (comment) |
I've been attempting to root my SGS 5 (International) on OSX. The device is detected, but when performing an action (e.g. print-pit) It will fail. The specific error I see when using verbose output is:
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
Looking at the OSX specific logs I see:
kernel[0]: USBF: 88081. 66 AppleUSBEHCI::Found a transaction past the completion deadline on bus 0x1d, timing out! (Addr: 6, EP: 1)
This is both with the stock cable, as well as an old one that is known to be a good cable that I've used in the past. I have also tried on multiple different laptops (both Apple) with the same results.
Please let me know if any additional information is needed.
The text was updated successfully, but these errors were encountered: