Long time no see. I got new Sony Xperia Z Tablet (WiFi, not LTE one) to play with and I thought that it would be nice device to run our openSUSE with my Enlightenment on that to combine cool hardware and cool software.
It seems that there is not much project targeted on running full blown Linux distribution on Android devices. You can meet Replicant (which is great anyway), you can meet Ubuntu Touch but that is almost all. So I decided to revive my old blog and write here my notes.
I played in past with HTC Desire Z with the same desire, but as I had very little time in the end, I didn't progressed significantly beyond interesting Hackweek project. I hope that this time it will do better and at least it is not my only mobile I'd wreck :)
I started with rooting the device, which was very simple thanks to the article on unlockr and the work of DooMLoRD. I prepared then openSUSE chroot on microSD card, automated chrooting process and installed some basic tools (gcc, git, mosh + ssh) and E17. To see I have working installation I used Android's native XWindow implementation.
To boot openSUSE I'd need to boot kernel with something like
root=/dev/block/mmcblk1p4(where my openSUSE partition is) or even provide my initramfs which will take care of mounting and other needed stuff. To be able to boot without bricking I need to find way how to provide kernel to bootloader without changing contents of flash.
fastbootshould do the job (at least it did with my HTC Desire Z attempts).
It seems that I can't influence kernel parameters for now so let's build own kernel with root device settings hardcoded. Sony provides repository with kernel source on github. Kernel configuration was not present so I took the one from Cyanogenmod project.
Let's have a look on internal flash to find some more information:
# fdisk -l /dev/block/mmcblk0 WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion. Disk /dev/block/mmcblk0: 15.8 GB, 15758000128 bytes, 30777344 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: gpt # Start End Size Type Name 1 256 4351 2M unknown TA 2 4352 4607 128K unknown sbl1 3 4608 5119 256K unknown sbl2 4 5120 5631 256K unknown s1sbl2 5 5632 6655 512K unknown sbl3 6 6656 7679 512K unknown aboot 7 7680 8703 512K unknown tz 8 8704 8959 128K unknown alt_sbl1 9 8960 9471 256K unknown alt_sbl2 10 9472 9983 256K unknown alt_s1sbl2 11 9984 11007 512K unknown alt_sbl3 12 11008 12031 512K unknown alt_aboot 13 12032 13055 512K unknown alt_tz 14 13056 14079 512K unknown rpm 15 14080 15103 512K unknown alt_rpm 16 16384 49151 16M Linux filesyste LTALabel 17 49152 90111 20M unknown boot 18 90112 91671 780K unknown modemst1 19 94208 95767 780K unknown modemst2 20 98304 99863 780K unknown fsg 21 99864 110103 5M unknown ramdump 22 110104 126487 8M Linux filesyste apps_log 23 126488 159255 16M unknown FOTAKernel 24 159744 4354047 2G Linux filesyste system 25 4354048 5480447 550M Linux filesyste cache 26 5480448 6266879 384M Linux filesyste B2B 27 6266880 30535646 11.6G Linux filesyste userdataAnd some basic identification of the partitions:
# file -s /dev/block/mmcblk0p{1..27}
/dev/block/mmcblk0p1: data
/dev/block/mmcblk0p2: data
/dev/block/mmcblk0p3: data
/dev/block/mmcblk0p4: data
/dev/block/mmcblk0p5: data
/dev/block/mmcblk0p6: Hitachi SH big-endian COFF object, not stripped
/dev/block/mmcblk0p7: data
/dev/block/mmcblk0p8: data
/dev/block/mmcblk0p9: data
/dev/block/mmcblk0p10: data
/dev/block/mmcblk0p11: data
/dev/block/mmcblk0p12: Hitachi SH big-endian COFF object, not stripped
/dev/block/mmcblk0p13: data
/dev/block/mmcblk0p14: data
/dev/block/mmcblk0p15: data
/dev/block/mmcblk0p16: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
/dev/block/mmcblk0p17: ELF 32-bit LSB executable, ARM, version 1, statically linked, stripped
/dev/block/mmcblk0p18: data
/dev/block/mmcblk0p19: data
/dev/block/mmcblk0p20: data
/dev/block/mmcblk0p21: data
/dev/block/mmcblk0p22: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (extents) (large files)
/dev/block/mmcblk0p23: ELF 32-bit LSB executable, ARM, version 1, statically linked, stripped
/dev/block/mmcblk0p24: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
/dev/block/mmcblk0p25: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (extents) (large files)
/dev/block/mmcblk0p26: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
/dev/block/mmcblk0p27: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (extents) (large files)
I have read somewhere that there is different format used than boot.img. I also found that there is already tool for extracting this format. Unfortunately it didn't work for me.
Fortunately the format was ELF executable used as container and we have tools for analyzing or manipulating that. So, it seems that FOTAKernel is kernel and initramfs in single ELF executable in mmcblk0p23.
# readelf -a mmcblk0p23-FOTAKernel ELF Header: Magic: 7f 45 4c 46 01 01 01 61 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: ARM ABI Version: 0 Type: EXEC (Executable file) Machine: ARM Version: 0x1 Entry point address: 0x80208000 Start of program headers: 52 (bytes into file) Start of section headers: 7720040 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 2 Size of section headers: 40 (bytes) Number of section headers: 1 Section header string table index: 0 Section Header: [Nr] Name Type Addr Off Size ES Flg Lk Inf Al [ 0]You can see two program headers, offsets and filesizes. First entry is kernel's. To extract kernel you can simply use dd:LOUSER+53494e 00000000 75bc68 001000 00 0 0 0 Key to Flags: W (write), A (alloc), X (execute), M (merge), S (strings) I (info), L (link order), G (group), T (TLS), E (exclude), x (unknown) O (extra OS processing required) o (OS specific), p (processor specific) There are no section groups in this file. Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x000074 0x80208000 0x80208000 0x581698 0x581698 0 LOAD 0x58170c 0x82200000 0x82200000 0x1da55c 0x1da55c 0 There is no dynamic section in this file. There are no relocations in this file. No version information found in this file.
$ dd if=/dev/block/mmcblk0p23 of=vmlinuz skip=$((0x74)) count=$((0x581698)) bs=1To get to contents of initramfs you have to do some more steps:
$ dd if=/dev/block/mmcblk0p23 skip=$((0x58170c)) count=$((0x1da55c)) bs=1 | zcat | cpio -id
So, now I have original initramfs I can modify to boot from microSD card after all that HW specific black magic, I have kernel to use, so experiments with boot can start next time.
republished to get to planet.opensuse.org page
Žádné komentáře:
Okomentovat