Keep it simple (downgrading Android version is bound to carry a risk) … this was the intention of my last message … you initially wanted to experiment with backup.
That is expected, you should be able to copy things to an external SD card if you really need to.
to test if I can run the boot.img.
That is a thing I would not experiment with.
I think no,
Because when “T” builds include needed firmware parts, it was not the case for “S” builds.
Now that the firmware have been upgraded, my through (even not sure) is that will be considered as a downgrade (conflict between custom-android system and expected firmware base)
Yes restoring “S” build should be possible as there were no firmware base modifications in “T” (stockOS based on android 13 don’t exist at my knowledge)
Restoring SamsungOS based on android 12 should still be possible using HOME_CSC file (that preserve /data) with the help of Odin3 windows or Odin4Linux because there is no android 13 based SamsungOS but reinstalling a custom recovery after that will erase /data
Hi again, just an update, I wasn’t able to backup in TWRP. The “System” partition wasn’t showing as an option to select when backing up. I tried it anyway but it failed.
I ended up wiping the system completely and reinstalling /e/ from TWRP from scratch. Took most of the day to set it up with all the apps again using Aurora due to the ongoing App Lounge issues. Do you know if the apps installed via Aurora will update through the App Lounge once the issue is resolved?
Anyway, call this a valuable learning curve. I now know a lot more about how my android works on the back end. And the end result is that TWRP is now my recovery system which is what I was hoping to achieve to begin with. I will be performing a full backup tonight and hoping that I don’t have to do this ever again.
Appreciate the good support from both of you.
The inverse is true, so maybe…
You mean including the /data partition where apps are
Do not forget to unselect the “update recovery” feature in system updater…
Sorry again for slow reply.
Yes, I wiped the system including the /data partition and reinstalled all non-FOSS apps via Aurora.
I have unchecked “update recovery” in the system updater, appreciate the reminder.
I updated to 2.5 which I thought went well but I suspect it might now be the cause of issues I’m experiencing with calling and mobile data outlined in this post.
Wondering if it’s possible to use the updater to reinstall 2.4.1 to see if it makes any difference to this issue or if it’s only able to go forwards? Is there a recommended way to rollback the version?
It seems to vary by device … does your updater offer “local update” in 3 dot menu top right ? This would permit you to download 2.4.1 to an accessible location and attempt to apply it. My guess would be that it would refuse to downgrade Android SPL.
Quoting
Releases · e / os / 🚀 Releases · GitLab
This /e/OS v2.5 version includes the Android security patches available as of October 2024.
This /e/OS v2.4 version includes the Android security patches available as of September 2024.
As you have TWRP, you could try TWRP to to downdate to 2.4.1.
I tried just now e-Recovery simply correctly refuses as this is seen as a downgrade.
I say correctly, Android says “never go back”.
However TWRP 3.7 might co-operate with you, but it should also refuse, imo.
I would warn though, say that succeeds, but phone still fails, as “Phone app - calls not connecting - making or receiving” you will still not know from a forensic troubleshooting point of view if your “non standard install” using TWRP was responsible.
Hey again, following your advice, I used TWRP to install v2.4.1 which did actually work and I am yet to find any issues with doing that, all apps were still there and functioning as they were, except that it didn’t solve the problem and I still can’t call.
My carrier is not on that list on carries not supporting /e/ but in the other post I have going about the calling issue (linked above) it was suggested that Australia phasing out 3G at the moment could be related.
Prior to these issues I did attempt a backup using TWRP (which was my whole reason for wanting TWRP in the first place) and this was the result. I googled the “required key not available” error and found that it’s to do with the encryption and the few that had managed to get around it were not using Samsung phones and the solutions were beyond my capability/understanding to even attempt.
This leaves me at a bit of a standstill. If I can’t make or receive calls then /e/ is not a viable choice for me with my current hardware and location, which is disappointing because I have been very impressed with it overall.
Any further troubleshooting suggestions welcome but I feel like I’ve been leaning on knowledgeable members of this community very hard and only contributing problems so far.
Thanks to those who have tried to help!
official TWRP (and LOS) maintainer Instructions :
Hi Piero. Apologies for the late reply once again.
With regard to the calling issue, the reasons for this have been clarified in the linked topic and are to do with the switching off of the 3G network in Australia (nothing to do with /e/ directly) so I won’t discuss that any further here.
About the backup issue, did you link the TWRP maintainer instructions for clarity in the thread or is there some information I have missed about the “required key not available” error?
I can’t remember exactly, but should be for you to read the last red parts that could be related to your issue.
This topic was automatically closed after 90 days. New replies are no longer allowed.
