I would really appreciate if some kind soul could explain to me how to do the upgrade.
Note: i bought a new 128 GB sd card and formatted to portable storage. My phone already had portable storage 32 GB but was getting full. I mention this because i have an info link on my upgrade notice that explains about needing
portable versus Adoptable.
Just for your information 1.17.1-q-herolte was a “special release” the purpose of which was to ensure users did not bring forward Adoptable storage. Here is the link to the Release Note v1.17.1-q · e / os / 🚀 Releases · GitLab. I understand from what you say that you already tried to deal with this.
I am following your much appreciated advice now. Cleared cache/storage in Update section.
About to soft reset. I figure i have to close phone first so will log off here and do that and report back,
I did the soft reset. Twice.
First time after simply turn phone off. Same result in updater.
Then shut phone down (shutdown on long press power button) and tried soft reset as you suggested.
which will lead to a download page if the URL is copied and pasted into a browser.
(I had already done that prior to starting this thread - which is how i know)
When the downloaded zip file is extracted, there are several files and folders.
The official advice on an Android version Upgrade is to treat it as a fresh install except in the case of an official or stable build, Different Build Types ← please read the link! – where the process is automated.
Please can we first establish (and please record here) for sure that the current build is stable.
Settings > About Phone > Android version > /e/OS version. Tap on /e/OS version to copy to clipboard.
So the automated stable (aka official) Android version upgrade was expected to happen in February / March 2024 – at the time one would have read:
Did the phone ever have an SD card as Adoptable storage?
A degree of speculation, but the encryption of the device may hold some “ghost” of a memory of this.
I would suggest that you uninstall all apps that are not vital to you.
You could install the app “List my Apps” de.onyxbits.listmyapps - (you may have apps you forgot about).
Especially uninstall all apps which ever existed in an Adaptable storage environment.
Did something I should know about happen with the phone around that time that would complicate the process?
Please prepare a backup, there is quite a high chance that you may have to Factory reset & reinstall as happened in the final post of the “Problem update 1.20 on Samsung Galaxy S7” which you already read – if necessary please ask before moving on.
Stage two
There is a risk of data loss. If you are given the choice to Format data, I suggest on a first pass you just say No.
I believe the file you should use is “url”: "https://ota.ecloud.global/stable/herolte/e-1.20-r-20240221382013-stable-herolte.zip",
From the filename we see the build date 2024-02-21.
Now down load this file on your phone, if necessary find it and move it to a location you can navigate to.
Boot into Recovery
Tap Apply update > Tap Choose from … > and navigate to e-1.20-r-20240221382013-stable-herolte.zip (If necessary use some appropriate button to apply, continue or install.)
The desired outcome is that the phone will boot into /e/OS 1.20-r-xxx in which case the Android version Upgrade will be complete.
Thanks @piero I edited the earlier post to make it quite clear that the archive should be reached only from the intended route, Django REST framework. However while working a few hours ago is Not Found now.
Edit So I guess @eguy that you will have to hold my “Stage two” suggestion until “older builds” become available again.
Meanwhile you could attempt this method with either of the builds currently available
As I read your posts again … it seems worth mentioning that the ROM should not be unzipped. If you wanted to check that the download was “all complete” the way to do it would be to check its sha256sum which can be found on the download page /e/OS stable herolte download.
As time goes on (and if you are prepared to wait) I suggest that you may feel more comfortable to wait for “older ROMs” to become available, remembering that there is no ETA for this and it may be one of the last priorities for the dev / infra team.
Here is the currently “Not found” link in order to make a quick check of availability
Hi @piero, not sure if the question was for me or not but yes, my S7 is up and running 2.6.3 now as of about an hour ago … ! Encountered some problems following the install guide for the herolte (that I will definitely document) and discovered a short cut/workaround install method that may be of interest to the community after big problems with adb no longer recognising the device after wiping.
presentation of the steps,
on the computer, on the device
type exceptions
old school device, a only device, a/b devices
brand exceptions instructions
common instructions
device specific steps
platform specific instructions
so i can add a paragraphe for the s7 somewhere, or a link to your thread…
Hi @piero, just updated from 2.6.3 to 2.7 and all good. Everything is working correctly as far as I can make out (so far, so good, … ). Really impressed with how easy it is to get yourself out of trouble as long as you’ve got a Linux box to hand. heimdall worked well to install the recovery image but adb failed miserably after the reboot with:
adb: sideload connection failed: device unauthorized.
This adb server’s $ADB_VENDOR_KEYS is not set
I’m guessing something got wiped and wasn’t included in the recovery image. Rather than trying to fix the problem I simply copied the zip file to an SD card and loaded/installed from that.
All good
updating the recovery first is recommanded by some users, from my point of view, it could be only important when upgrading.
as far as i know, the android built-in system updater use the existing recovery, and eventually (if enable in settings) replace it during the new build installation.
With this my TWRP got overwritten, by the /e recovery, so I used ODIN again to flash the above TWRP again and to my own surprise this went trough with no complaints e-2.4.1-s-20241008439849-official-herolte.zip:
Now Android could no longer read the external SD card, but I left it at that and went into TWRP recovery again, which had no problem reading internal and external SD:
|
What to make of all that? Would not recommend doing this, but it shows there is not much to stop anyone(like when trying to downgrade Android versions)!
In my case here I was able to use TWRPs file manager, so definitely worth trying if some thing went wrong.
