From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20110917163620.0ba31132@kolari.ethans.dre.am> Date: Sat, 17 Sep 2011 14:53:10 -0700 Message-ID: From: ron minnich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [9fans] Announcing Inferno for Android phones Topicbox-Message-UUID: 271502c8-ead7-11e9-9d60-3106f5b1d025 A few corrections. > $ adb shell mount -o remount,rw / > $ adb push boot-inferno.img adb push work/boot-inferno.img /boot-inferno.img > $ adb shell > Now you'll be in an Android shell. > android$ cat /proc/mtd > This will hopefully give you a list of "mtd" devices and their names. > We only care about the one called "boot." > android$ cat /dev/zero > /dev/mtd/<"boot" device from above> > The zeroing step may not be necessary, but I've never tried flashing > the boot manually without it. It is hard to believe it is needed. The reason is the erase state of flash is all 1s, not all zeros. Cat'ing zeros onto the flash is probably not what you want: it corresponds to an all-bits-burned state, not an all-bits-cleared state. In this case when you the next step: > android$ flash_image boot /boot-inferno.img The mtd driver will likely erase the flash (to all 1s!) and then burn it :-) > Then reboot and it should work. android continues to work. But no inferno at present. I get the nice white screen, but if I touch it, well, it's blank after a bit. The parallel_push script did not work that well for me, I had to push dis/ by hand. I think it would be better to copy the tar file over and untar it -- would avoid mac silliness with case in the names, as well. Anyway, I'm booted. I've taken notes and will post them later. I think I'm still missing lots of stuff so I may just push the tar file and untar it. ron