Problem installing /e/ on Samsung A3 2016

samsung-galaxy
build-issues

#1

Hi,

I followed instruction there : https://gitlab.e.foundation/e/wiki/en/wikis/device/a3xeltexx/install

but…

$ 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 don’t know how to solve this.
Help needed ^^


#2

Hi @Bud are you still facing an issue with the setup of the /e/ ROM?


#3

Nop… but I persevere :sweat_smile:


#4

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 ?

2/ I found that a version of Heimdall exists in 1.4.1 or 1.4.2 instead of the 1.4.0 that we find throw the wiki : https://bitbucket.org/benjamin_dobell/heimdall/downloads/?tab=downloads
Could it be more efficient ?

3/ PEBCAK ?


#5

Hi @rhunault please can you check the details put here by @Bud. He is having an issue with a Samsung install.


#6

Hi @Bud,

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.


#7

Hi @rhunault,

Thanks for your help.
I’ll contact you on Telegram (in french) if needed.

I hope to share the problem solved soon there ^^


#8

Heimdall 1.4.2 seems to be the solution for the Samsung Galaxy A3 2016.

/e/ is now installed but reboot in a loop… :frowning:
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 :sob:


#9

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.

My initial problem is solved.

Thank you all :wink:


#10

Happy to hear that. Enjoy!


#11

Hi Bud,

I have the same phone and the same problem with WiFi. Do you solved it?
Whats about GPS at Magic earth? My phone reboot in a loop, too.


#12

Hi @Adriano,

I took the time to be precise on each of this points.

  1. Reboot when connected on Wifi : not solved
  2. GPS/Magic Earth (with data connction without wifi)
  • 1st test : I saw the map zooming on my position \o/… and reboot :frowning:
  • 2nd and other tests : I just see the loader and the phone reboot each time
    So same problem
  1. GPS/Magic Earth without any data connection : it locate me

It seems to have a problem with internet connection in many ways but next to that I can :

  • surf on web pages
  • consult weather via the weather app
  • check my emails
  • and share the connection creating a Wifi Hotspot (The other devices using it deeply -> no reboot :neutral_face:)

It’s difficult to understand exactly what is the problem


Samsung Galaxy A3 restarts when connected to WLAN
#13

@Bud

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 :sleepy:
Lets hope they will be solve the problem soon.:pray:

It´s good to know, to have someone else in the same situation. :sweat_smile:


#14

Hi! Is the reboot when connected on wifi bug solved? I cannot find any issue on GitLab about it.

I would like to test /e/ on an A3 but am waiting for this bug to be solved before compiling trying to compile Heimdall 1.4.2. :wink:


#15

There is a similar issue here and as yet not resolved. Do not have an ETA on this. F.Y.I @rhunault


#16

Hi,

I confirm after testing the last version and it still reboot if :

  • I use wifi
  • I use GPS and mobile data at the same time

#17

This wifi issue is still relevant?
If yes we could consider A3 2016 build as unusable


#18

Maybe someone should try to build /e/ using the LOS device tree that works without Docker and test this issue out.


#19

@Manoj I tried to but I failed. I have a LineageOS unofficial working well (not perfectly) on it.
I’m interested in learning who to move forward.


#20

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 & @harvey186 here 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.