Yes selected ‘Enable ADB’, which is confirmed in console window at bottom of phone screen.
Tried again, still ‘Authorised’.
OK will try TWRP adb sideload
Yes selected ‘Enable ADB’, which is confirmed in console window at bottom of phone screen.
Tried again, still ‘Authorised’.
OK will try TWRP adb sideload
deleted post … deleted post
https://xdaforums.com/t/recovery-exynos-official-twrp-for-galaxy-s7-herolte.3333770/
Download Links :
(SM-G930F, SM-G930FD, SM-G930X, SM-G930W8) & Korea (SM-G930K, SM-G930L, SM-G930S)
then loosing /data, you can install :
to be up to date
Ok, thanks for all the help.
Am in download mode, have Heimdall on my PC, placed the correct device .img in the folder (twrp-3.7.0_9-1-herolte.img).
Opened cmd from the Heimdall folder, and ran ‘print-pit’, and received this error:
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:
Donate | Glass Echidna
Initialising connection…
Detecting device…
ERROR: Failed to access device. libusb error: -12
Am I doing this in the right order …
Update:
Thought I would have a go with Heimdall One Click, but the file ‘twrp-3.7.0_9-1-herolte.img.tar’ is not recognised in the ‘Load Package’ tab when I browse.
Have tried this:
Run the zadig.exe
Choose your phone from the drop down list (on my pc it was "MSM8960
Go through the drivers (WinUSB, Libusb0, Libusbk) and clikc Place drive for each of them.
Then run Heimdall
But ‘Replace Driver’ fails when I try with the first one suggested (WinUSB).
The Easy Installer for S7 - no longer seems an option in the Smart Phone selector - that worked a dream first time - could it be used again ?
I had quite a few ‘e.foundation’ web pages bookmarked - but these now 404, I guess there has been some re-arranging going on.
OK have resolved the problem, with a Fresh install of e/OS v2.8, S7 now working, with access to all files etc.
Thank you for your patience, think I have a better handle of the process now.
One question, does TWRP need to be flashed everytime you need it, I cannot boot into it without flashing it first.
For anyone with the same issue.
Tried using Heimdall on Win 10, Zadig updated driver to start, Heimdall run a ‘print-pit’ command successfully, but could not boot into TWRP for some reason, tried updating drivers again, but Zadig failed.
So used Odin3 to successfully flash TWRP to the S7, without any driver errors.
Downloaded TWRP file for device: Samsung
Check AP box in Odin, and browse to the TWRP file ‘img.tar’.
Before pressing ‘Start’:
See this video fior the trick to boot into TWRP:~
https://www.youtube.com/watch?v=5aE_AX8HBDg
NEED TO KEEP HOLDING Vol Up, Power and Bixby before and after pressing Odins Start, otherwise e-Recovery just appears.
In TWRP could not work out how to backup data (as pressed for time) … so decided to crack on.
Using TWRP ‘adb sideload’ I tried to Install e/OS v1.6, (did not wipe anything) but phone would not boot after sideload finished, phone was stuck in loop at boot time.
So Wiped all, and did fresh install of v2.8 using TWRP adb ‘sideload’ feature:
In cmd, from Platform-tools run:
adb sideload e-2.8-s-20250220470167-official-herolte.zip
Rebooted straight into v2.8 - with all directories available again.