Issues With Newer Samsung Bootloaders And Heimdall #209
Comments
|
got the exact same error. heimdall un-usable for me (linux) |
|
Is there any chance you’d be able to do the following for me on Windows?
This would help immensely in fixing support for these devices. |
|
On Sun, 22 Jun 2014, Benjamin Dobell wrote:
I have a Galaxy Note 10.1 2014 Edition (specifically, the SM-P607T) and I Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Silicon Valley |
|
Ben, I was able to get the log you were after thanks to a kind user who ran the steps you asked for. Hopefully this helps. Sent to your email. |
|
@Benjamin-Dobell |
|
@utkanos Thanks for the capture. Looking at the capture, I noticed that for some reason the device sends an empty bulk transfer to the computer right before the computer sends the packet to end the PIT transfer. So I've made a change to emulate this behaviour. However, it seems you were only getting that far with 1.4.0 and that 1.4.1 was failing earlier. Looking at this capture I see no reason why this particular device would fail before the end of the PIT transfer. It might be different for other devices though. Anyway, I've pushed a new commit to the master branch which includes the new behaviour that should fix the PIT transfer issue. If you could please retry with that commit and let me know how you go that would be great. |
|
@Benjamin-Dobell, thanks, I will test this and get back to you. A user named sytse made similar conclusions with the bulk transfer and PIT end session behavior and modified the source and was able to resolve the issue as well. I will play with both fixes and let you know what happens. Thanks very much for getting back with me on this! |
|
I just tested the latest commits, and I am still seeing issues. |
|
@Benjamin-Dobell slayher tested it and another user and they had the exact same experience. I am emailing you a diff file from the user that solved the issue for themself in the hopes that you can work with that to patch master. He's just removing some checks from happening and forcing a pit file instead of trying to read it from the device which does work but might not be the most elegant solution. I will send the file to your email, thanks for continuing to work on this. |
|
Hello all, i have the same problem with galaxy s3 L710 sprint |
|
@Benjamin-Dobell any update on this issue? Thanks. |
|
@Benjamin-Dobell Any updates? |
|
The patch from sshimko fixes recovery flashing for me on Galaxy S4 GT-I9506. I'm not able to boot into the recovery yet, but the heimdall flashing proceeds without any error. |
|
Hi - just randomly chiming in :) I tried the patch from sshimko and am still unable to download the pit file; I am getting "ERROR: Failed to receive handshake response. Result: -7" which is the same error I got before the change. My device is a (T-Mobile) Samsung Galaxy S5 SM-P900T. Alas! |
|
There seem to be multiple types of failures here. The patch fixes the issue wherein the session is successfully established, the PIT download has been initiated, then it fails. On OSX, it fails much earlier for me on both Mavericks and Yosemite, but seemingly in different ways. I believe they are distinct problems with different sources. @Astragalus which OS was this on? |
|
This was on Linux Mint 17, amd64, and I should add that the libusb I used was built from the git source. Please let me know if there's anything I can grab for you, I'm happy to help. |
|
I have problem flashing a Galaxy Tab Pro 8.4" as well. Version 1.4.0 exist with "libusb error -7" message, both on Mac OS X and on Ubuntu. Tried different computers with different USB cables. I've just compiled this day's Heimdall build. Still unable to flash. Verbose output follows: |
|
Same here, please investigate! My log is identical to many others here, won't spam now. |
|
Try #232 |
|
@tgalal I have changed the files as described to if (ReceiveBulkTransfer(nullptr, 1, kDefaultTimeoutEmptyTransfer, false) < 0 && verbose) and success = ReceivePacket(receiveFilePartPacket, kDefaultTimeoutReceive, receiveEmptyTransferFlags); and recompiled heimdall. The error is still the same though. |
|
|
Odin 3.07 worked from inside a VirtualBox VM running Win7 Ultimate x86, on the same Ubuntu 14.04 x64 host where Heimdall had failed. (It successfully flashed TWRP, which I used to install CM11). |
|
Same issue on ubuntu. To even get to the Error. Fixed that by changing heimdall/source/BridgeManager.cpp, line ~230 But still had the issue. |
|
Any update on this? I have a Galaxy Tab Pro 8.4" (SM-T320). |
|
Having this same problem with a Galaxy S5 Sprint, Arch Linux user here. Going to try passing my phone off to a VM. |
|
Identical problem when passing my phone off to a VM. I suppose I'll just live with the default OS. |
|
On SAMSUNG Galaxy S5 G900F $sudo ./heimdall print-pit --verbose Heimdall v1.4.1 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... Releasing device interface... |
|
@moismailzai Your method worked for me on a G900T. I did it from Windows, so of course I had to remove It wouldn't recognize the term "recovery" unless it was capitalized, and I needed to add |
|
@crabilld maybe since mine is refurbished, samsung may have put a newer recovery on it? i just cant get the pit file on windows ERROR: Failed to send request to end PIT file transfer! ............ |
|
not sure of the resolution here....why was this closed ? |
|
I was facing this issue on T-Mobile Galaxy Note 3. |
|
@sen4ik thank you very much for the windows binary. |
|
This happened for me on v1.4.1. There's a few ways to fix it:
|
|
@sen4ik Thanks so much for compiling and uploading that dude, saved me a lot of trouble! |
|
Hi, got it working under Fedora 23 (not sure all the packages installed are necessary, but it works): as root: then follow the instructions at the end of Linux/README, as normal user, and calling heimdall (as root) works for a Samsung Galaxy TabPro 8.4, where it didn't work previously with the packaged heimdall 1.4.1-5.fc23 Hope this helps someone, Eric |
|
@ericzolf : I had to do something very similar. I ended up building a new RPM/SRPM of what I cloned as of 20160603. That seemed to have fixed all the things. I had the same problem here as a lot of folks, but 1.4.1 (what Fedora ships) is just way old. The latest commits from master solved the problems I had. HTH! |
|
For what it is worth, I had this issue when my device was plugged into a USB3 port. Moving it to a USB2 port fixed it. |
|
I experienced this issue on OS X with JOdin3/Heimdall 1.4.0. My phone is Galaxy Alpha SM-G850M. Can anyone offer a guess as to a fork of the code I could try? @Benjamin-Dobell I installed your 1.4.1 unofficial dmg (hopefully it works as an upgrade; after the install, command line 'heimdall version' still gave 1.4.0) but it did not seem to resolve anything. |
|
Thanks to @sen4ik for the windows binary. It worked great and did not face "ERROR: Failed to send request to end PIT file transfer!"error. Device -Samsung Galaxy Tab Pro 8.4. |
|
Had the same issue using Heimdall with Ubuntu 14.04 x64, with a Galaxy S5. The SaburoJiro fork worked fine. |
|
FYI I just had success using the commandline (not frontend) compiled from source 1.4.1 on Samsung Galaxy S5 G900F #348 (comment) |
|
Having same problem with version 1.4.0 binaries downloaded from main web site with Samsung S5. #209 (comment) binary built by sen4ik worked! 👍 |
|
On Ubuntu 16.04 (KDE Neon really) #209 (comment) comment above did it for me (I was also using that other forked build, dunno if that mattered or not) |
|
Repo version (Ub.16.04 /64) gave this error; built version did not. Used CLI to flash SGN3, N900T, which seemed to work for all partitions, but could not overcome the secure boot error (a separate issue). Have read that Odin writes data to the MD5 partition with a private key. Would be great if that could be cracked. Much prefer using Heimdall. |
|
I hope I'm not spamming you with what may still be an existing issue , but I figured my specific variables may be useful info: I Flashed the stock ROM from Odin on Windows, and thought maybe it was the bricked phone causing the Heimdall issue, so just now I tried to flash the phone back on Debian with the Unofficial TWRP build for this phone and received the error again. From one Ben to another, |
|
i can confirm following is true in my case: For what it is worth, I had this issue when my device was plugged into a USB3 port. Moving it to a USB2 port fixed it.If you don't have a USB 2.0 port, you can try connecting via a USB 2.0 hub, as in my case |
|
The USB2.0 and re-insert the USB cable did the trick for me, too. (This is November 2017, and I am on klte.) |
|
Device: Samsung Galaxy Note 3 (hlte) Last night, I tried to flash a custom recovery using heimdall from apt repository of Subgraph OS, a Debian-based distro, without success. So, I followed the suggestions from this thread by uninstalling heimdall from apt and install the latest version from github instead and it just worked. The git commit id is 5377b62 . Thank you very much. |
|
Had the same issue with Samsung T700. Compiled my own Heimdall (1.4.2) and it worked. |
|
I'm not sure if the original purpose of this issue is still current: I've recently used heimdall 1.4.2 packaged in Fedora 27 and successfully flashed TWRP on a Galaxy S7 with Android 7, so it sounds to me like the issue is solved and should be closed. |
|
Meanwhile I found a way to solve it for me - that's why I deleted my post short after writeing.
It was something about my heimdall fronted thing. It's fine now, worked great. Thanks for your concern.
… Gesendet: Samstag, 30. Dezember 2017 um 18:00 Uhr
Von: "Eric L." ***@***.***>
An: Benjamin-Dobell/Heimdall ***@***.***>
Cc: anothernerd02 ***@***.***>, Comment ***@***.***>
Betreff: Re: [Benjamin-Dobell/Heimdall] Issues With Newer Samsung Bootloaders And Heimdall (#209)
I'm not sure if the original purpose of this issue is still current: I've recently used heimdall 1.4.2 packaged in Fedora 27 and successfully flashed TWRP on a Galaxy S7 with Android 7, so it sounds to me like the issue is solved and should be closed.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#209 (comment)
|
|
unfortunately, it's still broken. |
|
No joy here either, with a Galaxy Tab S2. |
|
I ran into the same issues with heimdall 1.4.0 running on linux which is still provided on the heimdall download page.
I've tried the latter and it worked for me because my distro provides version 1.4.1. |
|
I've ran into this a good while back, when I wanted to reflash my Galaxy S7. Running Heimdall 1.4.2 (compiled version here) works absolutely fine. Please, Mr Heimdall author sir, could you please get on with releasing an official new version? |
|
Worked after compiling 1.4.2 from source, and running the cli, aka NOT frontend. Had to try two different usb cables |
and others
Hi Ben,
Since Samsung has pushed some changes in their 4.4 OTAs for a few devices (hlte, i9506) heimdall, even 1.4.1 is unable to communicate with the device and retrieve a PIT or handshake properly at all.
Attached are some logs of the hlte with '4.4' Samsung Bootloader update
heimdall 1.4.0:
heimdall print-pit --verbose --no-reboot
Heimdall v1.4.0
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...
Manufacturer: "Sasmsung"
Product: "MSM8960"
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...
Attempt failed. Detaching driver...
Claiming interface again...
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.
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...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
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. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
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...
Re-attaching kernel driver...
and with heimdall 1.4.1:
heimdall print-pit --verbose
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...
Manufacturer: "Sasmsung"
Product: "MSM8960"
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...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
Thanks for looking into this when you can!
utkanos
edit: here is another device on 1.4.1 with this issue and slightly diff behavior:
heimdall print-pit --verbose
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...
Manufacturer: "Sasmsung"
Product: "MSM8960"
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!
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.
Releasing device interface...
The text was updated successfully, but these errors were encountered: