@piero Thanks for informations. May I ask you for further help? For me it would be the third time flashing a device, that’s why I still feel insecure about it.
I would like to install eOS with heimdall. Is this the way to do that:
Downloading eOS and TWRP on PC
Allow flashing (USB debugg. & OEM unlock)
Unlocking the bootloader by:
$ adb reboot bootloader
$ heimdall print-pit
Flashing TWRP: Re-anable Dev. Options for USB debug.
$ adb reboot bootloader
THE CRUTIAL PART: Booting to recovery
Installing eOS by using adb sideload method
This is the shortened way according to the Unified Install Guide.
But I’m missing the point, how does the TWRP.img get onto the device? Did I overlook that step?
Aaah, I didn’t notice it. Thanks.
But a new question arises. Following a Link inside the xda website (as listed above), it leads me to https://magiskzip.com/install-twrp-recovery-on-samsung-galaxy-a51/
After that I have to install vbmeta, which is no problem using heimdall according to no. 7 of your guide.
Now, how have I to flash the Disable_DM_ Verity ForeceEncrypt.zip? Possible by heimdall or using TWRP and SD-Card?
Done! 1.21-t is flashed. The device runs without problems (so far), only gps has become very slow compared to the previous android stock rom. Thanks to @ronnz98 for the build. As known, USB connection doesn’t work. Next I have to flash the update 2.2-t.
The installation (without odin, via heimdall) was very tedious. At times I thought I had bricked the smartphone. Flashing Vbmeta was acknowledged as an error. This led to a download loop. Nothing worked anymore, not even power off.
Then I took the .tar version of TWRP, unpacked it and transferred the files again using heimdall flash. And after many, many attempts (constant download loop) the TWRP screen miraculously appeared.
TWRP 3.7.1_12 no longer corresponds to the illustrations and steps (partially) as in the Unified Install Guide. I think I stumbled through it quite blindly. Again I had the feeling that the device was bricked (loop). I thought it didn’t matter now, and after I was back in TWRP, I called ADB Sideload and installed the eOS build. Rebooting, after showing for a long time the Samsung logo (panic/disappointment again) the bouncing e appeared !!! Yeahhh…happy.
Perhaps others would also like to flash the A51 to eOS, hence my somewhat longer experience report. This was only the third device I’ve flashed to eOS, so my experience is limited and I’m not an It-expert.
Thanks for the tip. I modified the settings according to the post below, and now it works quite good. In Organic Maps for example the location is found in about 30 sec. Super!
It was a stupid move by me. I wanted to test lineage.os for the device, but the installation via TWRP failed. I installed eOS 1.21 again. After the reboot, the e is stuck in a loop. It is possible to go back to TWRP.
I am sorry that I have to ask for help for my stupidity. Is there a solution?
Thanks. I did the installation again step by step according to the Unified Install Guide, starting at 8) using TWRP. Reboot, but it stucks on the “e” and is going into a loop. Power off of the device is not possible.
I tried again installing LineageOS for this device. The result is the same. It stucks on the logo and is going into a loop.
have you tried to format /data after the installation ?
also even if e-1.21-t is reported as working, e-2.2-t can be buggy…
in the end the recovery-e is mandatory for some builds/devices.
in some case, installation from SDcard reduce the risk of transfer error.
download the file again, or/and verify checksum is an assurance against corrupted file…
restore the device to stockOS-13 may be needed for a complete clean install from scratch.
I can happily announce that I am back to eOS 1.21-t on my device!
After installation this time I didn’t do any wipe, turned off the phone manually, after which it booted again to TWRP. There going to Reboot/System. But I’m not sure if that was the real trigger. Anyway it worked.
I would be very happy if @ronnz98 would check his build 2.2-t to see if there is a bug that prevents booting and leads to a download-loop.
To @ronnz98
Sorry, unfortunately the result was the same as above. After flashing 2.4 and rebooting, the phone started in download mode and stayed in a loop. The reinstallation of 1.21 went smoothly. Then I will probably have to wait for the upgrade to A14.
