Couldn't update to /e/OS 3.1.4

[Marine]

Hi,

I am using a samsung galaxy s10e with /e/ for several years now.

Yesterday I tried to upgrade to /e/3.1.4 (I am now running /e/3.1.1).

However my phone froze during the set up (black screen, white “e” and loading bar). As I couldn’t do anything, I let the battery discharged at night and I could turn it on in the morning with my last OS running.

Has anybody got this kind of trouble?

[piero]

Hello @Marine ,

why e-3.1.4-aXX when e-3.4-a15 is out ?

/e/OS community beyond0lte download

[HOWTO] Upgrade my /e/OS to major Android version without loosing /data

[Marine]

No idea ! My OS was offering me this update only.

[Marine]

Can I have some help upgrading to /e/ 3.4 ?

If I refer to your post [HOWTO] Upgrade my /e/OS to major Android version without loosing /data

my phone was running android 12 but I had to downgrade it to android 11 https://community.e.foundation/t/how-to-install-e-r-on-a-samsung-galaxy-s10e-already-running-android-12/38881

I don’t understand question 2 sorry

Do you have any idea if I can do what you call the dirty upgrade?

[piero]

@piero

1. What was the android version of the StockOS installed before /e/ ?

@Marine

my phone was running android 12 but I had to downgrade it to android 11

.

@piero

2. What is the latest available StockOS android version but not higher regarding to the android version of the /e/OS build you want to install ?
   Or what is the precise StockOS version required as a base to install the /e/OS build you want to install

@Marine

I don’t understand question 2 sorry

according to Install /e/OS on a Samsung Galaxy S10e - “beyond0lte” :

.

@piero

3. does latest /e/ build include the upgraded needed parts of the firmware ?

so : yes.

.

@piero

4. does Lineage wiki offer a firmware upgrade solution for this device ?

Update firmware on beyond0lte | LineageOS Wiki

so yes, but uneeded because answer to question (3) is yes.

.

@Marine

Do you have any idea if I can do what you call the dirty upgrade?

CONCLUSION :
because anxwer to question (3) is yes you can proceed without specificaly prior installing stockOS or firmware parts as they are included

[Marine]

Thank you so much ! It’s difficult for me to understand all of this

I’ll try soon !

@piero Is it still possible to get a bootloop? Or if the phone can’t do the update, I will still get my old OS?

Juste worried that my phone freezes again !..

[piero]

@Marine

It’s difficult for me to understand all of this

please make propositions, i will be happy to integrate them to make the guide clearer.

@Marine

Is it still possible to get a bootloop? Or if the phone can’t do the update, I will still get my old OS?
Juste worried that my phone freezes again !..

i cannot answer other than “it is not expected”.

it is always advised to take a backup in case…

[Marine]

I am not sure how you could improve it ! I feel it is like learning a new language, it takes time and some effort…

I tried the dirty upgrade but I got this recovery screen (I wasn’t expecting it). Shoud I follow the steps of the“Universal Method” you described? I am confused!

I tried apply update but I just have as only option “apply from adb”

[piero]

option (1) (don’t need a PC) should work on a device running android 13 based /e/OS…

option (2) and (3) (don’t need a PC) not all devices have the feature…

option (4) (need a PC) works in all case…

@piero

1. download the file on the phone, go to “→ settings → system updater” and use the feature called “locale update” (if you have it in the “3 dot menu” at top right of the screen).

or

2. download the file on the phone, reboot the phone into the recovery mode and use “apply update” then “from internal storage” (if your “recovery mode” have the feature).

or

3. download the file on a SDcard, reboot the phone into the recovery mode and use “apply update” then “from External SDcard” (if your “recovery mode” have the feature).

or

4. Universal Method, download the file on a computer, boot the phone into the recovery mode and use “apply update” then “from ADB” :

[Marine]

I did the option 1 but while rebooting, I got the recovery screen. Weird no?

@piero should I follow step 4 ?

[Marine]

Ok So I tried to follow step 4 …
Unfortunately I got this screen, I believe it didn’t work? If I try to reboot I get this message “previous installation has failed. Your device may fail to boot if you reboot now”. What sould I do ?

@piero I am panicking….. I believe I forgot to enable debugging on my phone … But on your /how to/ you didn’t recall how to access recovery mode and I probably did it the wrong way…
Can I reboot my phone ?.. or it won’t work anymore with the “installation aborted”?

[piero]

@Marine

I forgot to enable debugging on my phone

i just corrected that point in the guide…

@Marine

Can I reboot my phone ?.. or it won’t work anymore with the “installation aborted”?

i don’t know, you will need to try.

@Marine

@piero I am panicking…..

if it don’t boot, i have an idea…

.

(also i see on your phone screenshot that “recovery-e need to be updated”)

[Marine]

@piero

i don’t know, you will need to try.

Ok so I rebooted and fortunately I still have my old OS… But I am not confident at all in trying to upgrade again … I really don’t want to formate my phone. It’s not that “easy upgrade” after all

@piero

(also i see on your phone screenshot that “recovery-e need to be updated”)

What should I do about it ? How do you launch e-recovery?

[piero]

i reconise a “Windobe” screen,
so you need “Odin3” to upgrade your recovery to “recovery-e-3.4-a15.tar”
then you will be able to sideload the main /e/.zip file

In the following guide, where it is noticed TWRP, use your new recovery-e instead

@piero

3. Put your smartphone in download mode (see above how to do this).
   The display differs according to the version of Android, here 6.0.1 Marshmallow.

4. Connect your smartphone to your computer with a reliable cable.
   The word “Added” should appear on Odin. This means the smartphone in download mode is detected.

If nothing happens, it means your computer doesn’t have the necesary drivers. So you need to install them, by following the steps of the following 7) part. Sometimes you just have to wait a few minutes that Windows install them automatically.

in the “Options” tab (between “Log” and “Pit”) untick the “Auto-reboot” box.

5. Click on “AP”, then select the TWRP file in .tar format previously downloaded.

6. Click on “Start” to start installing TWRP on your device. It will take a few seconds. Once finished, Odin will display in a green box “PASS”.WARNING :

.

…NOW COMES THE CRUTIAL STEP !..

• To get out of the Download mode you must Force Power Off your Samsung device,
  (on some old devices, unplug the device,)
  hold Volume Down + Power.
  release when you see the screen turn off..

…IT IS THE CRUTIAL STEP !..

• immediately Boot to Recovery before any other boot mode attempt,
  hold Volume up + Home + Power
  release Power when you see the very little blue line in the top of the screen…

…IT WAS THE CRUTIAL STEP !..

.

Install the necessary drivers if needed

In order for your smartphone to communicate with the computer, and therefore be flashed, you must install the necessary drivers. (If you have already successfully installed TWRP, skip this step.)

1. Download them directly from an unofficial source .
2. Unzip the downloaded directory.
3. Open the unzipped directory created and launch the utility (the file ending by “.exe”).

4. Click on “Yes” in the Windows warning message and follow the steps indicated.
   Perfect, your device can now correctly communicate with Odin.

[Marine]

Why can’t I use the Universal Method ?

Is it going to erase my data?

[piero]

From your previous attempt, result the need of upgrade the recovery prior, then use it to upgrade /e/

As already said : do not apply any “factory-reset” nor format /data partition otherwise you will loose your data.

[piero]

No news, good news ?
Must i consider you succeed ?

[Marine]

Hi !
I didn’t try yet as my phone is my only way to get internet, I am afraid that I won’t succeed !..

I won’t forget to tell you if it worked or not once I tried…