Setedit Does Not Currently Support Editing This Table [upd] -
The error message "SetEdit does not currently support editing this table" typically appears when a user attempts to modify values in the Secure or Global tables without having granted the application the necessary elevated permissions via Android Debug Bridge (ADB). Cause of the Issue
Lack of Root Access: Some edits, especially those to system tables, require root access. Without it, certain modifications are off-limits. setedit does not currently support editing this table
However, a frustrating wall often appears when you try to modify a value. You tap on a setting, attempt to change it, and are met with the dreaded red error notification: "setedit does not currently support editing this table." The error message "SetEdit does not currently support
Missing ADB Permissions: Without the specific WRITE_SECURE_SETTINGS permission, the app is "locked" from making changes to these critical tables. However, a frustrating wall often appears when you
Manufacturers often add custom tables or alter the schema of existing ones to support proprietary features. If setedit encounters a table with a non-standard structure—perhaps a binary blob instead of a string or integer—it may default to a read-only mode to prevent database corruption. In these cases, the error is not a permissions issue, but a compatibility issue. The tool essentially says, "I see this table, but I do not recognize the format well enough to safely edit it."
The Full Error Explained
When you open SetEdit and try to switch to the Secure Table or Global Table, you might see the dreaded message:
