I was trying to install e/OS on a Galaxy S7 via the easy-installer and it failed…
I noticed that there was a trick to do for first boot into recovery mode, I managed to go to the recovery mode, but when the easy installer told me to go in “Update from ADB” it didn’t show me anything on wether or not the download of the os was complete… I though that it was somehow stuck and disconnected my device from the computer.
Now, my phone has no access to the custom recovery mode, instead it is back to the samsung/heroltexx/herolte mode, where I can “Apply update from ADB” or “Apply update from SD card”, or “Run graphics test”…
I tried “Apply update from ADB” and my computer detect it :
And then here I am because I don’t want to rush (like I did with my old Xperia XA2 which is in a unusable state) and I could use some help from you guys to achieve the installation.
Since I can use adb commands, I think something is still possible
Can you explain to me like I’m 5 how to do it ?
PS : I still have these :
from the easy-installer runs, maybe I could use them for manual installation ?
What sticks in my mind is that the e-recovery does not seem to be able to handle being flashed to a “new device”. I think especially the newer threads had this issue but it does not apply to all the threads I listed.
so from there, (with the device in download mode) try : C:\Heimdall>heimdall print-pit
the device must reboot, turn it off, reboot it in download mode and try : C:\Heimdall>heimdall flash --RECOVERY recovery-e-latest-s-herolte.img --no-reboot
after one minute, turn it off (Volume down + power) and IMMEDIATLY reboot to recovery mode (Volume up + power)
you must end in the recovery-e screen…
TWRP is shipped with a sha256 for twrp-3.7.0_9-1-herolte.img – this is used to check that the download is an exact match with the original. Try this SHA-256 Checksums Explained
Half of the job is to get a working Recovery. Once you have working Custom recovery (another description of TWRP) the second part of the job is easy.
You can use e-latest-s-herolte.zip and e-latest-s-herolte.zip.sha256sum
providing you can establish a sha256sum match as above.
this is expected : adb onlly works in system mode or in recovery mode…
in download mode, the correct heimdall command is heimdall detect
note : your photo is from Samsung recovery mode that have to be replaced by the recovery-e or TWRP.
.
on a computer running Windows, easiest is to follow one of the linked HowTo using Odin,
Well, I tried to go the Odin way, but after the drivers installation, the computer doesn’t detect anything (I tried different USB cables, even one of them was new)
about the heimdall detect, it showed this (before and after the drivers changes from Odin way):
I connected my phone to another USB port (soldered this time as I think I understood what you meant : I choosed one at the back of the computer) and I still got same errors :
As you can see I have missing drivers corresponding to my phone (it appears only when I’m plugging it)
But from here I don’t know what to do, I have samsing drivers installed already (the ones found from odin way of installing e/OS : Samsung USB drivers 1.7.61.0) and I also found these from windows update history :
Did you try uninstall Samsung drivers then with the phone connected in Download mode Select the " Problem device" and run Windows update (by right click perhaps) on that specific item.
For Windows users only: install the necessary drivers. A more complete set of instructions can be found in the Zadig user guide.
If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Samsung Kies.
Run zadig.exe found in your extracted Heimdall directory.
…
It is difficult when we offer you so many different ways forward!
Flash Custom recovery has to be done first.
The Windows way is with Odin.
If you want to use the commands still in your Snap environment, heimdall (a Linux command set adapted to work in Snap) may work, but follow Linux method / instructions.
adb commands will only be used in the “Second stage”, that is after Custom Recovery is flashed and working.
relate definitely to the phone in Download mode? Or something else?