[Android Software/Hacking General [Developers Only]] domenictroilo:
I have purchased a new Honda Pilot and it has an android head unit. https://xdaforums.com/android/help/heard-2016-honda-pilot-android-based-t3141346

Some very cleaver people have enabled root. https://xdaforums.com/android/general/guide-how-to-gain-root-shell-2016-honda-t3487644

I want to install a navigation application, that does not use the internet to grab maps, but stores them locally but there is only 800 MB of space left on the device. I am looking to increase the amount of usable space (ext4 filesystem of course) so I can use a tool such as fmount to move the data directory of any application to a different device.

I have purchased a USB stick and Partitioned it as follows:

Device Boot Start End Sectors Size Id Type

/dev/sdg1 8064 47729114 47721051 22.8G c W95 FAT32 (LBA)

/dev/sdg2 47729115 60500789 12771675 6.1G 83 Linux​

The first part for music and the second for storage!

When android starts up I have the follows mounts:

shell@android:/ $ mount

rootfs / rootfs rw 0 0

/dev/root / ext4 ro,relatime,data=ordered 0 0

devtmpfs /dev devtmpfs rw,relatime,size=401076k,nr_inodes=100269,mode=755 0 0

tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

tmpfs /acct tmpfs rw,relatime 0 0

tmpfs /cache tmpfs rw,relatime 0 0

tmpfs /config tmpfs rw,relatime 0 0

tmpfs /mnt tmpfs rw,relatime 0 0

tmpfs /storage tmpfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

/dev/root /system ext4 ro,relatime,data=ordered 0 0

tmpfs /tmp_database tmpfs rw,nosuid,nodev,noatime,nodiratime,size=65536k 0 0

tmpfs /tmp tmpfs rw,relatime 0 0

/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0

/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/block/mmcblk0p5 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0

/dev/block/mmcblk0p6 /var/log ext4 rw,nosuid,nodev,noatime,nodiratime,nomblk_io_submit,noauto_da_alloc,errors=remount-ro,data=ordered 0 0

/dev/block/mmcblk0p7 /vrdata ext4 rw,nosuid,nodev,noatime,nodiratime,nomblk_io_submit,noauto_da_alloc,errors=remount-ro,data=ordered 0 0

/dev/block/vold/8:1 /mnt/usb3 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/8:2 /mnt/shell/emulated/0 ext4 rw,relatime,data=ordered 0 0
​

Note that my primary partition is mounted as /mnt/usb3 and the second part is mounted as /mnt/shell/emulated/0 which is GREAT! But as you can see from the mount command there are no options on the mount so it is completely unusable. The other oddity is the directory "Android" is created on the /mnt/shell/emulated/0 file system every time I start up (boot process is creating this directory). I have tried to install some tools to allow me to automatically mount the partition such as scriptmanager and universal init.d but the unit is over writing something in the boot process and disabling any method to auto start scripts.

I don't need to modify the kernel, but I believe I do need to modify the init process. I have some experience with other ARM android devices but would like a little direction here.

I don't have it handy (from memory here) but /dev/block contains the following filesystems:

shell@android:/ $ cat /proc/partitions

major minor #blocks name

31 0 256 mtdblock0

31 1 256 mtdblock1

31 2 256 mtdblock2

31 3 256 mtdblock3

31 4 256 mtdblock4

31 5 4096 mtdblock5

31 6 64 mtdblock6

31 7 64 mtdblock7

31 8 64 mtdblock8

31 9 64 mtdblock9

31 10 4096 mtdblock10

31 11 4096 mtdblock11

31 12 256 mtdblock12

31 13 512 mtdblock13

31 14 64 mtdblock14

31 15 64 mtdblock15

31 16 64 mtdblock16

31 17 256 mtdblock17

31 18 64 mtdblock18

31 19 64 mtdblock19

31 20 64 mtdblock20

31 21 64 mtdblock21

31 22 64 mtdblock22

31 23 64 mtdblock23

31 24 64 mtdblock24

31 25 64 mtdblock25

31 26 64 mtdblock26

31 27 64 mtdblock27

31 28 64 mtdblock28

31 29 64 mtdblock29

31 30 576 mtdblock30

179 0 3842048 mmcblk0

179 1 257008 mmcblk0p1

179 2 899640 mmcblk0p2

179 3 257040 mmcblk0p3

179 4 1 mmcblk0p4

179 5 771088 mmcblk0p5

179 6 257008 mmcblk0p6

179 7 1204843 mmcblk0p7

259 0 128488 mmcblk0p8

179 16 1024 mmcblk0boot1

179 8 1024 mmcblk0boot0
​

Domenic

edit: updated list of filesystems in /dev/block