This is telling us that the /e/OS OTA Upgrade is not supported. It follows the convention that Upgrade is Android version upgrade (not talking about regular update).
The meaasage “false” is not the reason local update fails.
Local update one hopes to “fails safe”. It was never originally intended for upgrade. It often does work for upgrade if the offered ROM is able to make a start with the wrong recovery in place.
Sometimes we can find some Meta folder or so with the updater script and this script may contain “rules” to prevent use in certain conditions.
Here the actual error is more likely reported by using a PC terminal and adb sideload.
The official advice would be clean install.
After the above the next least hazardous method is to do a new install but omit Format data.
Do you mean the updater script inside META-INF, or do you suggest actually starting an adb sideload to inspect the recovery log? Since this OTA package contains a payload.bin rather than a classic update-binary, I’m not sure where the relevant checks are implemented.
Sorry, I do not have the ROM or the device. I guess I just responded badly to
… “should” … idk.
You can only do what you can do. There has been some talk on the testing channel how to get users out of a14-official. No definite method was proposed. You are reporting an update binary with no supporting text file.
My Nord (avicii) I came from a formatted phone and use the script to go from 14 to 16. So I would say back up your data and do a fresh install, the script is very fast and works well.
Just like any PC it is healthy to format the device once and a while anyway. With A16 the Nord prefromes very well.
