Land Rover A9 (landrover-a9)
Appearance
	
	
| This device is marked as not booting. Status: not booting, no active contributor | 
| Manufacturer | Land Rover | 
|---|---|
| Name | A9 | 
| Codename | landrover-a9 | 
| Hardware | |
| Chipset | MediaTek MT6582 | 
| CPU | Quad-core 1.3 GHz Cortex-A7 | 
| GPU | Mali-400 MP2 | 
| Display | 480x854 | 
| Storage | 8GiB | 
| Memory | 1GiB | 
| Architecture | armv7 | 
| Software | |
| Original software The software and version the device was shipped with. | Android 4.4.2 | 
| Extended version The most recent supported version from the manufacturer. | Android | 
| Mainline Instead of a Linux kernel fork, it is possible to run (Close to) Mainline. | no | 
Contributors
- alexlep
Random information
- Obscure phone: - This is just another clone from millions of devices from Chinese manufacturers. 
- MT6582 CPU
- Product code F090_GPS_KK 
Status
- a boot.img file with kernel, initramfs and dtb file from pmOS does not work.
- alexlep has a boot.img file from the vendor somewhere (extracted from the device?), that works when flashed via fastboot boot. It can not be extracted like a normal boot.img file, as reported on IRC. Probably the extraction tool can't handle the files.
- according to alexlep, there is a 512b header in front of the kernel and initramfs: - ramdisk and kernel has 512 bytes added in the beginning of the files - custom header with file description 
- ...and simply prepending that header in front of a custom initramfs/kernel does not work, as he reports. 
extracted boot.img, first bytes of pmOS initramfs (not working):
sp@sppc:~/else/pmbs_work/chroot_native/pmos/extracted$ xxd -l 50 ramdisk 00000000: 1f8b 0800 0000 0000 0203 949a 0d70 1ce5 .............p.. 00000010: 79c7 5fb0 09b2 621b 411d ac16 0317 c7a1 y._...b.A....... 00000020: 0ed8 d6d9 96b1 2026 11b5 70d4 5814 4344 ...... &..p.X.CD 00000030: ea49 .I
extracted boot.img, first bytes of the vendor's initramfs (working):
sp@sppc:~/else/pmbs_work/chroot_native/olololo/extracted$ xxd -l 50 ramdisk 00000000: 8816 8858 f5a7 0c00 524f 4f54 4653 0000 ...X....ROOTFS.. 00000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000020: 0000 0000 0000 0000 ffff ffff ffff ffff ................ 00000030: ffff
Links
- #73 lists lots of issues with the device, and additional information, such as fastboot's partitions output
- This might be the same phone?