[WIP]Android on Samsung Chromebook series 3

Android On Samsung Arm Chromebook?


  • Total voters
    183
Search This thread

vma

Senior Member
Mar 19, 2005
218
1
geocities.com
OMG! I have no idea how I overlooked that! I am really sorry...

...going to sit in the corner for a while

Regards,
vma
 

mqiasi

New member
Jun 8, 2010
4
0
i know, super old thread

I just got hold of some old xe303c12 comps.. thought to play around and install android on them. is it possible for you to upload your links ? :D
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    UPDATE: See second post for initial downloads of AOSP, CM , Arndale and Linaro/Arndale builds. These are very much a work in progress and may not even work. I am putting them forth for testing for the dev community to try out on their chromebooks.

    These builds will be based on the latest JB builds. There is still alot of work to be done here. The AOSP builds initially have been put up. The other builds will go up as they are completed. I am working on the documentation for putting this together as a repeatable process is doable. In time there will be an installer and other goodies, but for now this will just be a very vanilla and manual process.

    My goal is to get a working port of JB on the Samsung Chromebook. There has been no significant work on this front AFAIK. So I am taking it on myself to learn and try this out. Any community input would be helpful in making this work. I am fairly n00b at this but am looking to make this work.

    I found some promising information. I might be able to build this using the binaries from arndaleboard which appears to mostly use the same hardware.

    FYI for anyone experimenting to make this work please note that the following MUST be done for any chance of these root files to boot from SD.
    SD/MMC boot
    vold.fstab
    * Change the sdcard0 and sdcard1 lines so that the first line is sdcard1 and the second is sdcard0.
    fstab.arndale
    * Change all references to mmcblk0px to mmcblk1px.
    init.arndale.rc
    * Change the 2 references to mmcblk0px to mmcblk1px.
    mountd.conf
    * Change the reference to mmcblk0 to mmcblk1

    http://www.arndaleboard.org/wiki/index.php/Main_Page

    http://forum.insignal.co.kr/viewtopic.php?f=6&t=62
    http://forum.insignal.co.kr/viewtopic.php?f=6&t=63

    Now that the rootfs part is addressed I am tackling the booting issues. Current uboot methods focus mainly on linux distro booting. Android appears to require its own ramdisk (which is in the links below) there will be some extra downloads such as a working uboot.

    Once there are working versions of all the needed components working. An installer or installer script will be put together along with documentation. I may release this to a separate thread which I will post here.

    Additional info on flashing the actual arndale. http://www.arndaleboard.org/wiki/ind...Flash_a_Device
    Arndale is the base hardware also used on a Samsung series 3 Chromebook. Most if not all the components will work.

    Additionally MANTA aka nexus 10 hardware is similarly identical and can be used with some success. I am working on compiling base builds based on CM10, AOSP, Linaro and Arndale's git.

    Some more info on the bootloader

    http://www.denx.de/wiki/U-Boot
    http://www.chromium.org/chromium-os/...arm-chromebook

    Im using this post to keep notes on what I find and build. I might edit some more to update as I find stuff. I will create a separate post if I have any success. I got two of these. I can live with bricking one if it happens. And I imagine there is a way to restore the system if needed. I figure I will figure that part out first. To avoid any mishaps and have a brick.

    CREDITS: Musical_chairs for his invaluable input and resources he has linked in this post. I will update credits for other contributors once I get through the whole thread and credit all those obviously who build the original code these builds will be based on.
    3
    DISCLAIMER: For advanced users ONLY!! Not responsible if your chromebook gets bricked, struck by lightning or eaten by a pack of wild boars or attacked by crab people! Anything you do strongly recommended it be done on an SDcard to ensure easy rollbacks and no destruction of firmware.

    Here are the first downloads of the rootfs and ramdisk (both of which are needed for a working android install on chromebook) These are based on AOSP. More files will be coming as I am compiling. Basic instructions on how to set up uboot will be posted above as well as how to properly flash an SDcard. This assumes you know how to get your chromebook into dev-mode. Please note this is strictly for anyone with android system experience. The system may not even boot properly at this point. This is pre-pre-alpha at this point. There is alot of work to do before it even comes close to being usable. But if you get it working, please make a DD image (instructions above) and post it for all to use and work from. FOSS means sharing and sharing means caring. This will speed up the work needed to make this work for all of us.

    aosp-ramdisk.img
    https://mega.co.nz/#!sZgVmIQY!M9ANXXEJYAWR0TlRxV_mC3CdEXkTKC_Tgr1PdOD0Hxo
    aosp-rootfs.tar.bz2
    https://mega.co.nz/#!ZNgAFYqR!HkXcLxead3Zgm7lNcUzjb0YlfzEbbogTL5CnZDuUtIA

    arndale-kernel
    https://mega.co.nz/#!gIQXVLRC!U_L0WSutAXdGzdqhFrlzD1ij750Q8lTlKwHVoC28C14
    arndale-ramdisk.img.ub
    https://mega.co.nz/#!RB4XBAjS!JtNgciYJrLL_TDmjXjnZkTouPKwAhva26b7U9zvBYA0
    arndale-rootfs.tar.bz2
    https://mega.co.nz/#!xJwBVALa!QnwJRjQzhC218tcjMtKnimKZE2kn73sGs8XgeC75fDU
    3
    Any progress?

    Sent from my Galaxy Nexus using xda app-developers app
    2
    Well I finally made it to the nv-u-boot command prompt (and managed to freak out ChromeOS enough to cause it to reset itself and wipe all local data, but that's a minor detail). I wasn't making it to the nv-u-boot prompt before because I misunderstood the priority settings of the ChromeOS kernel partitions (higher number means "boot from me first" - oops). I finally 'got it' while reading the instructions and the script downloaded from this page: https://www.berrange.com/posts/2013...fedora-18-arm-on-a-samsung-google-chromebook/

    Anyway, you can boot to the nv-u-boot command prompt either from an SD card or by overwriting one of the kernel partitions on the emmc. I chose to use the SD card for now, for safety reasons. nv-u-boot (google's version at least) needs the /boot partition to be ext2, so I need to do some repartitioning to my sdcard before I can boot my Ubuntu again. But for now, how to get the nv-u-boot command prompt:

    (This assumes your Chromebook is in developer mode and has dev_boot_usb enabled.)
    1. Partition your SD card using parted vaguely as described on this page: (On a Linux machine with an SD card slot)
    http://blogs.arm.com/software-enablement/848-running-linux-on-the-series-3-chromebook/
    We need at least one ChromeOS kernel partition, and as far as I can tell, GParted does not know about those, so we need to create the kernel partition from the command line. We will also need an ext2 partition for /boot in order to use nv-u-boot, this is not part of the partitioning guide but you can do it with GParted later.
    2. Download nv-u-boot for 'snow' from here: (On the Chromebook now)
    http://commondatastorage.googleapis.com/chromeos-localmirror/distfiles/nv_uboot-snow.kpart.bz2
    3. Hit Ctrl+Alt+T for a terminal and enter:
    Code:
    shell
    cd ~/Downloads
    4. Extract the uboot image:
    Code:
    bzip2 -d nv_uboot-snow.kpart.bz2
    5. Write nv-u-boot to the SD card:
    Code:
    sudo dd if=nv_uboot-snow.kpart of=/dev/mmcblk1p1
    Replace 'p1' with the approproate partition number if you are not writing to the first partitition of the sdcard.
    6. Set partition flags:
    Code:
    sudo cgpt add -i 1 -S 1 -T 5 -P 15 /dev/mmcblk1
    (where -i is the partition number, -T is the number of tries, and -P is the boot priority, higher number boots first.)

    Now, when you reboot and hit Ctrl+U, the system will attempt to boot with nv-U-boot. Immediatly hold down the spacebar to interrupt uboot and be given toe command prompt (warning - if you don't hit any keys, uboot gets confused, ChromeOS gets scared, and next thing you know, it has reset itself and you'll need to re-enable dev mode. Believe me, I know...)

    From the uboot command prompt, you can make changes, save them, and boot in lots of interesting and creative ways. Now for figuring out uboot commands...
    2
    I'm attempting to get a build going today based on the arndale stable build once I convert the cyanogenmod to a rootfs I will use that. I got uboot going I just need to ensure it works.

    I am getting close if I have a working image I will upload it for SDcard use. Its a starting point for ROM modders to work with on the chromebook and might convince google to use android as a desktop OS alternative

    http://forum.insignal.co.kr/viewtopic.php?f=6&t=62