The problem is this. Bootloader 1.15 for developers was installed on the Galaxy S9+. Operating system version e-1.15-t-20230918331436-dev-star2lte.zip
Updating via the built-in menu did not work. So I downloaded the latest image e-1.18-t-20231210360971-dev-star2lte.zip and decided to install on top of this.
But I think the problem is that I made at least 2 mistakes before updating.
Before the update, I installed an alternative launcher (Final Interface) instead of the standard one and did not disable it.
I think it was necessary to switch the phone back to the standard screen launcher. Apparently that’s why I’ve now experienced an eternal reboot after the update.
The second mistake is that I did not install a new recovery before installing the latest firmware.
I don’t know how to install the latest recovery on Windows. I don’t remember how I installed it the first time.
Can someone tell me how to install the latest recovery? Or is this not necessary?
I can run the previous release of recovery Version 1.15
And install the latest update image from it, too, with a success of 1.00000, but after a restart, an eternal ball under the letter e jumps into the system. What should I do?
Please tell me.
I think the problem is that a third-party launcher (Final Interface) is installed in the system itself, and not the standard one. And therefore the operating system cannot start.
Of course, a factory reset could solve the problem, but I don’t want to lose information on my smartphone. How can I reset the screen launcher to default settings without doing a full reset?
Or maybe the problem is not this, but that the recovery from version e-1.15 does not fit e-1.18?
I tried installing the firmware on e-1.15 via adb sideload. I can flash it with 1.0000 success, but I still can’t reset the launcher to default settings.
I would love to activate it, but I can’t log in. The eternal letter e and the ball under it do not allow me to log in to change it to BlissLauncher , as you wrote.
Thank you 100 times for writing!
I thought no one would answer.
How to manually update the recovery or is there no need to do this? Is it already built into the latest firmware?
I tried to flash the latest firmware via adb sideloader using recovery version 1.15. I can flash it, but the recovery version does not change, and the operating system does not start.
Luckily I can enter recovery, but what should I do next?
Is it possible to activate BlissLauncher by changing the code in the latest firmware to force BlissLauncher to launch?
Can you use the ODIN 3 Flash tool under Windows? If yes, then Download first this version of Odin. More information will follow after your successful Odin installation.
