Samsung Chromebook 2

model: XE503C32-K02SE

  • cpu: Samsung Exynos 5 Octa 5800 - Quad A15 @ 2.0 GHz / Quad A7 @ 1.7 GHz
  • RAM: 4 GB - DDR3L 1600 MHz - on board 4G (max 4 GB)
  • storage: 16 GB eMMC - on board
  • LCD: 13,3 inch, 1920x1080 FHD (low-reflective), UMS2
  • graphics: integrated
  • VRAM: shared
  • network: wireless - 802.11ac (2x2) Ready+BT
  • color: Luminous Titan (grey)
  • serial number: 0ZUK9FCF500470
  • operating system: Google ChromeOS
  • power: 12 V DC center positive, 3.33 A
  • Bluetooth: v4.0
  • web camera: 720p HD

keys: recovery mode - hold down Esc and Refresh (F3) - press power, developer mode - press Ctrl-D from recovery screen (note: this clears local data)

hints: to get a root shell, start crosh (Ctrl-Alt-T) and then enter 'shell'

alternative OS: FreeBSD,

back to machines page.

Links

Samsung XE503C32-K01US, User Guide,

ChromebookDB Samsung Chromebook 2 13.3 XE503C32-K01US,

Google links: developer information - Samsung ARM Chromeboook, Samsung Chromebook 2, using nv-U-Boot on the Samsung ARM Chromebook, Dev-Install: Installing Developer and Test packages onto a Chrome OS device, Crostini,

ArchLinux Samsung Chromebook 2, archbk, Arch Linux Chromebook 2 Setup,

more links: How to install Linux on a Chromebook (and why you should), crouton,

History

2023-08-06: enabled developer mode again - it takes a while. After that, I can do 'shell' from crosh, and 'sudo -i', but 'dev_install' fails with "curl: (22) The requested URL returned error: 403 Forbidden". Oh well.

2023-08-06: charged the machine and powered it on. It still works. ChromeOS is stuck at version 75.0.3370.144.

2017-02-25: update - after restart it runs ChromeOS 56.0.2924.87 (Official Build) (32-bit), Platform 9000.82.0 (Official Build) stable-channel peach_pi.

2017-02-05: update - after another restart it is running ChromeOS 55.0.2884.105, platform 8872.76.0 (Official Build) stable-channel peach_pi.

2017-02-03: after restart it is running ChromeOS 53.0.2785.154, platform 8530.96.0 (Official Build) stable-channel peach_pi.

2017-02-03: I got a "Restart to update" notification, and restarted.

2017-02-03: this afternoon I booted my CB2 after a long hiatus. The battery was empty, I had to log in, log out and in again, because my account was not synced. Now it runs ChromeOS version 48.0.2564.116, platform 7647.84.0.

2015-08-30: after restart it is running ChromeOS version 44.0.2403.156, platform 7077.134.0 (Official Build) stable-channel peach_pi.

2015-02-28: today I bought a Neoprene sleeve (Trunk 13 inch, color silver from Expert for the Chromebook. NOK 299.-

2015-02-17: after the restart it is running ChromeOS version 40.0.2214.114, Platform 6457.94.0 (Official Build) stable-channel peach_pi.

2015-02-17: unpacked the machine and opened it up. It came to life, battery is at 68%, claimed 7 hours 5 minutes left. I connect to my wireless network, log in (using Swedish keyboard), configure and select a Norwegian keyboard. I get a "Restart to update" notification.

2015-02-17: I got a pickup message (text message on my cellphone) and picked up the package at my local PIB (Rimi Trondheimsveien) on my way back home from work.

2015-02-16: new InfoCare service portal status at 08:23 local time: it is now listed as "returned". At 16:02 I received a shipping notice with tracking.

2015-02-13: I checked InfoCare's service portal today. the activity is reported as "finished" with "changed battery. tested OK" as solution. We shall see how long it takes to ship it back to me.

2015-02-09: shipping - the package has been delivered (received by "Trond"), it should now be in the hands of InfoCare (the service partner).

2015-02-06: shipping - delivered the package at my local PIB, and got a receipt with a tracking number. The package is now in the hands of the postal service.

2015-02-06: packing - packed in the original packaging, added receipt and fault description, wrapped package in brown paper and put the RMA label on it.

2015-02-06: checking: the account info is secured, there is no microSD card in the slot, the I reset the CB2 by going to Settings, show advanced settings, Powerwash, then restart, Powerwash, confirm. I also reset developer mode. Next, taking pictures of the machine, the power adapter, and the packaging.

2015-02-04: Dustin has registered my Chromebook for service with their service partner, InfoCare.A bit later I received the necessary info from InfoCare for returning the machine

2015-02-03: Another response from Dustin, saying that they don't have a good enough replacement for the Chromebook I have, but they now asks if I want to have it repaired under warranty. I answer yes, please do a warranty repair.

2015-01-26: Dustin responded back, asking if they should find a suitable replacement to offer. The next day, I answered yes.

2015-01-20: I responded to Dustin, stating that a replacement Chromebook needed to be 13 inch, have a good screen and fullHD (1920x1080) screen resolution. Let's see what they come up with.

2015-01-19: Dustin responded to my mail from 2015-01-05 (so, two weeks response time), and asked if I wanted my money back, or a replacement Chromebook since the model I have is out of production / stock now.

2015-01-15: Installing developer packages: crosh, sudo -i, dev_install,

crosh> shell
chronos@localhost / $ sudo -i
localhost ~ # dev_install

then I used emerge to install sshfs-fuse:

localhost ~ # emerge sshfs-fuse

after that finishes I can create a directory in ~/Downloads, for example ~/Downloads/mpoint and mount remote directories via sshfs. Unfortunately, the files doesn't show up in App:Files.

2015-01-15: version (from "about:version"): Google Chrome: 39.0.2171.96 (Official Build)

2015-01-07: mark the FreeBSD usb stick as bootable to U-boot /ChromeOS: it looks like this:

crosh> shell
chronos@localhost / $ sudo cgpt show /dev/sda
       start        size    part  contents
           0           1          PMBR
           1           1          Pri GPT header
           2          32          Pri GPT table
        2048       30720       1  Label: ""
                                  Type: ChromeOS kernel
                                  UUID: 5F61A7DD-945A-11E4-8B56-50465D8BA2EA
                                  Attr: priority=0 tries=0 successful=0
       34816       30720       2  Label: ""
                                  Type: ChromeOS kernel
                                  UUID: 6DFC2195-945A-11E4-8B56-50465D8BA2EA
                                  Attr: priority=0 tries=0 successful=0
       65536    15175007       3  Label: ""
                                  Type: 516E7CB6-6ECF-11D6-8FF8-00022D09712B
                                  UUID: 7ADA9C28-945A-11E4-8B56-50465D8BA2EA
    15240543          32          Sec GPT table
    15240575           1          Sec GPT header

and I run this "magic command":

chronos@localhost / $ sudo cgpt add -P 12 -T 5 -S 1 -i 1 /dev/sda

verify:

chronos@localhost / $ sudo cgpt show /dev/sda
       start        size    part  contents
           0           1          PMBR
           1           1          Pri GPT header
           2          32          Pri GPT table
        2048       30720       1  Label: ""
                                  Type: ChromeOS kernel
                                  UUID: 5F61A7DD-945A-11E4-8B56-50465D8BA2EA
                                  Attr: priority=12 tries=5 successful=1
       34816       30720       2  Label: ""
                                  Type: ChromeOS kernel
                                  UUID: 6DFC2195-945A-11E4-8B56-50465D8BA2EA
                                  Attr: priority=0 tries=0 successful=0
       65536    15175007       3  Label: ""
                                  Type: 516E7CB6-6ECF-11D6-8FF8-00022D09712B
                                  UUID: 7ADA9C28-945A-11E4-8B56-50465D8BA2EA
    15240543          32          Sec GPT table
    15240575           1          Sec GPT header

explanation: mark partition one bootable, like this:

chronos@localhost / $ sudo cgpt add -h

Usage: cgpt add [OPTIONS] DRIVE

Add, edit, or remove a partition entry.

Options:
  -i NUM       Specify partition (default is next available)
  -b NUM       Beginning sector
  -s NUM       Size in sectors
  -t GUID      Partition Type GUID
  -u GUID      Partition Unique ID
  -l LABEL     Label
  -S NUM       set Successful flag (0|1)
  -T NUM       set Tries flag (0-15)
  -P NUM       set Priority flag (0-15)
  -A NUM       set raw 64-bit attribute value

Use the -i option to modify an existing partition.
The -b, -s, and -t options must be given for new partitions.

The partition type may also be given as one of these aliases:

    firmware    ChromeOS firmware
    kernel      ChromeOS kernel
    rootfs      ChromeOS rootfs
    data        Linux data
    reserved    ChromeOS reserved
    efi         EFI System Partition
    unused      Unused (nonexistent) partition

that's it.

2015-01-07: enable usb boot - the machine is already in developer mode:

crosh> shell
chronos@localhost / $ sudo crossystem dev_boot_usb=1

and verified - done.

2015-01-05: battery - I sent a message to Dustinhome.no explaining about the battery not charging, and what I have tried. I also asked them how they want to handle it. We shall see what their response is, and how quickly they respond.

2015-01-05: recovery usb stick in ChromeOS. First I start a real shell from crosh:

crosh> shell
chronos@localhost / $

next I use the cgpt command to show sda:

chronos@localhost / $ sudo cgpt show /dev/sda
       start        size    part  contents
           0           1          PMBR (Boot GUID: 483C7EE2-1566-FD40-8CA9-42BA30CBD1F5)
           1           1          Pri GPT header
           2          32          Pri GPT table
     2928640       98304       1  Label: "STATE"
                                  Type: Linux data
                                  UUID: B19D0D74-061A-E747-91E1-2958B18B8C2D
       20480       32768       2  Label: "KERN-A"
                                  Type: ChromeOS kernel
                                  UUID: 4846C074-B266-5544-98D5-12FFEBF43E9B
                                  Attr: priority=15 tries=15 successful=1
      286720     2641920       3  Label: "ROOT-A"
                                  Type: ChromeOS rootfs
                                  UUID: FC5C63C9-CDC1-9447-BDEF-CC61712337CA
       53248       32768       4  Label: "KERN-B"
                                  Type: ChromeOS kernel
                                  UUID: 8439D418-6126-7246-B64C-1D586ACB3B60
                                  Attr: priority=0 tries=0 successful=0
      282624        4096       5  Label: "ROOT-B"
                                  Type: ChromeOS rootfs
                                  UUID: A302721C-9F80-D148-95C9-B3FA21FD52FE
       16448           1       6  Label: "KERN-C"
                                  Type: ChromeOS kernel
                                  UUID: D5DC8790-91A9-0B40-A1EC-3310D8FE0D1B
                                  Attr: priority=0 tries=0 successful=0
       16449           1       7  Label: "ROOT-C"
                                  Type: ChromeOS rootfs
                                  UUID: A0EDD65D-65C1-E445-9CEF-36F11F1B7434
       86016       32768       8  Label: "OEM"
                                  Type: Linux data
                                  UUID: 63ED9FFA-B72C-284D-9F40-340B841A9E9E
       16450           1       9  Label: "reserved"
                                  Type: ChromeOS reserved
                                  UUID: 0A209ACA-0A50-CA45-9272-CFF9FFF0B530
       16451           1      10  Label: "reserved"
                                  Type: ChromeOS reserved
                                  UUID: 9CF37D5C-22ED-5B48-A045-A5F0D8C115D5
          64       16384      11  Label: "RWFW"
                                  Type: ChromeOS firmware
                                  UUID: ACADC195-7050-2044-84A3-18CA31E4A145
      249856       32768      12  Label: "EFI-SYSTEM"
                                  Type: EFI System Partition
                                  UUID: 483C7EE2-1566-FD40-8CA9-42BA30CBD1F5
           0          32 INVALID  Sec GPT table
           1           1 INVALID  Sec GPT header

WARNING: one of the GPT header/entries is invalid

nothing more.

2015-01-05: recovery usb stick layout in FreeBSD. I plugged the recovery usb stick into my FreeBSD workstation, which runs:

tingo@kg-core1$ uname -a
FreeBSD kg-core1.kg4.no 9.3-STABLE FreeBSD 9.3-STABLE #0 r273918: Fri Oct 31 22:52:44 CET 2014     root@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64

here is what gpart thinks of the stick:

tingo@kg-core1$ gpart show -p da2
=>     34  3059581     da2  GPT  (7.3G) [CORRUPT]
       34       30          - free -  (15k)
       64    16384  da2p11  !cab6e88e-abf3-4102-a07a-d4bb9be3c1d3  (8.0M)
    16448        1   da2p6  !fe3a2a5d-4f32-41a7-b725-accc3285a309  (512B)
    16449        1   da2p7  !3cb8e202-3b7e-47dd-8a3c-7ff2a13cfcec  (512B)
    16450        1   da2p9  !2e0a753d-9e48-43b0-8337-b15192cb1b5e  (512B)
    16451        1  da2p10  !2e0a753d-9e48-43b0-8337-b15192cb1b5e  (512B)
    16452     4028          - free -  (2M)
    20480    32768   da2p2  !fe3a2a5d-4f32-41a7-b725-accc3285a309  (16M)
    53248    32768   da2p4  !fe3a2a5d-4f32-41a7-b725-accc3285a309  (16M)
    86016    32768   da2p8  linux-data  (16M)
   118784   131072          - free -  (64M)
   249856    32768  da2p12  efi  (16M)
   282624     4096   da2p5  !3cb8e202-3b7e-47dd-8a3c-7ff2a13cfcec  (2.0M)
   286720  2641920   da2p3  !3cb8e202-3b7e-47dd-8a3c-7ff2a13cfcec  (1.3G)
  2928640    98304   da2p1  linux-data  (48M)
  3026944    32671          - free -  (16M)

for good measure, disktype too:

root@kg-core1# disktype /dev/da2

--- /dev/da2
Character device, size 7.267 GiB (7803174912 bytes)
DOS/MBR partition map
Partition 1: 2.412 GiB (2589949440 bytes, 5058495 sectors from 1)
  Type 0xEE (EFI GPT protective)
GPT partition map, 128 entries
  Disk size 1.459 GiB (1566539776 bytes, 3059648 sectors)
  Disk GUID 65885684-9D13-443D-B173-987E622B5ABE
Partition 1: 48 MiB (50331648 bytes, 98304 sectors from 2928640)
  Type Basic Data (GUID A2A0D0EB-E5B9-3344-87C0-68B6B72699C7)
  Partition Name "STATE"
  Partition GUID 740D9DB1-1A06-47E7-91E1-2958B18B8C2D
  Ext2 file system
    UUID E8764CBA-58FC-4ED0-89EE-61D0CE8C4125 (DCE, v4)
    Volume size 46.93 MiB (49205248 bytes, 12013 blocks of 4 KiB)
Partition 2: 16 MiB (16777216 bytes, 32768 sectors from 20480)
  Type Unknown (GUID 5D2A3AFE-324F-A741-B725-ACCC3285A309)
  Partition Name "KERN-A"
  Partition GUID 74C04648-66B2-4455-98D5-12FFEBF43E9B
Partition 3: 1.260 GiB (1352663040 bytes, 2641920 sectors from 286720)
  Type Unknown (GUID 02E2B83C-7E3B-DD47-8A3C-7FF2A13CFCEC)
  Partition Name "ROOT-A"
  Partition GUID C9635CFC-C1CD-4794-BDEF-CC61712337CA
  Ext2 file system
    Volume name "ROOT-A"
    UUID nil
    Volume size 1.195 GiB (1283457024 bytes, 313344 blocks of 4 KiB)
Partition 4: 16 MiB (16777216 bytes, 32768 sectors from 53248)
  Type Unknown (GUID 5D2A3AFE-324F-A741-B725-ACCC3285A309)
  Partition Name "KERN-B"
  Partition GUID 18D43984-2661-4672-B64C-1D586ACB3B60
Partition 5: 2 MiB (2097152 bytes, 4096 sectors from 282624)
  Type Unknown (GUID 02E2B83C-7E3B-DD47-8A3C-7FF2A13CFCEC)
  Partition Name "ROOT-B"
  Partition GUID 1C7202A3-809F-48D1-95C9-B3FA21FD52FE
  Blank disk/medium
Partition 6: 512 bytes (1 sectors from 16448)
  Type Unknown (GUID 5D2A3AFE-324F-A741-B725-ACCC3285A309)
  Partition Name "KERN-C"
  Partition GUID 9087DCD5-A991-400B-A1EC-3310D8FE0D1B
  Blank disk/medium
Partition 7: 512 bytes (1 sectors from 16449)
  Type Unknown (GUID 02E2B83C-7E3B-DD47-8A3C-7FF2A13CFCEC)
  Partition Name "ROOT-C"
  Partition GUID 5DD6EDA0-C165-45E4-9CEF-36F11F1B7434
  Blank disk/medium
Partition 8: 16 MiB (16777216 bytes, 32768 sectors from 86016)
  Type Basic Data (GUID A2A0D0EB-E5B9-3344-87C0-68B6B72699C7)
  Partition Name "OEM"
  Partition GUID FA9FED63-2CB7-4D28-9F40-340B841A9E9E
  Ext3 file system
    Volume name "OEM"
    UUID F7CB0983-5C02-4039-9CA9-A0534182066B (DCE, v4)
    Volume size 16 MiB (16777216 bytes, 4096 blocks of 4 KiB)
Partition 9: 512 bytes (1 sectors from 16450)
  Type Unknown (GUID 3D750A2E-489E-B043-8337-B15192CB1B5E)
  Partition Name "reserved"
  Partition GUID CA9A200A-500A-45CA-9272-CFF9FFF0B530
  Blank disk/medium
Partition 10: 512 bytes (1 sectors from 16451)
  Type Unknown (GUID 3D750A2E-489E-B043-8337-B15192CB1B5E)
  Partition Name "reserved"
  Partition GUID 5C7DF39C-ED22-485B-A045-A5F0D8C115D5
  Blank disk/medium
Partition 11: 8 MiB (8388608 bytes, 16384 sectors from 64)
  Type Unknown (GUID 8EE8B6CA-F3AB-0241-A07A-D4BB9BE3C1D3)
  Partition Name "RWFW"
  Partition GUID 95C1ADAC-5070-4420-84A3-18CA31E4A145
  Blank disk/medium
Partition 12: 16 MiB (16777216 bytes, 32768 sectors from 249856)
  Type EFI System (FAT) (GUID 28732AC1-1FF8-D211-BA4B-00A0C93EC93B)
  Partition Name "EFI-SYSTEM"
  Partition GUID E27E3C48-6615-40FD-8CA9-42BA30CBD1F5
  FAT16 file system (hints score 5 of 5)
    Volume size 15.95 MiB (16726016 bytes, 8167 clusters of 2 KiB)
    Volume name "EFI-SYSTEM"
Partition 13: unused

that was a lot.

2015-01-04: recovery media - in Chrome on my Chromebook, I went to chrome://imageburner and got the "Create OS Recovery Media" screen. I inserted a 8 GB usb stick (Kingston DataTraveler SE9), it warned me that all files on the stick would be erased, I pressed "OK". First it downloaded a recovery image (488 MB), extracted it, then started to copy it (1.5 GB) and then said "Your recovery media is ready. You may remove it from your system."

2015-01-04: battery - it seems the battery is not charging. The battery LED is blue (its should be red if charging) and the machine turns off if I unplug the power adapter. I tried a powerwash. It didn't help. When I turn off the Chromebook, the power LED blinks red. I measured the voltage from the power adapter (with my multimeter) - yep, it is 12 volts. I let the machine sit for many hours with the power adapter connected and the machine off - didn't help, the power led is still blinking red.

2015-01-03: I created a Google account. From Settings, Language and input settings, I could select "Norwegian" and Norwegian keyboard.

2015-01-03: first power on. I followed the quick start guide. Plugged in the power adapter, and opened the machine. It powered on, displaying a nice wallpaper and asking me to select language (English), keyboard (Norwegian was not available so I selected Swedish keyboard), connected to my (wireless) network and selected "Continue". Then I had to accept the Google Chrome OS Terms - this screen also had "System security setting" (TPM password) and "Accessibility". Next Chrome OS updated, before asking me to sign in. For now I selected Browse as Guest". After a while the panel (or whatever it is called - status tray) showed "restart to update" so I did.

2015-01-03: the Chromebook 2 has the following connectors on the left side (from back to front): DC input from power adapter, usb 3.0 (chargeable port), HDMI connector, micro-SD card slot. O the right side (from front to back): headset jack, usb 2.0 (chargeable port?), security slot.

2015-01-03: I picked up the package from Dustinhome today, at my local PIB (Rimi Trondheimsveien). The packaging contains:

1 x Chromebook
1 x power adapter (output: 12 V DC center positive, 3.33A) + power cable (the end that goes into the power adapter has the "Mickey Mouse" style plug)
1 x plastic bag with documentation: 1 x warranty information, 1 x 503C12 / 503C32 Quick Start Guide, 1 x Samsung Cromebook "Programvaruguide" (=software guide) which are offers for 1 year free AirDroid Premium + Wunderlist Pro + free lessions in Little Bridge.

2014-12-29: Sale on Dustinhome.no, and I found a Samsung Chromebook 2 (5010782006) for NOK 2490.- and this was the model with a full-HD display, so I bought it.