No more OTA Updates for S -- Which steps of the installation guide can I skip to manually upgrade to T?

Hi all, I have a Samsung Galaxy Tab S6 lite (SM-P610 / gtaxlwifi) and it stopped getting OTA upgrades for Android 12 (already since January :face_with_peeking_eye:) so I want to upgrade it manually to Android 13. There is a community build for it.

My question is which steps of the general install guide can I skip? Specifically: Do I need to flash an “up to date”(?) e-recovery? Do I need to use Odin/Heimdall to install a stock Android 13 firmware first? Etc.
Or is it as simple as booting into the old e-recovery of my S /e/ 1.19.1 (the recovery was always OTA-updated together with the OS, right?) and just install the new T /e/ 2.4.1 from there? (what would it be: install, sideload, upgrade, …? (It would be great, if I could keep my apps and data))

Thanks a lot for any help and feedback :sunglasses:
cheers!

PS, side question: would the “community build” also get OTA Updates
PPS, Wasn’t it announced at some point that OS-Upgrades would also be possible via the OTA Updater? Or is this just for some specific devices?

1 Like

From what I know, this applies exclusively to devices that Murena sells (or sold) in their store. However, users who got such a device elsewhere and installed the official (formerly called stable) version themselves also profit from this convenience.

2 Likes

It depend of the device, (i am quite confident in your case)
check if the e-2.4.1-t-20241009439852-community-gta4xlwifi.zip include the firmware parts…

Install platform-tools on a computer
Installing adb and fastboot on a Linux PC
Installing adb and fastboot on Windows PC

Download the e-2.4.1-t-20241009439852-community-gta4xlwifi.zip on the computer, (put it into the platform-tools folder)
.
Boot the phone into recovery mode.
.
Select Apply Update, then Apply from ADB

The screen should now change and the output at the bottom ask you to send the package from your computer.

On the computer issue command to sideload the eOS installation zip.

adb sideload e-2.4.1-t-20241009439852-community-gta4xlwifi.zip

the phone screen will be mostly blank with just the output at the bottom showing progress.
(Do not take attention to the wipe related things on the photo !)

On the computer the sideloading shows progress as a percentage figure that will stop at 47%. The phone will still be installing though (even though it might feel like nothing is happening sometimes!) and you can expect to see the following screens (excepting the wipe related things)

Then press the arrow at the top of the screen to return to Home Screen

Tap Reboot system now to boot into eOS.

4 Likes

Wow – thanks a lot for all the details, this is great! And sorry I did not find your original thread but I was not aware of that this process is called “dirty upgrade” :thinking: :wink:

check if the e-2.4.1-t-20241009439852-community-gta4xlwifi.zip include the firmware parts

there is a folder called firmware inside. but it is only ~10 MB large and it contains

cm.bin
keystorage.bin
sboot.bin
uh.bin
up_param.bin

is that it and is it enough?

One more question (I am a bit afraid of the process as I already completely bricked one of these tablets (same model) once when the firmware flashing with heimdall did not work right away and then the battery ran out and the tablet does not charge anymore if it does not have anything installed): In case this “dirty upgrade” goes wrong, would the old system still be there? or would at least the recovery still be on there (likely yes, right) and does this allow me to charge the tablet?

thanks again for your help! :star_struck:

Yes, exactly !

Samsung devices are quite unbrickable,

Ok, it won’t charge when in download mode, but you can turn it off with “volume down” + “power”.
Then it will charge when off, or in recovery mode or normal mode.

Using Odin3 Windows or Galaxy-Flasher Linux, it is quite easy to reinstall stock SamsungOS as a sane base to reinstall the recovery-e and finaly /e/OS

1 Like

hey, thanks a lot again. it worked and all my data are still there! :+1:

do you know by any chance whether it is safe to now lock the bootloader again?

PS, wanted to report in the other thread that it worked for my device. unfortunately, it is already closed – maybe you could (ask to) open it again and then people could keep reporting the result for their devices? – i think it would be useful for anybody trying to do the same …

This topic was automatically closed after 90 days. New replies are no longer allowed.