ERROR: Protocol initialisation failed! #413
Comments
|
Use version 1.4.2 - I recommend compiling yourself |
|
@JonnyTech I've built it from the repo, and I still get 1.4.1, built yesterday? When was 1.4.2 pushed? |
|
Okay, somehow built 1.4.2 from source, and now I'm detecting the device, but now I get this output, so I think it is the same error that I was getting before. |
|
Have you tried rebooting the phone and another USB port and/or cable? Which version of libusb do you have installed? Version 1.0.21 works for me: Make sure that you do not run Heimdall as root/sudo - I have had problems: What are the output of these commands: |
|
Tried reboot, other USB cable, ./heimdall detect came up with nothing, tried the 1st one again, and like before it detected on the original cable. Turns out my backup cable is faulty. After a complete sudo apt update && sudo apt upgrade, IT GOT THE PIT FILE! Here's my proof, though the .pit looks messy as hell, don't know if that's good? aliensonneptune@tinfoilhats:~/musicphone/Heimdall/bin$ ./heimdall detect
Device detected
aliensonneptune@tinfoilhats:~/musicphone/Heimdall/bin$ dpkg -l libusb-1*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=======================-================-================-====================================================
ii libusb-1.0-0:amd64 2:1.0.20-1 amd64 userspace USB programming library
ii libusb-1.0-0-dbg:amd64 2:1.0.20-1 amd64 userspace USB programming library development files
ii libusb-1.0-0-dev:amd64 2:1.0.20-1 amd64 userspace USB programming library development files
ii libusb-1.0-doc 2:1.0.20-1 all documentation for userspace USB programming
aliensonneptune@tinfoilhats:~/musicphone/Heimdall/bin$ ./heimdall download-pit --output pit.pit
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...
Claiming interface...
Setting up interface...
Initialising protocol...
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...
PIT file download successful.
Ending session...
Rebooting device...
Releasing device interface...
aliensonneptune@tinfoilhats:~/musicphone/Heimdall/bin$ cat pit.pit
v�4��COM_TAR2MSM8916��� xAPNHLOSNON-HLOS.bin�������MODEMmodem.bin����c��SBL1sbl1.mbn����g�@DDR���g��ABOOTaboot.mbn����w��RPMrpm.mbn���{��QSEEtz.mbn����QHEEhyp.mbn� �����FSG�
���� secsec.dat�
���� TPAD�
@�pEFSefs.img.ext4�����MODEMST1nvrebuild1.bin�����MODEMST2nvrebuild2.bin�����hBOOTboot.img���H�xRECOVERYrecovery.img������(FOTA�������7BACKUP������FSC����7�SSD��8@PERSISTpersist.img.ext4��xHPERSDATApersdata.img.ext4���KSYSTEMsystem.img.ext4���P@�CACHEcache.img.ext4��W@�HIDDENhidden.img.ext4��@]USERDATAuserdata.img.ext4remained�F�"PGPTpgpt.img�G�"�PITMSM8974.pit�H�2 MD5md5.img�I����!SGPTsgpt.imgI�W!����%C��4=��
����o!���p�%�<\T��R�q�
�I']enw��T?8�Z���{E��c�V�� ��E7O&���Q��B��4��4�����=�
ό�'�d�T}?����O����28��~�ڐe�V)G��<��`����y����d�"����A�9�e�!Q��'���)�&!ũ��Գ�M��Mq}�iah���H�
�2�樦E��<�K�6��OP�`G8��qА�?Ȁ ؖ,���ͫ������d5�+������0� |
|
So, the software is working correctly, you have a good connection to the device, the PIT file looks fine (it is not meant to be plain text, just wanted to make sure that you got something). Assuming that you have the correct IMG file for your device (not an Odin tar file - extract the IMG if you do) then you need to reboot your phone back into bootloader mode and do something like: Note that Can you post the complete console output, including the command line. |
|
I sent pretty much that command to my phone, and it rebooted, actually I tried doing it using -- instead of partition name, and accidentally flashed to 18, which was BACKUP, the phone still boots though. Here is the output of the console command, now how do I boot into the recovery? PS Sorry for being late to reply. |
|
Well done! To boot to recovery after flashing press Power, Volume Up and Home Buttons at the same time. If the phone boots normally then you pressed the buttons too late. At this point your newly flashed firmware has been overwritten by the system. So you need to flash it again from Heimdall in bootloader mode then hold the the buttons as it finished and restarts. Or you can use the |
|
I have tried booting, but it just shows the boot logo of my phone normally and some text in the top left. I thought it was loading TWRP in, but I left it for 20-25 mins then lost hope and held down all the buttons to boot normally? Is it the image or what? PS I'm using the latest image from here, have no idea if that's what I'm meant to be using? |
|
Okay, found an Odin-flashable TWRP .tar.md5, unpacked it, and found an .img file, whick looked flashable. Flashed it, worked flawlessly, booted TWRP, found my SuperSU .zip, installed.... aaaaaaaaand now I'm stuck on the loading screen :/ |
|
Has anyone else got this issue? I am having exactly the same thing: And my Heimdall buit from git, ubuntu 17.04. The phone is a Samsung Galaxy Note 3, SM-N900V. Any other solution would be amazing! |
|
Wiped dalvik/cache/tried hard resetting, SOMEBODY HELP, PLEASE, MY PHONE ISN'T LOADING IN. |
|
Did it boot after flashing TWRP, before installing SuperSU? |
|
Yes, and in the time since I last commented, I figured out that if TWRP still booted in, I could use ADB sideload to load in a new ROM, which could either solve my problems or make them worse. I'm an optimist. SO. I sideloaded a Lineage OS 14 ROM for the A500xx series, crossed my fingers and booted. Soon enough I was greeted by the amazing sight of a Lineage OS welcome screen. Currently sideloading opengapps for my device. Somehow flashing TWRP to root, and failing, then trying to fix it gave me face unlock and a stock (finally) theme? Anyway, couldn't have done it without your help, thanks a lot @JonnyTech |
|
@aliensonneptune - great result, glad that I could help, please close this issue now @spmp - do not hijack issues, please start your own using the new issue button |
|
@JonnyTech Sorry buddy, I thought it was the same issue as having the same error etc. Will start a new issue 8) |
|
Same problem here, "Protocol initialisation failed". I've noticed though that the first TL;DR only the first command after booting into download mode works! |
|
Thanks dandv! Indeed, only first command after booting into download works. |
|
um, help? I have the same error but I'm trying with the kernel is there any solution please? I'm trying to root my samsung A2 core |
|
Did you issue that command directly after booting the phone into download mode? If you read this thread you will learn that only one command after each reboot works. |
|
owh, okay |
|
I have tried everything here, I always get: |
|
Are you sure that you are in odin/download mode?: https://www.androidsettings.net/samsung-galaxy-a2-core-download-mode/
|
|
You might also want to try a newer build from a fork with a few fixes. It may or may not help... |
surely |
|
Bootloader unlocked? Tried different cables and USB ports? |
|
oops, I forgot to unlock the bootloader, but still the same problem 😕
Le mer. 6 oct. 2021 à 23:25, JonnyTech ***@***.***> a écrit :
… Bootloader unlocked? Tried different cables and USB ports?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#413 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR72PF4FRMRRHZT7V5L22HDUFTEFRANCNFSM4DYBGFIA>
.
|
|
I am trying "only" to Heimdall version 1.4.2 and libusb versions: Heimdall can see the device: Anything else I can try? |
|
I have written more about this error here: Troubleshooting: Heimdall Fails at Initialising Protocol In short:
|
|
Possibly same issue as fixed by PR #478 |
Have been trying for 3 hours to flash TWRP to a SMA500FU, and I don't know if it's a problem with the fact it's an A5, or if it's the build I'm using or what?
Here's the output of detect, and download-pit.
aliensonneptune@tinfoilhats:/$ sudo heimdall detect Device detected aliensonneptune@tinfoilhats:/$ sudo heimdall download-pit --output pit.pit 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... aliensonneptune@tinfoilhats:/$Can anyone help me?
PS, I'm an android noob, only been using it for 4 weeks.
PPS, I'm on a USB3, and the phone is on the 6.0.1 UD.
The text was updated successfully, but these errors were encountered: