Hello,
I’m following the installation instructions at https://doc.e.foundation/devices/herolte/install to deploy the /e/ OS on my Galaxy S7 smartphone and I’m stuck at the step requiring to install a custom recovery.
Here the details of my configuration:
Android v8.0.0
Samsung Galaxy S7 - firmware SM-G930U - Exynos
OEM unlocking and USB debugging activated
I tried to install the example TWRP custom recovery.
I built Heimdall on my computer.
I executed without issue the following command:
clecoued@clecoued:~$ sudo heimdall print-pit
My issue appears when i execute the flashing command:
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.
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
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...
WARNING: Empty bulk transfer after receiving packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
PIT file download successful.
Uploading RECOVERY
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
0%WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
2%
4%
6%
9%
11%
13%
16%
18%
20%
22%
25%
27%
29%
32%
34%
36%
39%
41%
43%
45%
48%
50%
52%
55%
57%
59%
62%
64%
66%
68%
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
71%
73%
75%
78%
80%
82%
84%
87%
89%
91%
94%
96%
98%
100%
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
RECOVERY upload successful
Ending session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: Failed to unpack received packet.
ERROR: Failed to receive session end confirmation!
Releasing device interface...
My phone also displays the following message - SECURE CHECK FAILS - recovery
My phone is not rooted - I can’t execute adb shell command line as su
I made investigations on internet and it seems that this is a bootloader/frimware locking issue.
Did someone in the community face a similar problem ? Did you find a workaround ?
a lot of people do have issues with heimdall. I refer using the good old working fastboot methode.
Try:
boot into recovery using ‘adb reboot recovery’ or via hardware keys
when in download (fastboot) mode use this command:
‘fastboot flash recovery twrp-3.3.1-0-herolte.img’ from inside your TWRP folder (where your twrp img is stored)
normally you can run this command with normal user.
at least reboot again into recovery via hardware keys (you must do this to complete twrp install)
@OP: It looks like you might be ‘in jail’ (the 7-day lock triggered if you allow to boot to system after factory reset). Do you have any warnings in red in download mode? I thought that was the case for me a few days ago (the OEM unlock option was gone in the stock OS), but then I was unexpectedly able to flash TWRP after two days.
Thanks for your answer.
I tried the fastboot command line you suggested.
I got stuck on the message ‘< waiting for any devices >’.
There is no device when I execute fastbook devices with my device in Downloading mode.
reb77,
I have the following warning in Downloading mode:
in red -
ODIN MODE - HIGH SPEED
in grey -
QUALCOMM SECUREBOOT: ENABLE
SECURE DOWNLOAD: ENABLE
I hope it will unlock in the upcomming days
@archie
Damn, I did not check the supported model version !
However I should be able to install LineageOS at least on the smartphone.
You are welcome. @reb77 has written that Samsung doesn’t support fastboot, but I can’t believe that. I will make some investigation regarding fastboot on Samsung
Be happy, that the flashing wasn’t working, because with a wrong custom rom, you can brick your device forever
And sorry, that I have that over read, I have had to warn you asap. Sorry
Sorry, but there are several howto’s for using fastboot on Samsung devices on the web. One I have posted. So I’m sorry, but I see no misinformation.
By the way, I own a Samsung Note2 and have used more than once fastboot commands with it/on it
@clecoued, it is a fallacy to think that your SM-G903U works with a chipset Exynos 8890.
And for the SM-G903U there is at best a UNOFFICAL customROM, but no OFFICIAL nightly LineageOS.
Samsung’s User Manual (PDF) gives no information about the SM-G903U chipset. On Samsung’s official presentation page there is not a word spoken about Chipset/CPU/GPU.
For example, the interested user has to be otherwise clever, e.g. »here« or »here«
The result is: Samsung’s North American Variant for the Galaxy S7 SM-G930U works with a Snapdragon 820 quad-core chipset. The European version of the S7 SM-G930* is equipped with an Exynos 8890 Octa.
In the WWW you can find how-to’s for rooting the SM-G930U (keyword “heroqlteue”). This makes it possible to better control the StockROM Android 8.0.0 Oero. Rooting has not only advantages. For example, system updates after a root access can always turn out to be a complicated matter. In most cases, the smartphone does not receive automatic updates (“OTA” updates) after a root process.
