$ heimdall print-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: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
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: 83
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: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #2 failed. Result: -7
WARNING: Control transfer #3 failed. Result: -7
WARNING: Control transfer #4 failed. Result: -7
WARNING: Control transfer #5 failed. Result: -7
WARNING: Control transfer #6 failed. Result: -7
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to send data: "ODIN"
Releasing device interface...
I redid the same operation on the A3 2016 without any changes.
I tried the same on a different phone, Samsung Galaxy Note 4, and I failed on the same command but a little bit further than with the A3 :
[...]
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...
I have now 3 questions :
1/ My OS is Ubuntu 18.04.02 (64bits) and I choose ubuntu13.04-heimdall_1.4.0-0_amd64.deb that seemed to be the closest. Was I right or I have to use an other one ?
You are pointing the source of your issue. Heimdall v1.4.0 is the last package available, but v1.4.2 is the last version. Unfortunately, for the moment, the only way to install this version is to build it. Instructions are located at the end of this page (“Appendix B - Installing Heimdall Suite from Source”).
Feel free to contact me on Telegram (@rhunault) if you need help.
Heimdall 1.4.2 seems to be the solution for the Samsung Galaxy A3 2016.
/e/ is now installed but reboot in a loop…
1st boot : I choose language et setup my Wifi and… reboot
since that, on the screen “emergency call or next” it’s freezing 5 secondes and reboot in a loop
Ok! Install is ok.
It is just a problem with data connection : if connected to a WiFi, it does not support it, except if it is a very low bandwidth. Not tested with SIM card yet.
I did exactly the same tests and got also the same results as you did.
In the meantime I updated my phone with the latest /e/ nightly Software from 6th April 2019.
But the problems are still there.
Unfortunately I don´t have any devices which are able to create a wifi hotspot
Lets hope they will be solve the problem soon.
It´s good to know, to have someone else in the same situation.
Hi @Bud, if you are interested in building the /e/ ROM for the Samsung A3 2016 you will find articles on our forum here ,here and here.
The method to be used in your case would be the non docker method as described by @andrelam & @harvey186here because you will need to do a few iterations with different device trees. We seriously need a device maintainer for the devices which have such issues especially the Samsung phones which are rebooting on connecting to wifi like the A3 .
I had contacted the developer from Lineage who had fixed the issue but he mentioned his sources have been upgraded to the latest Lineage version i.e. LOS 16.0 or Pie. Once we have completed our Pie upgrades of the source code and apps, which I expect should take the whole of June I will be contacting him again if required. Most probably the issue may resolve but we will still need to test it.