Jump to content

Samsung Galaxy S III (samsung-m0)

From Nura Wiki
Note Official disk images were reported not to work.
Samsung Galaxy S III
Samsung Galaxy S III
Samsung Galaxy S III
Manufacturer Samsung
Name Galaxy S III
Codename samsung-m0
Released 2012
Type handset
Hardware
Chipset Samsung Exynos 4412 Quad
CPU Quad-core 1.4 GHz Cortex-A9
GPU Mali 400 MP4
Display 720x1280 Super AMOLED
Storage 16/32/64 GB
Memory 1 GB (GT-i9300 & SHW-M440S)
Architecture armv7
Software
Original software
The software and version the device was shipped with.
Android 4.1.1
Extended version
The most recent supported version from the manufacturer.
Android
FOSS bootloader partial
Nura
Category community
Pre-built images
Whether pre-built images are available from the Nura Installation page.
yes
Mainline
Instead of a Linux kernel fork, it is possible to run (Close to) Mainline.
yes
Nura kernel
The kernel version that runs on the device's port.
7.1.1-0
Unixbench score
Unixbench Whetstone/Dhrystone score. See Unixbench.
0.0
Device package device-samsung-m0
Kernel package linux-postmarketos-exynos4
Features
Flashing
Whether it is possible to flash the device with pmbootstrap flasher.
Works
USB Networking
After connecting the device with USB to your PC, you can connect to it via telnet (initramfs) or SSH (booted system).
Partial
Internal storage
eMMC, SD cards, UFS...
Works
SD card
Also includes other external storage cards.
Works
Battery
Whether charging and battery level reporting work.
Works
Screen
Whether the display works; ideally with sleep mode and brightness control.
Works
Touchscreen
Works
Multimedia
3D Acceleration
Works
Audio
Audio playback, microphone, headset and buttons.
Partial
Camera
Partial
Camera Flash
Works
Connectivity
Wi-Fi
Works
Bluetooth
Partial
GPS
Broken
NFC
Near Field Communication
Broken
Modem
Calls
Broken
SMS
Broken
Mobile data
Broken
Miscellaneous
FDE
Full disk encryption and unlocking with unl0kr.
Works
USB OTG
USB On-The-Go or USB-C Role switching.
Works
HDMI/DP
Video and audio output with HDMI or DisplayPort.
Partial
Sensors
Accelerometer
Handles automatic screen rotation in many interfaces.
Works
Ambient Light
Measures the light level; used for automatic screen dimming in many interfaces.
Works
U-Boot
Primary Bootloader
Whether it is possible to replace stock bootloader with U-Boot.
Broken
Secondary Bootloader
Whether it is possible to chainload U-Boot from stock bootloader.
Untested
Mainline
Whether latest upstream versions of U-Boot are not broken and it is possible to use them.
Untested
Internal Storage
Whether it is possible to boot from internal storage (e.g. eMMC or UFS).
Untested
SD card
Whether it is possible to boot from SD card.
Untested
USB Host
Whether it is possible to boot from a USB storage or connect a keyboard.
Untested
USB Peripheral
Whether it is possible to use device as a peripheral in U-Boot, e.g. for fastboot mode.
Untested
Display
Untested
Buttons
Whether it is possible to navigate in boot menu or grub with volume and power buttons.
Untested

The Samsung Galaxy S III is an Android-based smartphone developed by Samsung and released in May 2012. Codenamed Midas, it is the most sold phone in the S series and has decent mainline Linux support. It is also well supported by the Replicant project, whose developers have expressed intent to collaborate with Nura.

So far, what works for Samsung Galaxy S III LTE (samsung-m3) also works for the samsung-m0 (Galaxy S III international GSM version without LTE, with model number I9300. It is also known as Galaxy S III 3G SHW-M440S in South Korea) and samsung-shv-e210s (a Korean variant). (None of these S III models should be confused with the North American S III models, which require OS builds.)

Model variants

  • GT-I9300 (Global, 3G) - samsung-m0
  • GT-I9305 (4G) - samsung-m3

Special boot modes

  • Download/Odin Mode: With the device powered off, hold Volume Down, Home and Power while connecting the device to a computer with a USB cable. A warning screen will appear: click Volume Up to enter Download Mode and run Heimdall commands.
    • Alternatively, with USB debugging enabled, run $ adb reboot download on a connected USB host.
  • Recovery Mode: With the device powered off, hold Volume Up, Home and Power while connecting the device to a computer with a USB cable.
    • Alternatively, with USB debugging enabled, run $ adb reboot recovery on a connected USB host.

Installation

Flashing to an SD card

Follow the Installation/Using a pre-built image article and flash the image to your SD card.

Flashing to the phone's internal storage

Note If this runs into errors, please use option 1.

Prepare img2simg

  • Download and build simg2img, making sure that it's executable with chmod.
  • Prepare the image:
    • If using a pre-built image, download a rootfs image (GNOME Mobile recommended, others ran into errors for me, more testing required) and extract it with any xz-supporting archive software. Make sure to NOT extract the .img itself, only the .xz.
    • If building the image with pmbootstrap, follow the instructions at the pmbootstrap article until the Flashing section, since you won't flash the image yet; then run pmbootstrap export and copy the rootfs image (usually named samsung-m0.img) from the output directory to a working directory.
  • Convert the rootfs image into an Android sparse image with img2simg:
    $ img2simg path-to-rootfs.img pmos-sparse.img
    
  • Boot into Download Mode.
  • Flash the new image with Heimdall into the userdata partition:
    $ heimdall flash --USERDATA pmos-sparse.img
    
  • Now use Heimdall to flash the image with -boot at the end to your boot partition. Make sure that you extract it before flashing it (the downloaded file is a compressed .tar.xz archive):
    $ heimdall flash --BOOT <Decompressed image filename> --verbose
    
    • Partitions must be written in full caps for Heimdall commands, otherwise the program won't find the partition and throw an error.

After finishing these steps, your device should automatically reboot into Nura!

Firmware

Alternative bootloaders

  • forkbomb got mainline U-Boot running on this device and wrote about it in this blog post.
  • xboot might be a completely free bootloader option. Looks to have zero proprietary blobs.

Bootloader installation

The bootloader on this device is not protected by Secure Boot. It can be replaced after disabling eMMC write protection for mmcblk0boot0. mmcblk0boot1 appears to be unused for this device.

Status

Audio

Audio mostly works. Notable omissions are input from the back microphone and output from the earpiece speaker and headphones. Only PulseAudio is working in v25.06, while PipeWire works on edge. Automatic device switching is unreliable when using it.

Display

Warning WARNING: Beware of screen burn-in on high brightness! Permanent discoloration can occur after consistent long use, especially on some low quality OLEDs.

Common aftermarket displays have not been verified to work, using the packaged driver. This cannot be guaranteed for all replacement parts that appear to work.

Buttons

The Home button is displayed as "0x10" in gnome-settings and cannot be mapped to a shortcut, while the touch keys work. See Tm2-touchkey for instructions.

Battery

Warning WARNING: Be careful with degraded batteries. They may cause issues. Some UIs will not power the device off automatically on low charge!

This device uses removable 2100 mAh Li-Ion batteries. Battery reporting works as of pmaports!2423, and charging works as of pmaports!2546, supporting 5V charging. It was reported that charging randomly stops, but should that happen you can just unplug and re-plug the cable. Charging is also very slow and the device will probably lose power if you use it while charging.

Known battery variants are:

  • EB-L1G6LLU (I9300, 2.1 Ah, NFC)
  • EB-L1G6ULU (I9300, 3 Ah, NFC)

Wi-Fi

Wi-Fi works as of pmaports!2556.

If networks show up but you can't connect to them, you can try using the nvram for samsung-m3/i9305. This is a hack and not necessarily endorsed, but at least one user has reported that their samsung-m0/i9300 needs this for Wi-Fi to work. We would like to handle this better, but currently we don't have any way of doing this.

To switch to the nvram meant for samsung-m3, run this command:

$ cd /lib/firmware/brcm
$ sudo mv brcmfmac4334-sdio.samsung,i9300.txt brcmfmac4334-sdio.samsung,i9300.txt.bak
$ sudo ln -sf brcmfmac4334-sdio.samsung,i9305.txt brcmfmac4334-sdio.samsung,i9300.txt

If it still refuses to connect, you might want to try replacing the contents of /lib/firmware/bcrm/brcmfmac4334-sdio.samsung,i9300.txt with the nvram from LineageOS. Apparently this is necessary on some British i9300 models.

Related issue: pmaports#1571

Modem

The modem is currently unsupported on Nura. However, it is supported on Replicant, and there was some work done to enable the modem on the i9300 variant of this device. (#1954, #2206 for LTE modem support, https://git.replicant.us/contrib/GNUtoo/kernel_replicant_linux/log/?h=replicant-11-i9300-modem) It can be found here. Note that even if you apply this, you would likely need user space patches as well for calls and mobile data to be usable.

Camera

User:Ka33 reports the back camera works in gst and megapixels, but libcamera can't detect it so the GNOME camera doesn't work, while the front camera is broken.

Video out

Samsung Galaxy S III providing video out to a TV through an original Samsung dock (model name: EDD-S20EWE).

Video output should work as long as you use an 11-pin MHL cable or dock (safest option would be an original Samsung dock/adapter from the time period, Samsung's EDD-S20EWE is known to work).

In September 2022, all HDMI-related nodes were disabled (pmaports!3395) as the kernel driver reports the wrong state, and this led to the Phosh stack not starting up. A WIP fix can be found on the Exynos 4 mainline GitLab.

GPS

The Galaxy S III uses the Broadcom BCM4751 GPS, but it's currently broken.

NFC

NFC is broken and requires a supported battery.

Warnings and considerations

  • It used to be that the battery percentage wasn't properly monitored and would get stuck at a set percentage at boot. While this was the case, the phone would not shut down when battery levels went too low, which could make the phone behave strangely on significantly worn batteries (in the ballpark of 50% wear). There are theories that this may have caused hardware failure for one user, but this is not proven. Battery level reporting has since been fixed, but it has not been extensively tested for reliability, so we recommend that you try to not let your phone's battery percentage fall too low. It should shut down on its own before anything adverse can happen, however.
    See pmaports#1115 for more information.
  • The eMMC firmware may be bugged and lead to data corruption. The Replicant Wiki has a good article about this.
  • Heimdall does not consider partition sizes when flashing. See Heimdall#494.

Contributors

Maintainer(s)

Users owning this device

See also

External links