Samsung Galaxy S III (samsung-m0): Difference between revisions
Add myself as maintainer |
Update and clean up article with up-to-date information and remove redundant instructions |
||
Line 9: | Line 9: | ||
| chipset = Exynos 4412 Quad | | chipset = Exynos 4412 Quad | ||
| cpu = Quad-core 1.4 GHz Cortex-A9 | | cpu = Quad-core 1.4 GHz Cortex-A9 | ||
| gpu = Mali | | gpu = Mali 400 MP4 | ||
| storage = 16 GB/32 GB | | storage = 16 GB/32 GB | ||
| display = 720x1280 Super AMOLED | | display = 720x1280 Super AMOLED | ||
Line 24: | Line 24: | ||
| status_mainline = Y | | status_mainline = Y | ||
| status_battery = P | | status_battery = P | ||
| status_3d = | | status_3d = Y | ||
| status_accel = | | status_accel = | ||
| status_audio = N | | status_audio = N | ||
Line 36: | Line 36: | ||
| booting = yes | | booting = yes | ||
}} | }} | ||
__TOC__ | __TOC__ | ||
Line 84: | Line 82: | ||
# and it should reboot automatically and start pmos from the sdcard | # and it should reboot automatically and start pmos from the sdcard | ||
</source> | </source> | ||
Line 193: | Line 148: | ||
== Mainline Kernel == | == Mainline Kernel == | ||
Thanks in large part to the [http://blog.forkwhiletrue.me/pages/midas-mainline/ Midas on Mainline] work that was done a few years ago, we now have initial mainline support for this device. The pmOS patch that added initial support is [https://gitlab.com/postmarketOS/pmaports/-/commit/0bab9b5f8a99b6e80cf5def6590d82e6d5dddc3d here]. | Thanks in large part to the [http://blog.forkwhiletrue.me/pages/midas-mainline/ Midas on Mainline] work that was done a few years ago, we now have initial mainline support for this device. The pmOS patch that added initial support is [https://gitlab.com/postmarketOS/pmaports/-/commit/0bab9b5f8a99b6e80cf5def6590d82e6d5dddc3d here]. | ||
Line 231: | Line 184: | ||
== Battery == | == Battery == | ||
With mainline, battery reporting works as of {{MR|2423|pmaports}}, and charging works as of {{MR|2546|pmaports}}. Support for battery reporting and charging with the downstream kernel is unknown. | |||
== | == Warnings and considerations == | ||
=== | === Power === | ||
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 {{issue|1115|pmaports}} 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 === | |||
See {{github|494|Heimdall|Benjamin-Dobell}} | |||
== See also == | |||
* {{wikipedia|Samsung_Galaxy_S_III|Wikipedia}} | |||
* {{Device package|samsung-i9300}} | |||
* {{Kernel package|samsung-i9300}} | |||
* [https://media.ccc.de/v/34c3-8784-emmc_hacking_or_how_i_fixed_long-dead_galaxy_s3_phones Fix long dead Galaxy S3 phone eMMC bug] | |||
* [https://toomoch.github.io/i9300-EMMC-GUIDE/ Guide to revive a bricked i9300 EMMC] | |||
Revision as of 13:42, 22 September 2021
![]() Samsung Galaxy SIII | |
Manufacturer | Samsung |
---|---|
Name | Galaxy S III |
Codename | samsung-i9300, samsung-i9305 |
Released | 2012 |
Hardware | |
Chipset | Exynos 4412 Quad |
CPU | Quad-core 1.4 GHz Cortex-A9 |
GPU | Mali 400 MP4 |
Display | 720x1280 Super AMOLED |
Storage | 16 GB/32 GB |
Memory |
1 GB(GT-i9300 & SHW-M440S) 2 GB(LTE Variants) |
Architecture | armv7 |
Software | |
Original software | Android 4.1.1 |
postmarketOS | |
Category | testing |
Pre-built images | no |
Mainline | yes |
Flashing |
Works |
---|---|
USB Networking |
Works |
Internal storage |
No data |
SD card |
No data |
Battery |
Partial |
Screen |
Works |
Touchscreen |
Works |
Multimedia | |
3D Acceleration |
Works |
Audio |
Broken |
Camera |
No data |
Camera Flash |
No data |
Connectivity | |
WiFi |
Works |
Bluetooth |
Broken |
GPS |
No data |
NFC |
No data |
Modem | |
Calls |
Broken |
SMS |
Broken |
Mobile data |
Broken |
Miscellaneous | |
FDE |
Works |
USB OTG |
No data |
HDMI/DP |
No data |
Sensors | |
Accelerometer |
No data |
Magnetometer |
No data |
Ambient Light |
No data |
Proximity |
No data |
Hall Effect |
No data |
Haptics |
No data |
Barometer |
No data |
Contributors
- Thiagaopluplus
- tyxieblub
- Colaur
Maintainer(s)
Basic info
So far, what works for samsung-i9305 (Galaxy SIII LTE version) also works for the samsung-i9300 (Galaxy SIII 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 SIII models should be confused with the North American SIII 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))
- 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
- DALEK 77 (Notes: 16GB, Pebble Blue)
- Demodé
- Dolphinana (Notes: pmOS with non-free wifi firmware)
- Eldyj (Notes: Chinese battery, running XenonHD with Koffee kernel)
- 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.)
- Jack Kekzoz
- LanaX64
- Missy
- Neilvandyke
- Nergzd723 (Notes: Power button broken, otherwise in perfect condition :D)
- Newbyte
- Nieldv
- Prowindows62 (Notes: Dualboot with postmarketOS and stock Android 4.3)
- Roboe (Notes: (borrowed) GT-I9300 16GB; unreliable USB; running postmarketOS 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
- TPJS (Notes: dont know, where it is currently; running Lineage-OS)
- 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 edge, problem see (2))
- Vipaol (Notes: pmos)
- Vipaol (Notes: stock)
- Vladuwka12 (Notes: Running stock)
- WonderfulShrineMaidenOfParadise
How to enter flash mode
- Hold power + Home + volume down
- When prompted, release all buttons and press volume up
Installation
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 i9305 / i9300 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
WiFi
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.
Network Manager
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
/etc/network/interfaces
e.g.,
$ 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
Restart services
$ sudo rc-service wpa_supplicant restart $ sudo rc-service networking start
WiFi on mainline
To get WiFi working on the mainline kernel install linux-firmware-brcm, then on the device copy nvram_net.txt
like this:
# cp /lib/firmware/postmarketos/nvram_net.txt /lib/firmware/brcm/brcmfmac4334-sdio.txt
On at least 5.13 and 5.14 the driver seem to expect a slightly different file name based on the device model so we can set up a symlink to handle both cases (replace i9305 with i9300 if you have i9300):
# ln -s brcmfmac4334-sdio.txt /lib/firmware/brcm/brcmfmac4334-sdio.samsung,i9305.txt
Afterwards reboot the device and connect to a WiFi network with NetworkManager or wpa_supplicant.
Mainline Kernel
Thanks in large part to the Midas on Mainline work that was done a few years ago, we now have initial mainline support for this device. The pmOS patch that added initial support is here.
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
Blog announcement: https://postmarketos.org/blog/2020/11/06/postmarketOS-in-2020-11-part-1/#mainline-all-the-phones-and-tablets
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 [1]
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 and LineageOS successfully got the Lima driver for Mesa working on Mali when using mainline linux: video success announcement linux-postmarketos-exynos4 now also has the same support.
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.
Battery
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.
Warnings and considerations
Power
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
See Heimdall#494