View Single Post
Old 03-10-2022, 05:50 AM   #15
Renate
Wizard
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 2,526
Karma: 10479009
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
Not really. The problem is getting the whole /system partition to be exactly as it was.

On my Poke3 the fstab is /vendor/etc/fstab.qcom and includes:
Code:
/dev/block/bootdevice/by-name/system  /  ext4  ro,barrier=1,discard  wait,verify
The "verify" means to use dm-verity to ensure that no part of /system has been modified.
We could modify that, but /vendor is also verified earlier on and its "fstab equivalent" is in the device tree:
Code:
vendor {
	compatible = "android,vendor";
	dev = "/dev/block/platform/soc/c0c4000.sdhci/by-name/vendor";
	type = "ext4";
	mnt_flags = "ro,barrier=1,discard";
	fsmgr_flags = "wait,verify";
	status = "ok";
};
Yes, we can work around all of this but it will make problems when we get incremental updates from Onyx.

Two solutions:
1) Use Magisk and don't touch /vendor or /system
2) Make backup copies of /vendor and /system, modify what you like, when it comes time for an update restore the stock backups, update and remod.

Also: There is no reason to delete an app; simply pm disable the package or component if you have root.
Renate is offline   Reply With Quote