[Android Head-Units] donaldta:
Well, this is great news. The "Kenwood" device should be able to accept ADB drivers. How exactly did you "forced Googles Fastboot interface"?

Well, this all depends on what actual mode it is in and how you want to proceed. I'll attach some files that might want to use "push". The first file comes from Chainfire's Root download page. Inside the zip archive are two files, su and Superuser.apk inside the corresponding directories of where they should be. The other two will help you do more stuff in within Android.

C:\adt\sdk\platform-tools> [COLOR="RoyalBlue"][B]adb push su /mnt/sdcard[/B][/COLOR]
C:\adt\sdk\platform-tools> [COLOR="RoyalBlue"][B]adb push Superuser.apk /mnt/sdcard[/B][/COLOR]
C:\adt\sdk\platform-tools> [COLOR="RoyalBlue"][B]adb push "ES File Explorer_3.1.0.2.apk" /mnt/sdcard[/B][/COLOR]
C:\adt\sdk\platform-tools> [COLOR="RoyalBlue"][B]adb push "Terminal Emulator_1.0.54.apk" /mnt/sdcard[/B][/COLOR]
C:\adt\sdk\platform-tools> [COLOR="RoyalBlue"][B]adb shell[/B][/COLOR]
# [COLOR="RoyalBlue"][B]id[/B][/COLOR]
uid=2000(shell) gid=2000(shell)
# [COLOR="RoyalBlue"][B]mount[/B][/COLOR]
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,nosuid,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
none /acct cgroup rw,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock0 [COLOR="Red"][B]/system[/B][/COLOR] yaffs2 [COLOR="Red"][B]ro[/B][/COLOR] 0 0
/dev/block/mtdblock1 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock2 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/vold/179:0 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:0 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0
#

If the /system partition is mounted ro (read only) and not rw (read-write) then you'll need to use realign the line to be able to mount it as read write. For example, "/dev/block/mtdblock0 /system yaffs2 ro 0 0" would need to written as the following command, "mount -o rw,remount -type yaffs2 /dev/block/mtdblock0 /system"

# mv /mnt/sdcard/su /system/xbin
# chown 0.0 /system/xbin/su
# chmod 06755 /system/xbin/su
# mv /mnt/sdcard/Superuser.apk /system/app
# chown 0.0 /system/app/Superuser.apk
# chmod 644 /system/app/Superuser.apk
# mv "/mnt/sdcard/Terminal Emulator_1.0.54.apk" /system/app/TerminalEmulator.apk
# chown 0.0 /system/app/TerminalEmulator.apk
# chmod 644 /system/app/TerminalEmulator.apk
# mv "/mnt/sdcard/ES File Explorer_3.1.0.2.apk" /system/app/FileExplorer.apk
# chown 0.0 /system/app/FileExplorer.apk
# chmod 644 /system/app/FileExplorer.apk
# reboot

If this works then you're rooted and have terminal and es file explorer access to do things. If not then maybe you're in fastboot mode which you should be able to use "fastboot oem unlock" to unlock the bootloader and allow to replace the recovery bootloader which a custom one which will allow you to upload an img that isn't necessarily signed by Kenwood's platform key.