0.19 ? Ok so, not yet interrested by an android 11 based ?
.
On my side, i just have dowloaded e-0.18-r-20211022 and e-0.19-q-20211027 in a way to check the content of METADATA, you may still have to edit META-DATA, as the team have included an USA carrier variant klteattactive device, but not the international main device klteactive into META-DATA.
To find your device codename you can run this command in the console of an adb enabled PC with you phone connected via a usb data cable (and “USB debugging” selected in developer options)
By your screenshot ( e-0.19-p-20211027 proposed ),
i understand that android 9 Pie based /e/OS is still builded for OTA updates, but not reachable on the website
OTA is “Over The Air” and means easy automatic update process : the system updater notify that an update is available, and you accept confirming by just a simple Klick
@piero my SM-G870F is now running 0.19 picked it manually from the recovery like last time, all up and running. So now for the the next step is maybe to update the recovery, to get it to update without manually pointing the recovery to it? What are the options? Have not looked up the metadata yet…do you want me to?
@piero I have been busy but not forgotten about this
Just stuck here atm after upgrade:
498.910454] usb 1-3: new high-speed USB device number 4 using ehci-pci
[ 499.067617] usb 1-3: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 4.00
[ 499.067621] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 499.067624] usb 1-3: Product: SAMSUNG_Android
[ 499.067626] usb 1-3: Manufacturer: SAMSUNG
[ 499.067629] usb 1-3: SerialNumber: 5bc32ef1
hibba@mantra:~$ adb devices
List of devices attached
hibba@mantra:~$ adb devices
List of devices attached
I tried this with the gts28velte. It didn’t work. TWRP won’t accept the zip. I’m pretty sure more needs to happen than to just zip a bunch of file in a folder. These zips are created in some special way.