Samsung Galaxy S III (samsung-m0)
- 1 Contributors
- 2 Maintainer(s)
- 3 Basic info
- 4 Users owning this device
- 5 How to enter flash mode
- 6 Installation
- 7 WiFi
- 8 Mainline Kernel
- 9 Battery
- 10 Warnings and considerations
- 11 See also
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, 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.)
Code name is MIDAS. Search for midas-mainline to find more info.
Users owning this device
- Arthurlutz (Notes: /e/ 0.11 (android 7 pie) (FIXME: m0 or m3))
- DALEK 77
- EnderNightLord (Notes: 1 GB RAM)
- ExtensionDriver (Notes: m0, white, worn battery cover)
- Illen (Notes: Battery is broken, works on charger. Runs mainline U-Boot/Linux.)
- Mossroy (Notes: sometimes used : It can not be flashed easily. Seems to have a hardware issue with current consumption, even with a new battery (FIXME: m0 or m3?))
- Nergzd723 (Notes: Power button broken, otherwise in perfect condition :D)
- Ungeskriptet (Notes: 2x White and 1x Pebble Blue, all GT-i9300)
How to enter flash mode
- Hold power + Home + volume down
- When prompted, release all buttons and press volume up
Set phone to ODIN mode
1. Turn off phone 2. Connect USB cable 3. Hold VOLUME_DOWN + HOME + POWER until you get Warning!! screen 4. Push VOLUME_UP to continue to ODIN mode screen
# Ready the build pmbootstrap init # (weston or xfce4 should do) # Install rootfs to Micro SD Card pmbootstrap install --sdcard=/dev/something # (typically /dev/sd<x> or /dev/mmcblk<#>, will depend on where your Micro SD Card is mounted) # You can now insert the sdcard into the device # Put the m0 / m3 into odin mode with the steps above and flash the kernel (to boot from the Micro SD Card) pmbootstrap flasher flash_kernel # (in odin mode) # and it should reboot automatically and start pmos from the sdcard
To get the WiFi working, you'll need to modify the wpa_supplicant configuration. If this is not done, wpa_supplicant starts with -ip2p0 which is not supported on our device.
$ echo 'wpa_supplicant_args="-Dwext"' | sudo tee /etc/conf.d/wpa_supplicant
You can use either NetworkManager or networking and wpa_supplicant. NetworkManager is recommend in most cases as it handles reconnection.
Ensure the networkmanger service is running
$ sudo rc-status | grep 'networkmanager'
if it not visible, try to start the service:
$ sudo rc-service networkmanager start
Search for available WiFi networks and connect to network
$ sudo nmcli device wifi list ifname wlan0 $ sudo nmcli --ask dev wifi connect SSID
Reboot and you should be connected.
Networking and wpa_supplicant
You will need to manually configure the interfaces by creating
$ sudo vi /etc/network/interfaces
auto lo iface lo inet loopback auto wlan0 iface wlan0 inet dhcp
Save changes and add networking to start with system
$ sudo rc-update add networking
Add WiFi network information
$ wpa_passphrase YOUR_SSID YOUR_PASSPHRASE | sudo tee /etc/wpa_supplicant/wpa_supplicant.conf
$ sudo rc-service wpa_supplicant restart $ sudo rc-service networking start
WiFi on mainline
As of pmaports!2556, WiFi should "just work" on mainline. However, note that reception is very poor and you have to be very close to the router to be able to connect and use it.
The pmports repo for this device's linux-postmarketos-exynos4 mainline kernel is here.
@pmOS_devices announcement from Nov 11, 2020: https://twitter.com/pmOS_devices/status/1326525105162293249
Upstream dts: exynos4412-i9305.dts
Upstream kernel support matrix: Midas on Mainline.
Note that a patch is required to make it work with the stock samsung bootloader and this is included in the pmports mainline repo above.
forkbomb from LineageOS got mainline u-boot running on this device and wrote about it in this blog post: https://blog.forkwhiletrue.me/posts/an-almost-fully-libre-galaxy-s3/
Replicant has this device booting with mainline Linux and almost mainline U-Boot with only the need for a few patches on top and would like to collaborate with us 
The Qualcomm Gobi MDM9615 Modem seems to have mainline kernel support as well: https://redmine.replicant.us/projects/replicant/wiki/GalaxyS3I9305#Hardware-table
The Replicant project is working on getting the i9300 modem working with a mainline kernel in a way that pmOS can also utilize: https://redmine.replicant.us/issues/1954 https://git.replicant.us/contrib/GNUtoo/kernel_replicant_linux/log/?h=replicant-11-i9300-modem
LTE modem support with the mainline kernel on Replicant is being done here: https://redmine.replicant.us/issues/2206 The Note II discussed here has the same or very similar modem as the i9305.
Replicant currently supports this device in 6.0 and is doing a lot of research in order to get it running with a mainline kernel with a mainline bootloader for Replicant 11. More bootloader research is here.
Replicant's mainline kernel git repo: https://git.replicant.us/replicant-next/kernel_replicant_linux/
xboot might be a completely free bootloader option. Looks to have zero proprietary blobs.
With mainline, battery reporting works as of pmaports!2423, and charging works as of pmaports!2546. Support for battery reporting and charging with the downstream kernel is unknown. Charging allegedly randomly stops, but should that happen you can just unplug and re-plug the cable.
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. 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.
eMMC firmware bugs
Replicant has a good article about this: https://redmine.replicant.us/projects/replicant/wiki/EMMCFirmwareBugs
Heimdall does not consider partition sizes when flashing