The official builds have dedicated maintainers and are tested on the telegram testing channel before the release.
I am not sure, but this may not be the case any longer because the connection between SafetyNet pass and adb root use is no longer there with Android >= 12: SafetyNet on /e/OS Community "dev" devices - let it in or not?. (The article explains the link between SafetyNet and adb root.)
As I do not use a smartphone with /e/OS official, I hope that another user may confirm that adb root now works on official devices, too.
Well these days the release is community then official, when it is published but the actual testing for devices which have official is with official build. community test builds are rare for device which have official
From the official docs:
Why canāt I root from developer options on official builds?
officialbuilds intend to be offer the better user experience for our users. Thatās why we worked hard in order to offer Safetynet support for those devices, in order to improve third party app support. To do so, we had to fake the build type, moving fromuserdebugtouserbuild (awaiting the move onuserbuilds)As a side effect, it disabled the
adb rootoption, available underDeveloper Options. In order to recover it, we advise our users to move on a/devbuild.
The following topic suggests, that adb root nowadays might work on Official builds and the above docs might be outdated:
TBH the current situation is confusing!
Can we please get an official clarification on this?
And if adb root is officially supported on āOfficial Buildsā, then could the official docs please be updated?
No adb root is not allowed on official builds.
PLEASE!
Then realy please keep community builds for all those of us, that need adb root.
Well, or enable adb root on the official builds.
adb-root Should still be usable by simply booting TWRP