if you didn't get around this problem yet, try 1. 'ps' to list the installer process and 'kill' it 2. run '/system/bin/installer -p /dev/block/ YOUR_SECOND_PARTITION_ON_USB_STICK' (e.g., I used /dev/block/sdc2 and / dev/block/sdd2 for my EeePC 701 and 900 respectively)
On Dec 31 2008, 3:39 pm, Andriod Developer <[email protected]> wrote: > Hi freedom, > I am running this image under Sun VirtualBox and I ran into the same > issue (i.e. /dev/block/sdb2) > How do i resolve this? how do i provide the installer with arugments? > > thanks > > On Dec 21, 5:15 pm, freedom <[email protected]> wrote: > > > Thanks, the problem I ran into was that /dev/block/sdbwas > > the card reader and the USB stick was sdc. After changing > > the argument for installer to /dev/block/sdc2, I got it > > installed. > > > On Dec 20, 4:05 am, "Dima Zavin" <[email protected]> wrote: > > > > > after boot from my USB stick, I saw > > > > init: Unable to open persisent property directory /data/property > > > > errno: 2 > > > > and > > > > This is harmless in this case. > > > > > I/installer( 1865): Waiting for device: /dev/block/sdb2 > > > > than some USB information, and shell prompt > > > > > my internal SSD was not touched at all, that is, it didn't start to > > > > install > > > > As I mentioned, the installer is definitely not robust. It assumes that > > > sda > > > will be the internal SSD, andsdbwill be the usbstick (iirc). You might > > > need to hack in the bios to make sure that the devices are assigned > > > properly > > > (in the order that we want them). > > > > The real solution is to pull in volume-id stuff from udev (drop it > > > somewhere > > > into external/, and add it to the build), have init call out to it when a > > > new block device shows up, and have it drop the right device node into > > > /dev/block-by-volid/... > > > > Then the installer can refer to the right volume by volumeid, and can > > > avoid > > > this device name hardcoding mess. When we build the images, we include the > > > appropriate volume id already, I just didn't get a chance to get the init > > > side of things done. Patches are welcome. > > > > Thanks. > > > > --Dima > > > > > On Dec 19, 4:23 am, "Dima Zavin" <[email protected]> wrote: > > > > > Try this (only tested on EeePC 701): > > > > > > repo init -u git://android.git.kernel.org/platform/manifest.git -b > > > > cupcake > > > > > repo sync > > > > > TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make -j8 > > > > > installer_img > > > > > dd if=out/target/product/eee_701/installer.img of=/dev/<usbstick of > > > > > your > > > > > choice> ; sync > > > > > > Boot from the usb stick. The installer is a bit crude, and needs > > > > polishing > > > > > and generalizing but it works. Note: It WILL WIPE your EeePC drive. :) > > > > > > --Dima > > > > > > On Thu, Dec 18, 2008 at 12:10 PM, Piethein Strengholt < > > > > > > [email protected]> wrote: > > > > > > > Check this: > > > > > > >http://source.android.com/roadmap/cupcake > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
