Perfect @piero, I’ll see if I can navigate to that location from the recovery I have installed.
Thank you!
.Hibba.
At present we only have e Recovery for devices on Q OS and above. If you can share a working recovery link I can have that added to the documentation
I can’t find any specific TWRP !
Who have build it in the past ?
How was it disappeared ?
It was linked to android file host ! no ?
After some search, it seems that TWRP for klte is an unified one and suposed suitable for klteactivexx
This is what I have found so far, trying to compile it but not luck yet, I’ll ask in github for assistance.
@piero using klte I got this: On ADB Sideload I get E3004:This package is for device: klteactivexx,klte;this device is klteactive. Updater ended with ERROR: 7
I have read about a solution somewhere 2 days ago
Unofficial Pi/e/ Community Build - s4mini Value Edition SM-i9195i "serranovelte" - #14 by piero
So, We have to modify the content of some files in the /e/.zip
to make the build that matching klteactivexx include klteactive codename
1) extract the e-0.18-p-20210815130098-dev-klteactivexx.zip,
2) Open /META-INF/com/android/metadata
we will add klteactive in the last line
pre-device=klteactivexx,klte
will become
pre-device=klteactivexx,klteactive,klte
clic here to compare with /e/ stock metadata for my serranoltexx
ota-property-files=metadata:69:359
ota-required-cache=0
ota-type=BLOCK
post-build=samsung/serranoltexx/serranolte:4.4.2/KOT49H/I9195XXUCQL2:user/release-keys
post-build-incremental=eng.root.20210814.095355
post-sdk-level=30
post-security-patch-level=2021-08-05
post-timestamp=1628934731
pre-device=serranolte,serranoltebmc,serranoltektt,serranoltexx
3) save it in the e-0.18-p-20210815130098-dev-klteactivexx folder,
OR replace the existing metadata by this new metadata,
4) open /META-INF/com/google/android/updater-script
we will insert a line betwenn the fist one and the seconde one
assert(getprop("ro.product.device") == "klteactivexx" || getprop("ro.build.product") == "klteactivexx" ||
getprop("ro.product.device") == "klte" || getprop("ro.build.product") == "klte" || abort("E3004: This package is for device: klteactivexx,klte; this device is " + getprop("ro.product.device") + "."););
will become
assert(getprop("ro.product.device") == "klteactivexx" || getprop("ro.build.product") == "klteactivexx" ||
getprop("ro.product.device") == "klteactive" || getprop("ro.build.product") == "klteactive" ||
getprop("ro.product.device") == "klte" || getprop("ro.build.product") == "klte" || abort("E3004: This package is for device: klteactivexx,klte; this device is " + getprop("ro.product.device") + "."););
clic here to compare with /e/ stock metadata for my serranoltexx
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" ||
getprop("ro.product.device") == "serranoltebmc" || getprop("ro.build.product") == "serranoltebmc" ||
getprop("ro.product.device") == "serranoltektt" || getprop("ro.build.product") == "serranoltektt" ||
getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" || abort("E3004: This package is for device: serranolte,serranoltebmc,serranoltektt,serranoltexx; this device is " + getprop("ro.product.device") + "."););
5) save it in the e-0.18-p-20210815130098-dev-klteactivexx folder,
OR replace the existing updater-script by this new updater-script,
6) make a .ZIP from the e-0.18-p-20210815130098-dev-klteactivexx folder.
7) rename the new .ZIP
OR download the modified Build to test e-0.18-p-20210815-modified-for-klteactive
8) try to install it with TWRP for the klte familly
.
please share your feedback…
.
https://forum.xda-developers.com/t/tutorial-the-updater-script-completely-explained.2377695/
.
1 Like
Just for the record @piero - I am so grateful for your effort, thank you so much! I would love to try that out, but what I am suspecting is the TWRP that is to blame here, not the e-0.18, what are your thoughts on that? (Ref my last reply)
@piero - what I do not get with this error message is that it says “device is klteactive” when the github link above states that it actually is klteactivexx? So in my mind it should have worked regardless?
I have opened an issue on the /e/ gitlab :
1 Like
FYI when I get the time with the next e.update I will change the recovery on my SM-G870F from lineage-18.1-20201225-UNOFFICIAL-recovery-klteactivexx.img that I got from: https:// androidfilehost.com/?w=files&flid=321280
To this? https: //twrp.me/samsung/samsunggalaxys5qualcomm.html - please confirm if correct.
Then with this: download the modified Build to test [e-0.18-p-20210815-modified-for-klteactive](https ://ecloud.global/s/gbkwMGyaXo7qtt5)
I’ll do a standard upgrade from within the e and check if it upgrades and reboots normally?
Thank you,
.Hibba.
1 Like
I cannot confirm as it is an hypothetical and non tested workaround…
.
.
On the other hand, i just seen that /e/OS Q and R are builded for month ! with their related e-recovery !
How have we missed it ? you @Hibba and me this summer. Spending time and effort for recovery compatibility with Pie
I think they wasn’t online ! in August
Hey @piero I have been thinking of you, been super busy and have just downloaded 0.19 but not installed it yet due to the fact that I wanted to touch base with you first and go through the installation steps we discussed this summer.
Thank you so much for following up, let’s get the ball rolling again.
.Hibba.
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)
$ adb shell getprop ro.product.device
1 Like
So enlighten me here @piero… I’ll gladly try what you suggest. As of now the updater only suggest 0.19. Is 11 available for manual download?
.
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
https://images.ecloud.global/dev/klteactivexx
Update could be OTA, or manually without wiping /data,
but Upgrade have to be done manually within formating /data.
I’ll start with the codename check and report back.
…and then decide what upgrade I land on.
Not sure what OTA means though…
/e/OS R build android 11 based is actually 0.18
.
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
Fantastic, I’ll try the OTA first just to be on the lazy side. 
Thank you so much for you fantastic support @piero.
.Hibba.
@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?
Boot the device in download mode,
On your PC, go to the folder where you have downloaded recovery-e.zip, there, open a terminal and launch the heimdall flash command