Land Rover A9 (landrover-a9): Difference between revisions
Appearance
m replace link with working one |
m added infobox |
||
Line 1: | Line 1: | ||
{{Infobox device | |||
| manufacturer = Land Rover | |||
| name = A9 | |||
| codename = landrover-a9 <!-- e.g. htc-bravo --> | |||
| image = File:landrover-a9.jpg | |||
| imagecaption = CHANGE_ME | |||
| releaseyear = CHANGE_ME | |||
| originalsoftware = Android 4.4.2 | |||
| chipset = MediaTek MT6582 | |||
| cpu = Quad-core 1.3 GHz Cortex-A7 | |||
| gpu = Mali-400 MP2 | |||
| storage = 8GiB | |||
| display = 480x854 | |||
| memory = 1GiB | |||
| architecture = armv7 | |||
<!-- the following status_* questions should be answered with Y - yes, P - partial, N - no, or left blank (for untested or unknown) --> | |||
| status_usbnet = <!-- USB networking does work? then put Y here and delete this comment --> | |||
| status_flashing = <!-- Flashing with "pmbootstrap flasher" works? Put Y here. It works the same for everything coming below. --> | |||
| status_touch = <!-- Touch screen is working? You can also answer these questions with P for partially. --> | |||
| status_screen = <!-- The display is working? --> | |||
| status_wifi = <!-- Wireless network works? --> | |||
| status_xwayland = <!-- Showing X11 applications in a Wayland compositor (Weston, KWin, ...) works? --> | |||
| status_fde = <!-- When installing with full disk encryption, can you type in the password with the on screen keyboard? --> | |||
| status_mainline = <!-- Instead of a Linux kernel fork, it is possible to run mainline. --> | |||
| status_battery = <!-- Charging the battery with charging-sdl is possible --> | |||
| status_3d = <!-- Hardware accelerated 3D graphics (e.g. with freedreno) --> | |||
| status_accel = <!-- The sensor that measures proper acceleration works --> | |||
| status_audio = <!-- Using the device's speakers/headphone jack works --> | |||
| status_bluetooth = <!-- It's possible to pair and use other devices via the bluetooth protocol --> | |||
| status_camera = <!-- Taking photos and videos works. --> | |||
| status_gps = <!-- The Global Positioning System sensor works. --> | |||
| status_mobiledata = <!-- Connecting to the Internet via cellular network. --> | |||
| status_sms = <!-- Sending and receiving short messages works as intended. --> | |||
| status_calls = <!-- Talking to other people over the cellular network. --> | |||
| status = not booting, no active contributor <!-- Text displayed in the "not booting" table on the Devices page , e.g "kernel compiles, doesn't boot" --> | |||
| booting = no | |||
<!-- you can also use these lines if you need to: | |||
Version of the kernel that pmos is running | |||
| pmoskernel = 3.x.x | |||
see Unixbench page on wiki | |||
| whet_dhry = 0.0 | |||
Is OTG available, not used in wiki | |||
| status_otg = - | |||
--> | |||
}} | |||
=== Contributors === | === Contributors === | ||
Revision as of 12:21, 20 September 2019
This device is marked as not booting. Status: not booting, no active contributor |
CHANGE_ME CHANGE_ME | |
Manufacturer | Land Rover |
---|---|
Name | A9 |
Codename | landrover-a9 |
Released | CHANGE_ME |
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 |
Android 4.4.2 |
Extended version |
Android 4.4.2 |
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?