[Device Roadmap] Android 9 (Pie) & 10 (Q) : Test builds to support new devices

Hi,

Many thanks for your answer and proposal. I do not have time right now to redo all of the process but as soon as i do, i will contact you.

I have also looked at your post

  • where you are explaining Format data and Advanced Wipe should not be done on Sony devices ; do you know why ? (just for my knowledge)

  • also can you tell me what was the android version on the z3c you finally install /e/ on ?

Thanks again

OTA update appeared, thanks.

One thing with the update from version 0.9 to 0.10 is that the Maps application disappeared.
There were no Maps in OTA 0.11 either.
Installation “Magic Earth” from the store solves the problem.

I did this on an untouched sony z3c, and i lost the MAC-Adress of the device leading to non functioning wifi, with all roms from /e/ to linage to carbon rom, to original sony firmware. no the device is paper weight. it seems that there is a partition on that device that stores this info and is deleted by twrp when doin the above…
i started from the latest sony firmware which is something xxxx.291 or so.
the first bricked sony was my original sony preorderd z3c, no provider branding

Samsung Galaxy Tab S2 8.0 LTE (2016) (gts28velte)
Samsung Galaxy Tab S2 8.0 2015 (LTE) (gts28ltexx)
Samsung Galaxy Tab S2 8.0 2015 (Wi-Fi) (gts28wifi)
Samsung Galaxy Tab S2 8.0 WiFi (2016) (gts28vewifi)
Samsung Galaxy Tab S2 9.7 LTE (2016) (gts210velte)
Samsung Galaxy Tab S2 9.7 2015 (LTE) (gts210ltexx)
Samsung Galaxy Tab S2 9.7 2015 (Wi-Fi) (gts210wifi)
Samsung Galaxy Tab S2 9.7 WiFi (2016) (gts210vewifi)

Hi,

I finally succeeded in installing e/ (after few problems… so I learn basics of flashtool… Did you try it for your first bricked z3c?)

I wanted to thank you for your support !
M

Hi, I have intensively tested the BQ Aquaris X (e-0.9-p-2020072264212-test-bardock) for several weeks with no issues at all. Now I have under test his big brother the BQ Aquaris X Pro. Really nice to “rescue” this two devices and give them a second life.

Thanks.

2 Likes

Thanks for the feedback and let me know what happens with the X Pro.

HI-

I am a bit confused. Should I have gotten an OTA at this point for my Shamu? I have this version installed:

Thanks for writing this up. I tried to flash my SM-T813 via USB, but I couldn’t flash the /e/ ROM. I always got Error 7 in TWRP.

As you wrote, I then tried to installed the ROM directly via TWRP. I used a USB Stick with OTG adaptor to safe and install the image from (instead of an mSD Card) but got the same Error.

After a reboot everything worked and /e/ runs fine on my tablet now. I ended up installing manually from the USB Stick, but maybe it’d have worked via adb as well.

Already received the first update, seems running well.

If you are using TWRP 4.0.0, use TWRP 3.3.1 instead.

Thanks for the follow up. In the end it worked after the reboot, so it’s fine for me. I just downloaded the newest version from the official TWRP website while I prepared to flash.

Any reason to rollback or will it be fine?

When will the new OTA be released? :slight_smile:

I would like to get the OTA update for my S2 tablet.
I see that I need to repeat a manual flash with a build newer than the one below

After flashing the new build, will my data and configuration remain there or I will be forced to reconfigure all the apps ?

All OTA’s are suspended for now while we figure out the issue with the v0.12 build. Hopefully early next week I should be able to run a fresh set of builds for all the still to be supported devices.
BTW we are adding 4-5 devices every week to our officially supported list so it will not be long before you get the official build on your device.

3 Likes

Same error message on all versions of TWRP and e/. Looked into the files and it might be a script error, asserting the device attributes with getprop. Even if I setprop in the TWRP terminal or via adb shell the error persists.
FIX:
Deleted the first line of the script (META-INF/com/google/android/updater-script)
Disabled zip signature verification
Installed my modified zip

Works fine now, make sure to get in touch should any more problems occur.

@Manoj Update of the List of LineageOS supported devices since the last update (August 9th):

New supported devices:

Google Pixel 3 (blueline) : 10
Google Pixel 3 XL (crosshatch) : 10
Google Pixel 3a (sargo) : 10
Google Pixel 3a XL (bonito) : 10
Google Pixel 4 (flame) : 10
Google Pixel 4 XL (coral) : 10
Huawei P Smart (figo) : Pie
Huawei P20 Lite (anne) : Pie
Motorola Moto G7 Play (channel) : 10
Motorola Moto G7 Power (ocean) : 10
Nokia 6.1 (2018) (PL2) : 10
OnePlus 7T Pro (hotdog) : 10
Samsung Galaxy A7 (2016) (a7xelte) : 10
Xiaomi Redmi Note 8 / 8T (ginkgo) : 10

These devices were missing from my list (don’t know why) so I added them:
Realme 3 Pro (RMX1851) : Pie
Xiaomi Redmi K20 / Mi 9T (davinci) : 10

3 Likes

I bought a gts210vewifi with the Test-Build from September 2020 installed.
In General it works well.
But: New Pipe crashes, when i start playing a video. YouTube in Bromite has no problem.
New Pipe has no Problem on my crackling with LineageOS for MicroG 17.1.

Which versions you have on the two phones?

If you want, there’s a room on matrix to understand all the story:
#newpipe:matrix.org

NewPipe just initiated an Update via browser on both devices to 0.20.4.
Now there is no problem with /e/ OS on the tablet.
(I sent crash-reports)

0.20.4 seems to have problems.
In the meantime that issues will be fixed, I suggest you to install Newpipe Legacy 0.20.2, that work fine!