flashed a Samsung Galaxy S8+
This commit is contained in:
parent
0143f30c1a
commit
e0806f0e8e
180
devices/sm-g955f.md
Normal file
180
devices/sm-g955f.md
Normal file
|
|
@ -0,0 +1,180 @@
|
||||||
|
# Steps to flash microG LineageOS on Samsung Galaxy S8+
|
||||||
|
|
||||||
|
download latest TWRP image from https://eu.dl.twrp.me/dream2lte/
|
||||||
|
|
||||||
|
download latest lineageOS unofficial build from https://mega.nz/folder/NYpgFQCY#VYa2sKGXY83vEjOHZ-rIZg
|
||||||
|
|
||||||
|
## Unlock the Bootloader / OEM
|
||||||
|
|
||||||
|
Attach phone to PC. Use a good USB-C cable; make sure that you can use it
|
||||||
|
to copy data.
|
||||||
|
|
||||||
|
Enable developer options
|
||||||
|
|
||||||
|
Enable USB debugging in developer options
|
||||||
|
|
||||||
|
Allow USB debugging access for your PC
|
||||||
|
|
||||||
|
Allow OEM unlock
|
||||||
|
|
||||||
|
## Flash Recovery
|
||||||
|
|
||||||
|
*Right now, flashing recovery only works with Odin; Odin only runs on Windows.
|
||||||
|
Guide how to flash TWRP with Odin:
|
||||||
|
https://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/
|
||||||
|
|
||||||
|
If Heimdall works:*
|
||||||
|
|
||||||
|
Power off the your device and connect the USB adapter to the computer (but not to the device, yet).
|
||||||
|
|
||||||
|
Boot into download mode:
|
||||||
|
|
||||||
|
With the device powered off, hold Volume Down + Home + Power.
|
||||||
|
|
||||||
|
Accept the disclaimer, then insert the USB cable into the device.
|
||||||
|
|
||||||
|
`heimdall flash --RECOVERY twrp-*dream2lte.img`
|
||||||
|
|
||||||
|
Now we don't want to boot into the system, we want into the new recovery
|
||||||
|
directly - so turn off the phone with the power button, and then boot into
|
||||||
|
recovery by holding the power button and volume up for a few seconds. Release
|
||||||
|
them only when you see the blue "Recovery" writing in the top left of the
|
||||||
|
screen.
|
||||||
|
|
||||||
|
Then go to Wipe + Advanced Wipe to wipe the following partitions:
|
||||||
|
|
||||||
|
* System
|
||||||
|
* Data
|
||||||
|
* Cache
|
||||||
|
* Dalvik
|
||||||
|
|
||||||
|
We also had to "Format Data", because the data partition could not be mounted
|
||||||
|
first.
|
||||||
|
|
||||||
|
Then go to Advanced/ADB Sideload, swipe to the right, and execute `adb sideload lineage-xxx.zip` on your computer.
|
||||||
|
* When it shows something like `Total xfer: 1.00x` or `adb: failed to read command: Success` on the PC, and `Exit code: 1.000000` in TWRP, it has suceeded.
|
||||||
|
|
||||||
|
Unfortunately addonsu doesn't exist for lineageOS 17, so we need to find
|
||||||
|
another rooting tool, e.g. Magisk. This would also be flashed at this point.
|
||||||
|
|
||||||
|
Reboot to start LineageOS!
|
||||||
|
|
||||||
|
### Finish Installation
|
||||||
|
|
||||||
|
Go through the setup screen and choose what you want. You can be as restrictive
|
||||||
|
as you want. Make sure to choose a Wi-Fi, so you can proceed with the next
|
||||||
|
steps; you can also do this at any later time.
|
||||||
|
|
||||||
|
You should also choose a screen lock pin. Patterns are not very secure (you can
|
||||||
|
often see them by holding the phone into the light at the right angle).
|
||||||
|
Passwords are a bit inconvenient (but most secure). Do *not* use a fingerprint
|
||||||
|
sensor, they are really insecure.
|
||||||
|
|
||||||
|
<!--
|
||||||
|
*We didn't try this out yet:*
|
||||||
|
|
||||||
|
## Install microG
|
||||||
|
|
||||||
|
### Signature Spoofing
|
||||||
|
|
||||||
|
To install microG, you need to first patch the ROM to allow signature spoofing.
|
||||||
|
[tingle](https://github.com/ale5000-git/tingle) is a useful tool for this.
|
||||||
|
After installation, do the following steps:
|
||||||
|
|
||||||
|
1. Make sure Developer options is enabled. This is hidden by default since
|
||||||
|
sometime in Android 4.x, you can show it by going to About phone and tapping
|
||||||
|
on the Build number 7 times in succession.
|
||||||
|
2. In the developer settings, find the setting for Android debugging and enable
|
||||||
|
it.
|
||||||
|
3. Find the setting for Root access and make sure ADB has root access.
|
||||||
|
4. Connect your device via USB.
|
||||||
|
5. Now, on the computer, run python main.py (or python3 main.py).
|
||||||
|
6. Select the option 1 to allow the patcher to do everything automatically.
|
||||||
|
7. Reboot the device
|
||||||
|
|
||||||
|
### Install microG via F-Droid
|
||||||
|
|
||||||
|
Now you can install microG via F-Droid. First add [the microG F-Droid
|
||||||
|
repository](https://microg.org/fdroid.html). Refresh the sources. Then you can
|
||||||
|
install the app GMScore via the repository.
|
||||||
|
|
||||||
|
### Initial microG Setup
|
||||||
|
|
||||||
|
Finally, open the "microG settings" app which should now have appeared. Follow
|
||||||
|
the instructions by
|
||||||
|
[shadow53](https://shadow53.com/android/no-gapps/setup-guide/microg/#initial-setup).
|
||||||
|
|
||||||
|
-->
|
||||||
|
|
||||||
|
## Device Encryption
|
||||||
|
|
||||||
|
Charge the phone to 100%.
|
||||||
|
|
||||||
|
Go to the Security Settings and encrypt the phone. During the process, it
|
||||||
|
reboots once and asks you for the device PIN. It can take a while, but not soo
|
||||||
|
long actually.
|
||||||
|
|
||||||
|
<!--
|
||||||
|
|
||||||
|
### Secure the device encryption
|
||||||
|
|
||||||
|
You usually want to have a long password for your device encryption, which you
|
||||||
|
only have to enter when the phone boots, and a shorter PIN for your lockscreen.
|
||||||
|
By design, Android doesn't allow this; this is a workaround to make it possible
|
||||||
|
still.
|
||||||
|
|
||||||
|
We will also install an app which shuts down the phone when you get the unlock
|
||||||
|
code wrong 5 times in a row.
|
||||||
|
|
||||||
|
#### Wrong PIN Shutdown
|
||||||
|
|
||||||
|
Open the F-Droid app, wait until it is done with "Updating repositories".
|
||||||
|
|
||||||
|
Install the app "Wrong PIN Shutdown".
|
||||||
|
|
||||||
|
Now go to the developer settings, and enable root for Apps and ADB.
|
||||||
|
|
||||||
|
Open "Wrong PIN Shutdown", grant Admin rights until forever, activate the
|
||||||
|
function, and set it to shut down the phone after 5 wrong tries to enter the
|
||||||
|
PIN. You can try it out directly - if you enter your PIN wrong 5 times, does it
|
||||||
|
shut down?
|
||||||
|
|
||||||
|
#### Change the encryption password to a long password
|
||||||
|
|
||||||
|
First you need to enable USB debugging again. You can enable the developer
|
||||||
|
options at "About Phone", tap the "build number" seven times. After you enabled
|
||||||
|
it, you can find the Developer options in the settings at "System > Advanced >
|
||||||
|
Developer Options". Enable USB debugging and reboot into the bootloader mode:
|
||||||
|
|
||||||
|
Then go to the Security settings and set the PIN you want to use for your
|
||||||
|
lockscreen.
|
||||||
|
|
||||||
|
Now you have to backup the files where it is saved. To do so, execute these
|
||||||
|
commands with adb - you need to be connected to a PC with a proper USB cable:
|
||||||
|
|
||||||
|
```
|
||||||
|
adb root
|
||||||
|
adb pull /data/system_de/0/spblob/
|
||||||
|
adb pull /data/misc/keystore/user_0/1000_USRPKEY_synthetic_password_* # the file has a different name; just remove the * and press tab before executing it
|
||||||
|
adb pull /data/system/locksettings.db
|
||||||
|
```
|
||||||
|
|
||||||
|
Now, go to the Security settings again, and change your PIN to the password you
|
||||||
|
want to use for the encryption. Unfortunately you can use maximally 17
|
||||||
|
characters.
|
||||||
|
|
||||||
|
Finally, you use adb again to restore the backup of the PIN, which changes your
|
||||||
|
lockscreen PIN, but not your encryption passphrase:
|
||||||
|
|
||||||
|
```
|
||||||
|
adb push locksettings.db /data/system/locksettings.db
|
||||||
|
adb push 1000_USRPKEY_synthetic_password_* /data/misc/keystore/user_0/ # the filename will be different with your device
|
||||||
|
adb push spblob/ /data/system_de/0/
|
||||||
|
```
|
||||||
|
|
||||||
|
When you try to unlock your screen now, you will realize that you still have to
|
||||||
|
enter the encryption passphrase. So reboot the phone; enter the encryption
|
||||||
|
passphrase at startup, as desired. When the phone has booted, you can use the
|
||||||
|
(shorter) PIN to unlock your phone.
|
||||||
|
|
||||||
|
-->
|
||||||
Loading…
Reference in a new issue