S9 doen not boot in E recovery but in Samsung recovery.
It seems to install E/os, easy installer says it’s done, but the phone said it’s aborted.
I did excactly what the easy installer said.
log file far too large to post it here, so I posted the part with the download error message:
2023-08-18 16:29:42,989 DEBUG [Thread-9] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>“C:\Program Files\easy-installer\bin\heimdall” detect 1>nul
2023-08-18 16:29:42,994 DEBUG [Thread-10] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>“C:\Program Files\easy-installer\bin\heimdall” detect 1>nul
2023-08-18 16:29:43,210 DEBUG [Thread-9] e.e.i.t.CommandExecutionTask [null:-1]
(debug)ERROR: Failed to detect compatible download-mode device.
2023-08-18 16:29:43,210 DEBUG [Thread-10] e.e.i.t.CommandExecutionTask [null:-1]
(debug)ERROR: Failed to detect compatible download-mode device.
2023-08-18 16:29:43,219 DEBUG [Thread-9] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>if errorLevel 1 (
2023-08-18 16:29:43,219 DEBUG [Thread-10] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>if errorLevel 1 (
2023-08-18 16:29:43,220 DEBUG [Thread-9] e.e.i.t.CommandExecutionTask [null:-1]
(debug)echo not found
2023-08-18 16:29:43,220 DEBUG [Thread-10] e.e.i.t.CommandExecutionTask [null:-1]
(debug)echo not found
2023-08-18 16:29:43,220 DEBUG [Thread-9] e.e.i.t.CommandExecutionTask [null:-1]
(debug) ping 127.0.0.1 -n 2 -w 1000 1>NUL
2023-08-18 16:29:43,220 DEBUG [Thread-10] e.e.i.t.CommandExecutionTask [null:-1]
(debug) ping 127.0.0.1 -n 2 -w 1000 1>NUL
2023-08-18 16:29:43,220 DEBUG [Thread-9] e.e.i.t.CommandExecutionTask [null:-1]
(debug) goto :heimdall_detect
2023-08-18 16:29:43,220 DEBUG [Thread-10] e.e.i.t.CommandExecutionTask [null:-1]
(debug) goto :heimdall_detect
2023-08-18 16:29:43,220 DEBUG [Thread-9] e.e.i.t.CommandExecutionTask [null:-1]
(debug)) else (echo succeed )
2023-08-18 16:29:43,221 DEBUG [Thread-10] e.e.i.t.CommandExecutionTask [null:-1]
(debug)) else (echo succeed )
2023-08-18 16:29:43,221 DEBUG [Thread-9] e.e.i.t.CommandExecutionTask [null:-1]
(debug)not found
2023-08-18 16:29:43,221 DEBUG [Thread-10] e.e.i.t.CommandExecutionTask [null:-1]
(debug)not found
2023-08-18 16:29:44,269 DEBUG [Thread-10] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>“C:\Program Files\easy-installer\bin\heimdall” detect 1>nul
2023-08-18 16:29:44,274 DEBUG [Thread-9] e.e.i.t.CommandExecutionTask [null:-1]
(debug)C:\Program Files\easy-installer>“C:\Program Files\easy-installer\bin\heimdall” detect 1>nul
2023-08-18 16:29:44,476 DEBUG [Thread-9] e.e.i.t.CommandExecutionTask [null:-1]
(debug)ERROR: Failed to detect compatible download-mode device.
2023-08-18 16:29:44,476 DEBUG [Thread-10] e.e.i.t.CommandExecutionTask [null:-1]
(debug)ERROR: Failed to detect compatible download-mode device.
This section of log only really tells us
Failed to detect compatible download-mode device.
in the preceding section of the log you are likely to see
waiting for recovery
Then, if my guess is right, Recovery is found but Easy Installer cannot work with Android recovery.
Edit later OK … from the full log … this is not what I expected !
I have installed 5 S9 so far without problems.
This time no “e recovery” but Android recovery.
When I choose apply update from ADB easy installer goes further and says e/os should be loading now,
you should see the e logo.
But the phone is stuck and can only be resetted to stock android factory mode
Full log is here: http://gofile.me/3kmui/FD8SQhjJs
Please can you show the contents of
C:\Users\OrionSystemen\AppData\Local\easy-installer\feedback-96e6e3de-a79a-4da9-91aa-4257faa570c7.txt
Edit, 24 hours later. I had not previously wanted to include a guess or speculation but I cannot explain how Easy Installer moves on at the point
ERROR: Failed to access device. libusb error: -12
If
heimdall flash --RECOVERY recovery-e-latest-q-starlte.img --no-reboot
were to fail I would expect Easy Installer to fail / close.
Perhaps someone else can offer a more informed opinion.
As this is a long log with, I think, 230 matches for
ERROR: Failed to detect compatible download-mode device.
It might be worth checking the Odin mode screen for any clues of some lock still applied.