If the “lasy instabler” has installed TWRP, we can think it have prepared the device to accept the famous android 8 based /e/stable (by flashing android 8 /vendor)
No friends, no neighbors, no familly, no work ?
So, simplier is from the PC, just to take the latest e-stable.ZIP from the “lasy instabler folder”,
( today it is e-0.19-o-stable ),
copy it into the phone memory
And simply install it using the TWRP install feature.
Other solution is reinstalling the android 10 based Samsung OS, then TWRP, then e-0.19-q-dev
Alternative is installing an android 10 based vendor.img to the /vendor partition using TWRP, then e-0.19-q-dev
OK. So I am using Linux Mint Xcfe with Samsung Galaxy s9. When I type snap run easy-installer in the Terminal it comes up with this (almost all here in this one screenshot, with a little bit at the end not showing, so please let me know if you need/want to see that too):
Did I muck things up by not having upgraded to 10 before using the Easy-Installer? I mean, like, with how things work/don’t work once I have /e/ installed?
Edit, after most recent post, so if the phone was Oreo, you are all good for /e/ Oreo stable.
I am trying to catch up on what you wrote already! Based on what I have read I guess most likely Easy Installer embarked on the Downgrade to Android 8. This would fit with the very experienced @piero’s suggestion to go with Oreo, stable.
I expect Easy Installer will be able to pick up where it left off, but you were getting good advice earlier to do Android 10 manually. So if it was 8 all along that changes too - so I struck through that line as I have not read enough
This minute I do not want to influence you one way or another!
So did the familiar Easy Installer interface appear after that screen?
So, simplier is from the PC, just to take the latest e-stable.ZIP from the “lasy instabler folder”, ( today it is e-0.19-o-stable ),
copy it into the phone memory
And simply install it using the TWRP install feature.
Other solution is reinstalling the android 10 based Samsung OS, then TWRP, then e-0.19-q-dev
Alternative is installing an android 10 based vendor.img to the /vendor partition using TWRP, then e-0.19-q-dev
So which of these do you recommend for me? I am not sure, but my local library might use Windows, but I doubt I would have free access on their computers. I can’t think of anyone or anywhere else where I could access Windows, but I suppose I could ask around.
Otherwise, if I try the e-stable.ZIP (please can you provide the link to this here?), then will this result in the same as if I had gone from android 10?
What I am trying to understand is whether I have messed things up by going from 8 to /e/?
Samsung build traps to stop people downgrading!
/e/ likes you to put your chosen /e/ on top of exactly the same Android version.
So if I had a Android 8 Samsung, I would have to decide if 1.) I would Upgrade Samsung to 10, but as @Piero says, you really want Windows for that NOW.
or 2.) go with /e/ Oreo.
You have options, but some carry a risk if the phone is “half changed”. I feel you are over anxious, please don’t do two things at once!
That’s cool. So, from what you and aibd are saying, it seems that the /e/ that I am able to install now, without first reverting to android 10, will be an older version of /e/? Does /e/ OS not upgrade and all of that jazz?
Also, please would you paste the link to the suitable ZIP here, as I don’t trust myself to find the correct one! Thank you.