Samsung Galaxy S III (samsung-m0)
| Official disk images were reported not to work. |
|
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 |
|
| Kernel package |
|
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
|
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
|
| This device is based on the Exynos 4412. See the SoC page for common tips, guides and troubleshooting steps |
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 , and while connecting the device to a computer with a USB cable. A warning screen will appear: click to enter Download Mode and run Heimdall commands.
- Alternatively, with USB debugging enabled, run
$ adb reboot downloadon a connected USB host.
- Alternatively, with USB debugging enabled, run
- Recovery Mode: With the device powered off, hold , and while connecting the device to a computer with a USB cable.
- Alternatively, with USB debugging enabled, run
$ adb reboot recoveryon a connected USB host.
- Alternatively, with USB debugging enabled, run
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
| 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 exportand 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: 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: 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

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
- Thiagaopluplus
- tyxieblub
- Newbyte
- Grimler
Maintainer(s)
Users owning this device
- AmateurPenguin (Notes: Marble white and pebble blue,1 alive,uboot)
- Arthurlutz (Notes: /e/ 0.11 (android 7 pie) (FIXME: m0 or m3))
- Bastindo (Notes: 2x black, 2x blue)
- ByteXD23! (Notes: Has battery, Not responsive, perhaps dead EMMC?)
- ByteXD23! (Notes: No battery, Not responsive, perhaps dead EMMC?)
- Cick0
- D1don
- DALEK 77 (Notes: 16GB, Pebble Blue)
- Demodé
- Dolphinana (Notes: pmOS with non-free wifi firmware)
- Eepymeowers (Notes: SGH-I535 ver, fully working)
- Eldyj (Notes: I9300, Chinese battery, running PMOS edge with gnome-mobile, no issues so far)
- Eloy
- EnderNightLord (Notes: 1 GB RAM)
- ExtensionDriver (Notes: m0, white, worn battery cover)
- GeraltvonNVIDIA (Notes: Running phosh (community))
- Grimler
- Illen (Notes: Battery is broken, works on charger. Runs mainline U-Boot/Linux.)
- Interstellar-Column (Notes: LineageOS)
- Jack Kekzoz
- Ka33 (Notes: not with me yet, pmos)
- LanaX64
- Lunaoverflow (Notes: Bricked)
- Lxpanel (Notes: will not turn on)
- Madhaxbro (Notes: GT-I9300, runs pmOS edge + TWRP. Ready for testing. Large battery, around 3Ah. Classic design. Works well as a portable audio player. Plasma can fill up memory and slow the UI to a crawl if you push it.)
- Malo1301 (Notes: Broken glass and damaged power button. Used to run Nura, but I repurposed its SD card.)
- Missy
- Neilvandyke
- Nergzd723 (Notes: Power button broken, otherwise in perfect condition :D)
- Newbyte
- Nieldv
- Prowindows62 (Notes: Dualboot with postmarketOS and stock Android 4.3)
- R0rt1z2 (Notes: Bricked with u-boot, needs UART)
- Rebel1725
- Roboe (Notes: (borrowed) GT-I9300 16GB; unreliable USB; running pmOS stable)
- Roboe (Notes: (borrowed) GT-I9300_TIZEN (Tizen RD-PQ); HW rev. 0xC (M0_REAL_REV1.1_2nd_120413); PIT Version 08; running Tizen 2.2.0 with U-Boot 2011.03 (Jul 16 2013))
- Russanandres (Notes: Cyanogenmod 13)
- Sputnik1973 (Notes: Broken screen and bad battery.)
- Sputnik1973 (Notes: Mint condition, no issues (with the original dock that came with it.))
- Thenightterrorx (Notes: haven't tried flashing yet)
- Thiagaoplusplus
- Tigersusyt (Notes: GT-I9300 - No battery, unsure what is installed)
- TryzenAlpensky (Notes: Pebble Blue - 16GB)
- UltrasonicMadness (Notes: GT-I9300)
- Ungeskriptet (Notes: 2x White and 1x Pebble Blue, all GT-i9300. One with U-Boot :D)
- User0 (Notes: running postmarketOS)
- Vincele (Notes: PMOS, problem see (1))
- Vipaol (Notes: pmos)
- Vipaol (Notes: stock)
- Vladuwka12 (Notes: Running stock)
- WonderfulShrineMaidenOfParadise
- X7s (Notes: no power button but works perfectly)
See also
External links
- Samsung Galaxy S III on Wikipedia
- Official TWRP build
- TWRP with eMMC boot partitions patch for flashing bootloaders
- exynos4412-i9305.dts – Upstream DTS file
Samsung Galaxy S III (I9300) on Replicant Wiki
Bootloader research on Replicant Wiki
- "eMMC hacking, or: how I fixed long-dead Galaxy S3 phones", Oran Avraham at 34C3. 27 December 2017.
- Guide to revive a bricked i9300 eMMC
- pmaports!2556 Rename from i9300 to m0