No description
- Makefile 85.3%
- Shell 14.7%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| diagnostics | ||
| prebuilt | ||
| recovery/root | ||
| sepolicy/vendor | ||
| tools | ||
| Android.mk | ||
| AndroidProducts.mk | ||
| BoardConfig.mk | ||
| CMD_0X18_INVESTIGATION.md | ||
| device.mk | ||
| README.md | ||
| recovery.fstab | ||
| twrp_sycamore_row_5G.mk | ||
| V15_SOTER_PRE_0X18_STATIC_AUDIT.md | ||
| V16_BOOT_DECRYPT_UNLOCK_STATIC_AUDIT.md | ||
| V17_STOCK_THH_IDENTITY_STATIC_AUDIT.md | ||
| V18_STOCK_TEE_IDENTITY_STATIC_AUDIT.md | ||
| VENDOR_BOOT_FRAGMENT_AUDIT.md | ||
Device configuration for Motorola Moto Pad 2026 (codenamed "sycamore_row_5G")
The Motorola Moto Pad 2026 / XT2575-4 (codenamed "sycamore_row_5G") is an Android tablet from Motorola Mobility based on the MediaTek MT8755 platform.
This device tree is intended for building Team Win Recovery Project (TWRP).
Device specifications
| Basic | Spec Sheet |
|---|---|
| Model | Motorola XT2575-4 |
| Codename | sycamore_row_5G |
| SoC | MediaTek MT8755 (MT6835 platform) |
| CPU | 64-bit ARM, Cortex-A76 / Cortex-A55 |
| GPU | ARM Mali |
| Shipped Android Version | Android 15 |
| Tested Stock Firmware | Android 16 / ZUI 17.5 |
| Storage | UFS |
| Display | 2560 x 1600 pixels, 90 Hz |
| Partition Scheme | A/B, Virtual A/B, Dynamic Partitions |
| Encryption | File-Based Encryption (FBE v2) with metadata encryption |
| Filesystem | F2FS userdata, EROFS/EXT4 dynamic partitions |
| Recovery Layout | TWRP recovery ramdisk stored in vendor_boot |
| Vendor Boot Header | Version 4 |
Device picture
Device reference
Motorola Moto Pad (2026) - GSMArena
Status
Current state of features:
- Correct screen/recovery size
- Working display
- Working touch
- Screen brightness control
- Power off
- Reboot to system
- Reboot to bootloader
- Reboot to recovery
- Fastboot / fastbootd
- ADB
- Internal storage detected
- External SD card detected
- exFAT external storage
- F2FS userdata support
- EXT4 support
- EROFS support
- Dynamic partition support
- A/B slot handling
vendor_bootv4 support- Stock PLATFORM vendor ramdisk preserved
- TWRP RECOVERY vendor ramdisk fragment
- Metadata encryption successfully decrypted
/datablock device successfully decrypted and mounted- KeyMint service
- Gatekeeper service
- Keystore2 service
- Full FBE decryption
- User PIN/password decryption
- Decrypted
/data/media - MTP
- Vibration / haptics
- USB mass storage export
- TWRP native
vendor_bootinstallation from pristine stock image - All commonly modified partitions exposed for image flashing
Encryption status
Metadata encryption is working and TWRP successfully creates and mounts the decrypted userdata block device.
Current testing reaches the Android hardware-wrapped storage key path but fails during system-wide fscrypt key initialization.
The current failure occurs in the MediaTek Beanpod KeyMint trusted application while processing storage-key conversion:
cmd 0x18 / cmd 24
km_error = -33
AES_decrypt_ctr:
decrypt keyblob compare hash failed
DeserializeAuthEncryptedBlob:
decrypt keyblob failed (-33)
**Copyright (C) 2023 A-Team Digital Solutions**
