The good news is that an updated version of the Updater has been released which will enable users with test builds to get the builds OTA
The bad news is that this would require a manual flash again the first time for test build users. Subsequent test builds will flow in OTA
Just tested this on a Redmi land 3S check the screenshot below
Reporting my experience on flashing a Samsung Galaxy S2 tablet, SM-T813 with an sdcard mounted
with https://eu.dl.twrp.me/gts210vewifi/twrp-3.4.0-0-gts210vewifi.img
and e-0.10-p-2020081167314-test-gts210vewifi
through a linux Mint 19.3 cinnamon (adb and heimdall installed)
Steps
Iâve found the device already factory reset
start the device, and finish the setup avoiding all requests from Goo and Sam
enable the developer mode on the device (seven taps on build) and turn the device off then back on but in download mode, i.e. pressing Home + Volume Down + Power
on linux terminal
a) > adb devices to verify the usb connection
b) > heimdall print-pit > info.txt to save informations from the device
c) > adb reboot bootloader to reboot into download mode
d) > heimdall flash --RECOVERY twrp-3.4.0-0-gts210vewifi.img --no-reboot
Entering TWRP recovery mode
For me, being not a a âflashaolicâ, the tricky part was the proper timing between the two steps here below. Along this step I broke into a cold sweat, since I supposed I entered into a boot loop. Note that if you do not enter TWRP at this stage, you have to repeat the steps c) and d) above.
Again: the proper timing is the key to escape the cold sweat !
a) press Volume Down + Power to turn off the device
b) after the shut down (dark screen) press Home + Volume Down + Power to enter into TWRP recovery mode.
Make a backup of the device in factory state for an improbable, but still useful, future restore (TWRP)
a) mount an USB OTG (where to save the backup)
b) wipe > Format data to remove the encryption
c) Backup > check System + Boot
d) Select storage > USB OTG and wait until finished
e) unmount USB OTG and remove the key
Still on TWRP: wiping the device
a) wipe > advanced wipe > check Dalvik cache + System + Data and swipe to wipe
b) back to TWRP main screen
Copying the eOS zip file from linux to the device and flashing it.
a) from linux terminal > adb push e-0.10-p-2020081167314-test-gts210vewifi.zip /sdcard1/
b) wait until the copy is finished
c) on TWRP
go back to home screen, tap install and navigate to sdcard1 (panel on the left), keeping Zip signature unchecked
d) swipe to confirm flash and wait
reboot and setup with eOS
All ended well and now I can start using my very first tablet.
As far I can see, it works properly, but I still encounter problems that I find in my S8 smartphone. For example, on this tablet I cannot add my (webdav) Gandi account with the embedded DAV5x fork, while it works properly with my /e/ account.
On my S8 I have installed DAVx5: there I can add my own Gandi account but not the /e/ one.
I have just installed and run this build e-0.10-p-2020081267314-test-z3c with no problems.
I did a âdirty flashâ over an earlier unofficial build (e-0.9-p-2020072464361-test-z3c) to preserve my installed apps and data. This worked fine.
The one strangeness was that I have a shortcut to Magic Earth on my Launcher 3 home screen. After flashing the shortcut was still there, but the icone was âgreyedâ, and pressing it give the message âApp isnât avaialble.â When I checked via the app drawer, it looks like the app is not installed. I guess itâs not longer one of the pre-installed apps.
I havenât run the test plan, because it seems to be focussed on a clean install. If you still need it I can blow away my existing apps and data, do a âcleanâ flash, and work through the tests. But Iâm happy not to do that if you feel the build has been tested enough already
No need to update the test plan. This build is more to test the OTA and eRecovery. Will be making another set of builds once the eRecovery code has been merged into this branch. Hope to get that done today. Once the build is complete it should show up on all the test devices with the 0.10 build.
sideloading it on previous lineageOS(16), so you can call it âdirt installâ
My aim was having Android Auto working thanks to microg integration, but it does not work neither (Iâm not saying itâs /e/ fault, just I was not able to make it work in with my car)
NO fm radio sadly
Much better camera app!!
Overall it seems to work fine (calls, im, etc)
I will use it a few more days and then decide if I come back to lineageOS but I wanted to report this here.
Have you not received a single OTA on the tablet?
The first v-0.10âŚbuild has to be clean flashed is my guess. I am seeing that in a few posts on this thread. A dirty flash does not help with the subsequent OTA.
All the same have started a build for the YTX703L you can try refreshing the updater in a couple of hours to check,
Thanks- I will let you know when a build is available. Was trying to run a build for the YTX703L but it failed due to some issues on our build infra. Will have the team look at it today and then run a new build specifically for this device to test OTA. Will update you.
Hello. Is the OTA update already available for OPPO R5s ?
I tried after manual update and for about a week on a clean installation but nothing appears.
Thanks for answering (I have abandon to try on this phone and keep the lineage os)
I have another z3c fully new on which I have installed the last TWRP version (available on TWRP website) but for now it does not boot into recovery⌠so for now i told myself âdonât do anythingâ
If anybody in Paris is interested to help / doing it versus payment (if anybody interested please contact me)
i used the TWRP Version from lineage os for z3c, not from their website. If you have unlocked the bootloader with sony code successful and flashed twrp, you should be able to boot into it. One hint is using the âhard offâ button in your z3c, it is located left of the sim card slot (a yellow quadratic button, press it with a pencil or something similar, and your phone is hard off) then you can hold the volume down button and keep it pressed while pressing power button, and release both when phone vibrates. than it should boot into twrp (give it like 30 secs, sony logo will appear before twrp).