Upgrade from 1.19.1-s-20240112372761-dev-vayu to current version/ saving all data peviously

Hello,
i searched online for about an hour, didn’t find a solution.
So:
i finally decided to upgrade from android 12 to 14. To save all my data, i think i have to root. to do that via magisk, i have to extract the boot.img from my os (see above). Correct?
I just don’t find it anymore.
Is it possible to still download my current os-version?
If not, is there any other way to save all app-data?

Thank you for help,
best from Robert

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

That might be the way to go, idk.

I would suggest when attempting upgrade from “2024-01-12” that to capture a backup is the highest priority right now.

For to follow the way i know i need the exact firmware (1.19.1-s-20240112372761-dev-vayu).
Where can i still download it? Does anybody know that? The reason for this is that i want to extract the boot.img.

One last try:

I tried several ways for rooting suggested on the net. Didn`t work.

The murena help team won`t help me because i didn`t buy the phone at murena (says so when trying to contact them). i spent days reading on the net and trying to root.

So: Does anybody know a way to gain access to the old 1.19.1-s-20240112372761-dev-vayu in order for me to exract boot.img?

“Magisk” should works..

Builds older than october 2024 are unavailable,
why not simply upgrading to current e-3.2-t ? /e/OS community vayu download

@piero:

Unfortunately, Magisk only works if there is something to patch. Which i was looking for.

Thank you for the suggestion of dirty upgrade. I`ll try it after saving all the data i can without root. (In case of data-loss i would then lose a few important ones, otherwise i wouldn`t make such a fuss).

do you have TWRP installed ?

Yes i have it installed.

sorry i have to go out for some hours,
but i think about the command line “DD” feature, we need to find the block number of the BOOT partition and so we can copy it from the device…

Thank you. Would be great if that worked. I’ll google it without google….

In case you want to help me further, take all the time you need. I waited nearly 2 years, Because the updates stopped. Didn`t know i had to take another way to upgrade to the next android-version. Thought e os was discontinued for my device. Won`t happen again!

1 Like

We will try to indentify partition number

  • on the PC, Download the parted binary
  • boot the device in TWRP mode
  • on the PC open a terminal from where the binary is located
adb push parted /sbin
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0

.

you should see something like :

Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name      Flags
 1      4194kB  8389kB  4194kB               BOTA0     msftdata
 2      8389kB  12.6MB  4194kB               BOTA1     msftdata
 3      12.6MB  33.6MB  21.0MB  ext4         EFS       msftdata
 4      33.6MB  41.9MB  8389kB               PARAM     msftdata
 5      41.9MB  50.3MB  8389kB               BOOT      msftdata
 6      50.3MB  58.7MB  8389kB               RECOVERY  msftdata
 7      58.7MB  92.3MB  33.6MB               RADIO     msftdata
 8      92.3MB  1166MB  1074MB  ext4         CACHE     msftdata
 9      1166MB  2777MB  1611MB  ext4         SYSTEM    msftdata


.

please share the BOOT partition number