Is this OTA update working seamless? Because afair there is a change from “FullDiskEncryption” (FDE) to “FileBasedEncryption” (FBE)…is this done during the upgrade seamless or is this update turning the phone into factory reset state??
Just keep in mind that at least I have still issues with using “Seedvault”
During a short period of time, the upgrade from 2.9 to 3.5 for all Samsung 9 series has been offered, but this is due to a wrong manipulation on our side: effectively, the encryption change from FDE to FBE requires a data format.
This upgrade has been withdrawn, and an upgrade from 2.9 to 2.10 is now proposed. You should see it in the updater: isn’t it the case ? And/or do you still see the 3.5 upgrade ?
We apologize for the inconvenience. People, if any, that performed the upgrade, should now be stuck at the bootanimation. To recover, the 2.10 ota must be sideloaded in the recovery via adb.
I saw the most recent update and took it. and I don’t recall if it was 2.10 or 3.5. After the update my phone got stuck on the iode boot logo and didn’t boot no matter how much I’ve waited. I went on github and downloaded all the versions from 3.4 to 2.9 and tried flashing the image via Heimdall (Linux) and sideloaded the zip via adb. I haven’t factory reset my phone yet and while I was downgrading to 3.x versions it got stuck on the boot logo. But when I’ve started downgrading to 2.x versions it started to get stuck on “Downloading… Do not turn off target”. I really don’t want to lose data if possible, could you help me?
If the recovery has been properly flash, the problem is to reboot into it.
Does the recovery has been flashed ? Do you get an error message ?
To reboot into it from the Download screen, press and hold Power + Vol down until black screen, then quickly press Power + Vol up + Bixby.
I updated samsung S9 with the iodé updater to 3.5.
And was stuck in the logo screen aftwards.
Followed your instructions here and flashed the recovery in download mode
Then I got to recovery menu and choose reboot to recovery.
The phone now displays reboot to recovery…
Doing adb on an usb connected computer just gives
adb sideload iode-2.10-20230131-starlte.zip
daemon not running; starting now at tcp:5037
daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method…
adb: pre-KitKat sideload connection failed: no devices/emulators found