I have been analyzing the way flash_two_factory.sh bash script works.
It seems to me images are put in both slots (A and B), with the exception of the logo.bin as well as super.img. Why is that?
Some of us (the users) are currently in the middle of v3.0 update disaster and I have this more general observation with the above. If both slots are touched during the update - do I correctly understand the previous version of the OS would not be accessible any more? If so, is that a wise thing to do? My impression was the whole purpose of those slots was to have a way to recover when things stop working as expected. Do I understand this correctly?
You are talking about the install script where it is considered good practice to harmonise the slots.
The update ROM is a different package with a different filename. In an update situation the slots are expected to “swap”.
1 Like
Explain “harmonize” then. What does it mean?
The “trusty” (sort of) AI tells me this:
In Android, “bootloader slot A” refers to one of two separate bootloader partitions used in the A/B system update architecture. This system allows for seamless updates where one slot contains the current running system, while the other slot can be updated while the device is in use. If an update fails or needs to be rolled back, the device can boot from the previous, working slot (slot A or B).
If so, then this “harmonizing” (the way I understand the word) could become the last nail to the coffin. Agree?
Oh, never mind. I know what you mean. It is the First Time /e/OS install vs. upgrade / update (which apparently and hopefully) uses a completely different scheme to move images to the corresponding partitions. Right?
Then again, it is rather strange to provide this “install” version for the phone that was built for /e/OS and had it pre-installed even before leaving factory. Unsuspecting users might potentially shoot themselves in the foot if things go wrong.
But as others have observed with 3.0 both slots have been written… or is it because of locked bootloader that adb sideload in recovery doesn’t allow sideload to 2.9…?
Who knows what others do on their devices.
At least now we (at least: I) have the understanding: [initial] install != update/upgrade. The latter utilizes the slots the way those slots are intended to be used.