Can confirm.. for rooted/dual-boot linux, I get "error: partition table not match".
I know it's still early stages, but I do hope an update path becomes available for rooted or dual-boot phones. Even a manual process would be fine, as long as we don't have have to "factory reset" each time.
For now, I'll "wait and see".
Yes.
I have dual boot Android/Linux (not rooted), and that is the message I got.
If dual boot was an unauthorized hack, this would be understandable, but as it was a major selling point, it does not reflect well upon them that their Android Firmware Update does not allow for a dual boot partition table.
Since the installation software for the dual boot system requires you to set the size of the Android/Linux partitions on-the-fly a firmware update that requires a specific partition size rather than a properly identified partition of at least X size is not going to work.
Since I don't believe that you have to reinstall your various apps after applying an update, it can't be a complete overwrite of the partition. That would argue that it modifies the partition contents selectively, since it wouldn't be possible to retain already installed third party apps otherwise. If it can selectively modify the partition contents, it should not require a set partition size, just a partition that is sufficiently large and properly labelled such that it knows it is the appropriate partition.
"Should" and "actually possible", of course, may not be the same thing at all. Given that firmware updates are manufacturer specific, I suspect that the standard practice of validating a device for a firmware upgrade is to check it against a template physically describing the device. Such a description would include where the firmware resides. If there is a dedicated chip for the firmware, this would not be a problem. But, if the firmware resides on the same physical media as the OS, it is possible that it would actually require a specific partition table structure for the OS to confirm that it is a compatible device. Given that the installation process for the dual boot Android/Linux allows you to set your partitions to pretty much whatever size you desire so long as they are large enough for the respective OSes to install, there is no "standard" partition table for a dual boot system when you include size of the partitions as part of the description, and thus if the Android OS actually requires a defined partition table, including size of partitions, for a firmware upgrade, and it isn't possible to provide that interactively during the firmware upgrade process, we're SOL. Unless there is a means to apply the firmware update via another OS which would allow for a variable partition structure in the target device.
Um, is that a logical analysis? Am I off-base in my chain of reasoning? And does it reflect reality? I have to admit to working in a vacuum in regard to how the Android OS operates, and how firmware updates are vetted prior to installation, and how they are actually installed after passing that vetting process.
~~~~
