Difference between revisions of "ASUS Transformer Pad (asus-tf300t)"

From postmarketOS
Jump to navigation Jump to search
m (Contributor changes + Line up codename with the rest of the devices table)
Line 2: Line 2:
| manufacturer = ASUS
| manufacturer = ASUS
| name = Transformer Pad
| name = Transformer Pad
| codename = tf300t
| codename = asus-tf300t
| image = File:ASUS Transformer Pad.jpg
| image = File:ASUS Transformer Pad.jpg
| imagecaption = ASUS Transformer Pad
| imagecaption = ASUS Transformer Pad
Line 39: Line 39:
* jonty-comp
* jonty-comp
* Jasper (working on [[ASUS Transformer Pad Infinity]])
* Jasper
* MartijnBraam
* MartijnBraam

Revision as of 16:19, 16 January 2020

ASUS Transformer Pad
ASUS Transformer Pad
ASUS Transformer Pad
Manufacturer ASUS
Name Transformer Pad
Codename asus-tf300t
Released 2012
Category testing
Original software Android 4.0 on Linux 3.1
Chipset Nvidia Tegra 3 T30
CPU Quad-core 1.2 GHz Cortex-A9
Display 1280x800 IPS
Storage 16/32 GB
Memory 1 GB
Architecture armv7
USB Networking
3D Acceleration
Mobile data


  • jonty-comp
  • Jasper
  • MartijnBraam

Compiling a kernel

old CM13 kernel

  • Compiling CM13 kernel (GitHub)
  • Compiling 4.14-rc3 with tf300t specific patches
  • Flashing via Android recovery zip (Boot image included)
  • System boots
  • Most sensors/cameras/devices seem to be detected (e.g. accelerometer values can be read from /sys etc)

Mainline (Grate)

  • Grate is a upstream based tree for tegra devices with the goal of actually upstreaming any changes done. Trying to mainline this device should be relatively doable up to a certain point since the Tegra 3 is well supported on this tree. I'll be basing work on this tablet on the TF300t port since that one is the closest in Hardware.
  • Baseline kernel sources: https://github.com/grate-driver/linux
  • Source: transformers branch https://github.com/okias/linux/tree/transformers (Michal TF300t work)
  • Version: 5.5.0-rc5
  • Status: Boots.

What does not work (downstream kernel)

  • Flashing via fastboot (device appears to write successfully but then locks up and does not apply the uploaded image)
  • Framebuffer (stuck on ASUS bootloader graphic)

The framebuffer issue is an interesting one as it works without issue on CM13-based Android ROMs with the same kernel and defconfig. Possible toolchain issue or patch needed for GCC6. Devices with a working framebuffer output modesetting information in dmesg after loading the tegradc driver, but the PMOS compiled kernel does not. Common fixes including setting values in /sys have no effect yet.


The first step to do anything with the device is unlocking, with this device its done by sideloading the unlock apk from asus and clicking a few buttons in the app. The apk can be found on the asus support page.

Fastboot issue

It seems like the bootloader doesn't handle flashing the boot and userdata partition correctly, the official firmware package flashes an "Android blob" to the staging partition with fastboot which triggers an flashing screen on the tablet which copies the data to the correct partitions.

After unlocking the device the blobs still needs to have some signature which can be generated by drwowe/BlobTools. This repository adds the -s option to sign the generated blobs.

$ ./pmbootstrap.py export /example
$ blobpack -s output.blob LNX /example/boot.img-asus-tf300t APP asus-tf300t.img
Found 2 partitions as commandline arguments
Partname: LNX Filename: boot.img-asus-tf300t
Partname: APP Filename: asus-tf300t.img
Size: 60
2 partitions starting at offset 0x3C
Offset: 92
$ fastboot flash staging output.blob
target didn't report max-download-size
sending 'staging' (680522 KB)...
OKAY [113.288s]
writing 'staging'...
FAILED (remote: (InvalidSize))
finished. total time: 116.623s

The update doesn't get updated yet with this code but at least the bootloader doesn't freeze anymore after the flashing command.

See also