Does anyone have any idea what I’m doing wrong?
Tried to update to e/os version U via adb sideload - e-2.7-u-20250110460593-community-kebab.zip
it is notified in small carracters, security patch date is older than the version already installed, you need to wait for the release of e-2.8-u (you certainly already run e-2.7-t so you cannot install e-2.7-u)
have a try using e-2.6.4-t instead of e-2.7-t as an intermediate, but i am not sure the trick will work…
1 Like
in the meantime I went back to fastboot, flashed the newest recovery as well (first time I didnt update the recovery), then went back to the new recovery and successfully updated e/os to U.
I have no idea why, but the only difference was there the “active slot” changed to “a” in the recovery screen. I dont why or how to swap it, but the update worked without wiping. I just don’t know what is this thing about the slots. Maybe I have 2 different systems now and one is hidden?
The two slots alternate with each update. At the next update you will populate Slot B. Slot A will still contain the current build. In the event the next update is faulty, there is the possibility that you could set_active slot A and revert.
There is an XDA link within this reply Installation does not go forward FP4/win10 - #18 by aibd