You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Sony | Xperia Z | yuga | C6603 | tested
40
40
Sony | Xperia Z3 | z3 | | under development
41
41
Sony | Xperia ZX | kagura | | planned
42
42
Fairphone | Fairphone 2 | FP2 | | under development
43
-
Fairphone | Fairphone 3 | FP3 | | planned
43
+
Fairphone | Fairphone 3 | FP3 | | under development
44
44
Motorola | Moto G5 | cedric | | planned
45
45
Motorola | moto g7 power | ocean | | under development
46
46
@@ -75,7 +75,11 @@ All kinds of contributions are welcome. These include:
75
75
76
76
### How to contribute your own installation configurations
77
77
78
-
If you want to use the tool for a non-supported smartphone, the fastest way is to adapt an [existing config file](https://github.com/openandroidinstaller-dev/openandroidinstaller/tree/main/openandroidinstaller/assets/configs).
78
+
If you want to use the tool for a non-supported smartphone, the fastest way is to adapt an [existing config file](https://github.com/openandroidinstaller-dev/openandroidinstaller/tree/main/openandroidinstaller/assets/configs). The file should be named after the `device code` of your device. This is in general the output by `adb shell getprop | grep ro.product.device` when the devices is connected to the computer. You can also get the device code by connecting the device to the computer and run OpenAndroidInstaller to detect the device.
79
+
80
+
**To test your config file with the executable** without using the developer setup, place it in the same directory as the executable. There it will be detected by name. After you created a config file and it works fine, you can open a pull request to make the file available to other users. Please also add the device to the supported devices table above.
81
+
82
+
#### Content of a config file
79
83
80
84
Every step in the config file corresponds to one view in the application. These steps should contain the following fields:
81
85
-`title`: str; Describing the overall goal of the step. Will be displayed in the header of the view.
@@ -94,11 +98,6 @@ Every step in the config file corresponds to one view in the application. These
94
98
-`allow_skip`: [OPTIONAL] boolean; If a skip button should be displayed to allow skipping this step. Can be useful when the bootloader is already unlocked.
95
99
-`link`: [OPTIONAL] Link to use for the link button if type is `link_button_with_confirm`.
96
100
97
-
The file should be named after device name output by `adb shell getprop | grep ro.product.device` when the devices is connected to the computer. You can also get the device code by connecting the device to the computer and run OpenAndroidInstaller to detect the device.
98
-
99
-
To test your config file with the executable without using the developer setup, place it in the same directory as the executable. There it will be detected by name.
100
-
After you created a config file and it works fine, you can open a pull request to make the file available to other users. Please also add the device to the supported devices table above.
101
-
102
101
### How to build the application for your platform
103
102
104
103
The executables for the OpenAndroidInstaller are build with [pyinstaller](https://pyinstaller.org/en/stable/index.html). You can create builds for MacOS or Linux with `make build-app`. For Windows the paths need to be modified. For now, you can have a look [here](https://github.com/openandroidinstaller-dev/openandroidinstaller/blob/v0.1.2-alpha/.github/workflows/manual-build-windows.yml#L22) on how it's done.
Now you need to flash a custom recovery system on the phone. A recovery is a small subsystem on your phone, that manages updating,
18
+
adapting and repairing of the operating system.
19
+
- title: "Flash a custom recovery"
20
+
type: call_button
21
+
content: Turn on your device. Once the device is fully booted, you need to reboot into the bootloader again by pressing 'Confirm and run' here. Then continue.
22
+
command: "adb reboot bootloader"
23
+
- title: "Flash a custom recovery"
24
+
type: call_button
25
+
content: Once the device is in fastboot mode, flash the custom recovery (temporarily) by pressing 'Confirm and run'. Once it's done continue.
26
+
command: "fastboot flash boot <recovery>"
27
+
- title: "Flash temporary recovery"
28
+
type: confirm_button
29
+
content: >
30
+
Now reboot into recovery to verify the installation. Do not reboot into the existing OS, since it will overwrite the recovery you just installed!
31
+
With the device powered off, hold 'Volume Up + Power'. Release when boot logo appears.
32
+
install_os:
33
+
- title: "Flash LineageOS"
34
+
type: confirm_button
35
+
content: >
36
+
Now tap 'Factory Reset', then 'Format data / Factory reset' on your phone screen and continue with the formatting process.
37
+
This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
38
+
- title: "Flash LineageOS"
39
+
type: confirm_button
40
+
content: Return to the main menu on the phone.
41
+
- title: "Flash LineageOS"
42
+
type: confirm_button
43
+
content: On the device, select “Apply Update”, then “Apply from ADB” to begin sideload. Then confirm here.
44
+
- title: "Flash LineageOS"
45
+
type: call_button
46
+
content: >
47
+
Now it's time to flash the LineageOS image. Don't remove the USB-Cable and press 'Confirm and run' to start!
48
+
This might take a while. Confirm after it's done.
49
+
command: "adb sideload <image>"
50
+
- title: "Flash LineageOS"
51
+
type: confirm_button
52
+
content: Flashing finished. Now press 'back' (arrow) and then 'Reboot system now' on the phone screen to finish the installation. Then confirm here.
0 commit comments