It has been observed to me that of course I can just change fstab to make the filesystem writable...I have gotten too used to locked-down devices
Still, the question stands, what is the right way to flash a build as though it were an OTA update?
It has been observed to me that of course I can just change fstab to make the filesystem writable...I have gotten too used to locked-down devices
Still, the question stands, what is the right way to flash a build as though it were an OTA update?
@kugiigi Unfortunately what I tested on my device was creating my own script and systemd service that do what I want, but the proper implementation is to merge the functionality into an existing script. So the theory is tested, but the exact code is not.
As far as I can tell there is no way to just modify the existing script on my device because the filesystem is read-only, but please correct me if I'm wrong.
Hello, n00b question incoming. I am very very new to UBT and mobile device development.
I am running an f(x)tec pro1X. I want to push a change to one of the python scripts in the port. I've already done enough to confirm that my change is theoretically sound, but naturally due dilligence says that I should actually do a system image build and test it.
The instructions with the port seem to be for doing a full reinstall with a wipe:
https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x
Is it possible for me to just modify the immutable image (like a system update)? This phone isn't a daily driver, but I don't want to wipe it out either. I assume I just need to do a subset of those steps, but I don't know which ones.
Thanks!