Cant get into factory reset keeps going into download mode with S8

[electroteque]

There is an issue with the instructions with the installer. I am stuck at this point. It keeps wanting to go into the blue download screen and not into factory reset after it has uploaded files. pressing all those buttons wants to go into download mode or reboots.

This system refused letting me upload a screenshot of the screen. whats the point ?

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

[aibd]

@electroteque

after it has uploaded files

There are two main sets of files to Upload. First the recovery. After this one has to boot into recovery. Did you see a Custom recovery or did you see a Recovery called Android Recovery.

@aibd

These images are from an unmodified Samsung.

|

If you saw the unmodified Android recovery, then you need to use this technique to boot into your Custom recovery

@aibd

“Your first boot into the custom recovery”. This was originally written when TWRP was the standard custom recovery in use. Now we find the more simple /e/ Recovery published with most /e/OS builds.

Many users fail at this point; you should avoid allowing the phone to do a standard shutdown cycle.

Where we have just overwritten the Android recovery with the Custom recovery the user needs to know:

The key combination Volume down + Power on it’s own is Soft reset and will cause your phone to reboot and the device will over-write TWRP back to original, preventing the install of /e/, without further warning.

The instruction set to make your first boot into TWRP is often abbreviated for experienced users, but for a first timer would read:

• Please now Force stop the phone – from the current “Download mode”
  • Disregard the (unhelpful) screen message “Downloading … Do not turn off target”
• Use Volume down + Home/Bixby + Power to Force stop.
• Attend carefully, keep holding the buttons - it may take about 7 seconds,
• the instant the screen goes black (black as in off) and before the device starts to restart
• instantly change the finger press to Volume up + Bixby/Home + Power,
• Be prepared for another 7 second hold without relaxing, until Teamwin is seen.

Here, as a video.

Another nice wording to achieve the same is:

• Press all 4 buttons Volume Up + Volume down + Home/Bixby + Power for 7 seconds till the screen dies,
• Release the Volume down the instant the screen goes black
• Keep holding Volume up + Bixby/Home + Power till TeamWin appears

… or maybe it is something else … you might look for the log

@Ingo_FP_Angel

Where to find the log

The installer creates a log file with a randomly generated name (e.g. 45761d08-711f-435a-881d-a236949654bb.log) that might contain useful information if something doesn’t work as expected.

Location of the log file:

• Linux: ~/snap/easy-installer/common
• Windows: %LOCALAPPDATA%\easy-installer
  • if you don’t know how to open this location, press the Windows key plus the “r” key at the same time and paste %LOCALAPPDATA%\easy-installer into the box that appears, then hit the Enter key)

[electroteque]

I got it to power down from download mode. Used volume up to get to a recovery mode and then it says “no command”.

volume up and power does nothing.

log file at the end is here

EBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1] getFullCmd(), full command = [cmd.exe, /c, "“C:\Program Files\easy-installer\bin\scripts\install-recovery.bat” “C:\Users\danielr\AppData\Local\easy-installer\sources\dreamlte\recovery-e-latest-r-dreamlte.img” “C:\Program Files\easy-installer\bin"”]
2024-05-26 04:22:03,764 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>set TWRP_IMAGE_PATH=“C:\Users\danielr\AppData\Local\easy-installer\sources\dreamlte\recovery-e-latest-r-dreamlte.img”
2024-05-26 04:22:03,765 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>set HEIMDALL_FOLDER=C:\Program Files\easy-installer\bin\
2024-05-26 04:22:03,765 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>if not defined TWRP_IMAGE_PATH (exit /b 101 )
2024-05-26 04:22:03,765 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>“C:\Program Files\easy-installer\bin\wdi-simple.exe”
2024-05-26 04:22:52,786 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>ping 127.0.0.1 -n 3 -w 10000 1>NUL
2024-05-26 04:22:54,824 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>set HEIMDALL_PATH=“C:\Program Files\easy-installer\bin\heimdall”
2024-05-26 04:22:54,824 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>“C:\Program Files\easy-installer\bin\heimdall” flash --RECOVERY ““C:\Users\danielr\AppData\Local\easy-installer\sources\dreamlte\recovery-e-latest-r-dreamlte.img”” --no-reboot
2024-05-26 04:22:54,832 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)Heimdall v1.4.2
2024-05-26 04:22:54,832 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
2024-05-26 04:22:54,832 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)http://www.glassechidna.com.au/
2024-05-26 04:22:54,832 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)This software is provided free of charge. Copying and redistribution is
2024-05-26 04:22:54,833 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)encouraged.
2024-05-26 04:22:54,833 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)If you appreciate this software and you would like to support future
2024-05-26 04:22:54,833 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)development please consider donating:
2024-05-26 04:22:54,833 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)http://www.glassechidna.com.au/donate/
2024-05-26 04:22:55,847 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)Initialising connection…
2024-05-26 04:22:55,850 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)Detecting device…
2024-05-26 04:22:55,862 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)ERROR: Failed to access device. libusb error: -12
2024-05-26 04:22:55,864 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>exit /b 0
2024-05-26 04:22:55,866 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1] Exit value = 0

2024-05-26 04:22:55,867 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] loadSubScene(uiRoot)
2024-05-26 04:22:55,867 DEBUG [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] change view()
2024-05-26 04:22:55,867 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] ResetNextButtonEventHandler()
2024-05-26 04:22:56,180 WARN [JavaFX Application Thread] e.e.i.u.UiUtils [null:-1] loadImage(), image’s file name = , error = java.lang.NullPointerException: Input stream must not be null
2024-05-26 04:22:56,184 DEBUG [Thread-112] e.e.i.t.CommandExecutionTask [null:-1] updateParameters(), Parameters = {device_id=ce021712e1a75c2e03, adb_folder_path="C:\Program Files\easy-installer\bin"adb}
2024-05-26 04:22:56,184 DEBUG [Thread-112] e.e.i.t.CommandExecutionTask [null:-1] getFullCmd(), full command = [cmd.exe, /c, "“C:\Program Files\easy-installer\bin\scripts\wait-e-recovery-sideload.bat” “ce021712e1a75c2e03” “C:\Program Files\easy-installer\bin\adb"”]
2024-05-26 04:22:56,208 DEBUG [Thread-112] e.e.i.t.CommandExecutionTask [null:-1]
(debug)“waiting for recovery”
2024-05-26 04:22:56,208 DEBUG [Thread-112] e.e.i.t.CommandExecutionTask [null:-1]
(debug)“C:\Program Files\easy-installer\bin\adb\adb” -s ce021712e1a75c2e03 wait-for-sideload
2024-05-26 04:44:50,376 DEBUG [Thread-112] e.e.i.t.CommandExecutionTask [null:-1]
(debug)“device not detected in recovery”
2024-05-26 04:44:50,382 DEBUG [Thread-112] e.e.i.t.CommandExecutionTask [null:-1] Exit value = 101

2024-05-26 04:44:50,385 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] ResetNextButtonEventHandler()

[electroteque]

I dont understand what moment have to press the buttons while it’s switched off or turned on ? Nothing seems to work Ive only managed to get as far as the “no command” screen and the download screen a terminal did come up.

I tried these combinations while powered on volume down, bixby, power , goes down download screen, press volume down to exit, press volume up, bixby, power nothing.

volume down, bixby, power , goes down download screen, press volume up to get to download mode, press volume down, bixby, power to reboot then change to volume up, , press volume up, nothing.

[aibd]

@electroteque

to get to a recovery mode

Would you describe the Recovery mode as similar to the image, that is an unmodified Android Recovery? A confirmation would be to see if the phone still boots correctly to system, Download mode and Recovery mode which is capable of booting back to system, confirming an Original Android Recovery.

Your partial log seems to show a valid Recovery upload command

“C:\Program Files\easy-installer\bin\heimdall”
flash --RECOVERY ““C:\Users\danielr\AppData\Local\easy-installer\sources\dreamlte\recovery-e-latest-r-dreamlte.img”” --no-reboot

The downloaded and available Recovery is e-Recovery.

Then

(debug)Detecting device…
2024-05-26 04:22:55,862 DEBUG [Thread-111] e.e.i.t.CommandExecutionTask [null:-1]
(debug)ERROR: Failed to access device. libusb error: -12
[...]
(debug)“waiting for recovery”
[...]
(debug)“C:\Program Files\easy-installer\bin\adb\adb” -s ce021712e1a75c2e03 wait-for-sideload
[...]
(debug)“device not detected in recovery”

This was the reply I gave for another lbusb error: -12 case

@aibd

Libusb errors can derive anywhere is the usb chain from PC motherboard to device.

Without doing a fuller analysis, try a different cable (a cable can transmit data and perform parts of the install but fail to communicate with Download mode – it has been reported that an original Samsung cable behaves this way !).

Secondly, some USB hubs should be avoided. Sometimes a mix of different USB ports might be provided through such an internal hub. (Often at the front.) Try to use the USB port actually soldered to the motherboard. (Usually at the back.)

[electroteque]

Ive flashed before manually with LineageOS. I might have to do the manual method so I can see what is going on. I’ll try another cable. Im not sure why I am having a hard time even getting into the reset screen.

[aibd]

@electroteque

even getting into the reset screen.

I don’t understand. Why do you not tell me if you have

@aibd

an unmodified Android Recovery?

Does your recovery offer a Factory reset?

@electroteque

Ive flashed before manually with LineageOS.

Ahhh … Perhaps you are using Easy Installer over LineageOS? Not a problem.

@electroteque

I might have to do the manual method so I can see what is going on.

Much easier to debug! Perhaps use the Windows device manager technique in linked post to check for correct full drivers for Samsung. Windows regular drivers may not communicate with Download mode.

[electroteque]

I tried another cable. In the download window I see no console log of anything being uploaded. The terminal loads however. I am running the installer in a restricted user login but it asks for admin permissions for the tool.

When going to the reset window it again goes to “no command” and then after a while loads Android Recovery.

I think the installer is borked and will have to try manual mode.

[aibd]

@electroteque

I am running the installer in a restricted user login but it asks for admin permissions for the tool.

libusb error: -12 – I understand that this (also) is a general permission error.

Like this ?

https://forum.snapcraft.io/t/installing-snaps-without-admin-access/5717

[electroteque]

I did the installer process in the download screen as admin. I see no console logs of anything being uploaded, a terminal displays about uploading a driver but no actual further logs shown, there is nothing printed out in the console logs on the download mode screen.

Going into the recovery screen still says “no command” and then goes to Android Recovery. I think the installer is broken. I had a look at the manual process and documentation is messy and hard to follow. There is no heimdall link for windows. I downloaded the stable dreamlite files but need to figure out how to go from there.

[aibd]

@electroteque

There is no heimdall link for windows

On Windows, Odin is good for the job. Check out this HOWTO [HOWTO] Install /e/ on a Samsung smartphone with Windows easily

Later Edit Good to see that this suggestion worked out for you, Samsung S8 install via ODIN works. Installer does not.

[electroteque]

Its a bit of a dead end. I tried the manual mode docs the actual tool name is zadig not zadiag as example docs need fixing up. It is helpful visibly seeing where the problem is via manual mode however. Odin sees the phone but zadig doesn’t. I tried choosing a random “Gadget Serial” device but failed installing a driver. I might be forced to use Odin instead ? I dont remember how to use Odin and its interface is bad too.

my motherboard is a gigabyte Aorus master x570. Ive tried every single usb port on it and 2 different cables. But the fact Odin sees the device right away means there is something wrong with the other tools instead.

Ive taken up all the time I can looking at it and have to come back to it.