Browse Source

added all contents

master
DanSman 2 years ago
parent
commit
b0dc4c2c3b
55 changed files with 7649 additions and 15 deletions
  1. +7
    -0
      all-pages.md
  2. +7
    -0
      content/desktop/_Footer.md
  3. +129
    -0
      content/desktop/arch.md
  4. +132
    -0
      content/desktop/manjaro.md
  5. +7
    -0
      content/mobile/_Footer.md
  6. +44
    -0
      content/mobile/android.md
  7. +7
    -0
      content/mobile/android/_Footer.md
  8. +164
    -0
      content/mobile/android/about-android.md
  9. +468
    -0
      content/mobile/android/basic-installation.md
  10. +8
    -0
      content/mobile/android/devices/lg/g2/d801.md
  11. +7
    -0
      content/mobile/android/devices/samsung/galaxy-note-4/_Footer.md
  12. +404
    -0
      content/mobile/android/devices/samsung/galaxy-note-4/n910f.md
  13. +7
    -0
      content/mobile/apple.md
  14. +7
    -0
      content/pwoss/_Footer.md
  15. +63
    -0
      content/pwoss/faq.md
  16. +20
    -0
      content/pwoss/gitea.md
  17. +16
    -0
      content/pwoss/wiki.md
  18. +7
    -0
      content/server/_Footer.md
  19. +2292
    -0
      content/server/arch-scratch-docu.md
  20. +183
    -0
      content/server/arch-x86_64.md
  21. +9
    -0
      content/server/other-arm-devices.md
  22. +946
    -0
      content/server/raspberry-image-docu.md
  23. +192
    -0
      content/server/raspberry-pi.md
  24. +1946
    -0
      content/server/raspberry-scratch-docu.md
  25. +191
    -0
      content/server/software-suite.md
  26. +48
    -13
      custom.css
  27. +49
    -0
      deprecated/custom-roms.md
  28. +64
    -0
      deprecated/good-to-know.md
  29. +9
    -0
      deprecated/lg.md
  30. +30
    -0
      deprecated/projects.md
  31. +15
    -0
      deprecated/samsung.md
  32. +13
    -0
      deprecated/supported-phones.md
  33. +65
    -2
      home.md
  34. BIN
      public/images/icons/desktop.png
  35. BIN
      public/images/icons/mobile.png
  36. BIN
      public/images/icons/pwoss.png
  37. BIN
      public/images/icons/server.png
  38. +93
    -0
      public/images/pwoss-wiki.svg
  39. +0
    -0
      public/templates/compare.mustache
  40. +0
    -0
      public/templates/create.mustache
  41. +0
    -0
      public/templates/edit.mustache
  42. +0
    -0
      public/templates/editor.mustache
  43. +0
    -0
      public/templates/error.mustache
  44. +0
    -0
      public/templates/file_view.mustache
  45. +0
    -0
      public/templates/history.mustache
  46. +0
    -0
      public/templates/history_authors/gravatar.mustache
  47. +0
    -0
      public/templates/history_authors/identicon.mustache
  48. +0
    -0
      public/templates/history_authors/none.mustache
  49. +0
    -0
      public/templates/latest_changes.mustache
  50. +0
    -0
      public/templates/layout.mustache
  51. +0
    -0
      public/templates/livepreview.mustache
  52. +0
    -0
      public/templates/page.mustache
  53. +0
    -0
      public/templates/pages.mustache
  54. +0
    -0
      public/templates/search.mustache
  55. +0
    -0
      public/templates/searchbar.mustache

+ 7
- 0
all-pages.md View File

@ -0,0 +1,7 @@
# All Pages
<center>
Just an overview of all pages.
</center>
------
<<GlobalTOC("All pages")>>

+ 7
- 0
content/desktop/_Footer.md View File

@ -0,0 +1,7 @@
<center>
[&#8679;UP&#8679;](#)
<br>
<br>
<<Navigation("Navigate Desktop", "content/desktop/", true)>>
</center>
[&#60;&#60; back](/)

+ 129
- 0
content/desktop/arch.md View File

@ -0,0 +1,129 @@
# Arch Linux
<center>
__!!!Still under process!!!__
_This isn't recommended!_
&nbsp;
If you have enough time and you would like to learn more about Arch Linux ... go for it!
Otherwise, use Manjaro, Mint, Ubuntu, etc., these are really good Linux distributions!
</center>
------
[[_TOC_]]
&nbsp;
# 1. Requirements
To get your new operating system on your PC you'll need a few things:
Hardware, Software and a little of your time.
&nbsp;
## 1.1. Hardware
### 1.1.1. Minimal system
> - 512 megabyte (MB) of memory (RAM)
> - 800 megabytes (MB) of hard disk space
> - A one gigahertz (GHz) processor
> - A broadband internet connection
> - x86_64-compatible machine
&nbsp;
### 1.1.2. Recommended system
> - 2 gigabyte (GB) of memory (RAM)
> - 8 gigabytes (GB) of hard disk space
> - A 2 gigahertz (GHz) processor
> - A broadband internet connection
> - x86_64-compatible machine
&nbsp;
### 1.1.3. System architecture
The following items are also recommended:
- A reliable 1GB (or greater) USB stick
The USB Stick is necessary for the installation of the system. Also, having a reliable USB stick from a reputable brand will help ensure that the process goes smoothly.
&nbsp;
## 1.2. Software
### 1.2.1. Arch ISO
Download the .iso file and the .iso.sig file from some of the listed provider from [archlinux.org](https://www.archlinux.org/download/) and open the md5.txt file.
> Arch Linux is only available for 64-bit systems.
&nbsp;
Check the two files in the same folder with the following command/s:
- for Arch user
- ```pacman-key -v archlinux-<version>-x86_64.iso.sig```
- other [GnuPGP](https://wiki.archlinux.org/index.php/GnuPG) systems
- ```gpg --keyserver pgp.mit.edu --keyserver-options auto-key-retrieve --verify archlinux-<version>-x86_64.iso.sig```
- and check the md5sum with the following command
- ```md5sum archlinux-<version>-x86_64.iso```
> Another method to verify the authenticity of the signature is to ensure that the public key's fingerprint is identical to the key fingerprint of the [Arch Linux developer](https://www.archlinux.org/people/developers/) who signed the ISO-file. See [Wikipedia:Public-key_cryptography](https://en.wikipedia.org/wiki/Public-key_cryptography) for more information on the public-key process to authenticate keys.
&nbsp;
### 1.2.2. (Optional) Etcher
Download Etcher to flash the ISO
- [Etcher](https://www.balena.io/etcher/) (www.balena.io - link)
&nbsp;
# 2. How To
## 2.1. BIOS
You have to align the boot-start to your USB-Stick.
Depending on your motherboard, you must press the __"esc"__ or __"f2"__ or __"f12"__ or __"end"__ key immediately after the PC starts.
> Check your motherboard/computer manual if no button works or ask us.
__Go to:__
1. Boot
2. BOOT DEVICE PRIORITY (or similar)
Put the USB at the first place (with F5 and F6). Hit the button _esc_ until _save changes and reset_. Hit __enter__ and __yes__.
Reboot and choose Start: Boot Arch Linux (x86_64)
(After installing your operating system, you need to change back your BIOS settings)
&nbsp;
## 2.2. Installation
If you got every [requirements](/content/desktop/arch#1-requirements) then we can go further with the first step (3 steps in total).
Get yourself a coffee or tea and let's go through this.
### 2.2.1. Step 1
#### 2.2.1.1. Flashing the ISO file
```
fdisk -l
```
or with _sudo_
```
sudo fdisk -l
```
(check _of=/dev/sdd_, if it's really your USB Stick!!!)
```
sudo dd bs=4M if=~/Downloads/archlinux-<version>-x86_64.iso of=/dev/sdd
```
> You can also use [Etcher](https://www.balena.io/etcher/) if you prefer a graphical user interface (GUI).
&nbsp;
### 2.2.2. Step 2

+ 132
- 0
content/desktop/manjaro.md View File

@ -0,0 +1,132 @@
# Manjaro Linux
<center>
We choose Manjaro as the first place because of the same reasons like [here](/content/server/software-suite#software-suite_arch-linux-operating-system).
Manjaro Linux is based on Arch Linux.
</center>
------
[[_TOC_]]
# 1. Requirements
To get your new operating system on your PC you'll need a few things:
Hardware, Software and a little of your time.
&nbsp;
## 1.1. Hardware
### 1.1.1. Recommended system
- One gigabyte (GB) of memory (RAM)
- Thirty gigabytes (GB) of hard disk space
- A one gigahertz (GHz) processor
- A high definition (HD) graphics card and monitor
- A broadband internet connection
***Note: It is highly advised that you exceed the recommended requirements for a smooth system operation. Factors such the desktop environment (DE) and user specific applications may require more resources.***
&nbsp;
### 1.1.2. System architecture
The following items are also recommended:
- A reliable 4GB (or greater) USB stick
- Keyboard and mice
The USB Stick is necessary for the installation of the system. Also, having a reliable USB stick from a reputable brand will help ensure that the process goes smoothly.
&nbsp;
## 1.2. Software
Download the .ISO file from [manjaro.org](https://manjaro.org/get-manjaro/).
### 1.2.1. Officially supported desktop environments
- KDE Plasma
- GNOME
- XFCE
Manjaro comes in different "flavors". If you have an old system, you can go with the Xfce desktop environment (DE). Xfce is well-known throughout the enthusiast community for being light on system resources by stripping down on unnecessary features whilst keeping a traditional desktop experience. Its user interface (UI) is quite similar to older versions of Windows (such as XP). If you have a relatively modern system (or a system that is sufficiently fast enough), the K Desktop Environment (KDE) will provide all features of a modern desktop environment, boasting beautiful desktop effects and a plethora of customisation options.
A lot of modern laptops now come with touchscreen support. Linux support for touchscreen laptops greatly depends on the desktop environment and the applications the user wants to use. The GNOME desktop environment, while being known for being heavier on resources, is quite well optimised for touch devices.
Every version has their own strength and weaknesses. Here is an overview of the different versions [quora.com](https://www.quora.com/Is-there-a-good-comparison-between-Cinnamon-Xfce-KDE-and-MATE-Which-one-should-I-choose).
### 1.2.2. 32-bit support
Why isn't there a 32-bit version available? Many developers, as well as the community, have already moved on to 64-bit. While there may be alternatives that support 32-bit systems, it is unknown how long this support can continue before development is deemed "officially dead". The chances are that you are already runnning a 64-bit system! Dropping 32-bit support also frees up some bandwidth that would have been otherwise used for hosting 32-bit ISOs (images) and packages. Hence, Arch Linux (and therefore Manjaro Linux) are only available in 64-bit.
&nbsp;
# 2. How To
The easiest way is to follow the instruction of Manjaro itself.
[manjaro.org](https://osdn.net/projects/manjaro/storage/Manjaro-User-Guide.pdf/)
## 2.1. BIOS
You have to align the boot-start to your USB-Stick.
Depending on your motherboard, you must press the __"esc"__ or __"f2"__ or __"f12"__ or __"end"__ key immediately after the PC starts.
> check your motherboard/computer manual if no button works or ask us.
__Go to:__
1. Boot
2. BOOT DEVICE PRIORITY (or similar)
Put the USB at the first place (with F5 and F6). Hit the button _esc_ until _save changes and reset_. Hit __enter__ and __yes__.
Reboot and choose Start: Boot Manjaro.x86_64 kde.
(After installing your operating system, you need to change back your BIOS settings)
&nbsp;
## 2.2. Partition
We recommend to set up **_3_** partitions. While you may run less than 3 partitions, it was determined that having 3 partitions will enable users to have the greatest amount of flexibility.
1. Choose **_root_** or **_/_** and use ext4 partition and encrypt the root partition 40GB should be enough.
2. The size of the **__swap__** partition greatly depends on the amount of system RAM you have. Having the same sized swap partition as the system RAM should be more than sufficient for a majority of users. If you however need more space for other partitions, and if you have greater than or equal to 8GB of RAM, than you could just take half the size of your system RAM (however you'll be giving up hibernation support). You may or may not have heard of a swap file. For the sake of convenience, you should just stick with a partition.
3. The rest will be for the **_home_** or **__/home__** partition. First of all, choosing a home partition is very important. If someday you want to try another distribution, you can mount the home partition on any Linux system.
This makes it very convenient to try a different distribution without saving your data. But do not forget to save the key from / = “/crypto_keyfile.bin”
So choose also the encryption option for the home partition.
(After installing your operating system, you need to change back your BIOS settings)
&nbsp;
## 2.3. Recommendation
After installing and restarting your new system, connect your system to the internet and look for the terminal application and copy the following command into the terminal:
sudo pacman-mirrors -f 10 && sudo pacman -Syyu
and follow the instruction.
The above command searches and stores details of 10 recently updated package mirrors, and then forces the system to refresh its package database in order to check for new updates.
Afterwards, install at first yaourt for yay (We know, it’s sounds stupid for the pros here)
sudo pacman -S yaourt && yaourt -S yay && sudo pacman -Rs yaourt
It’s just quicker.
If you are using the KDE version, we recommend disabling “Baloo” (the indexing service for KDE). Baloo checks for files stored on the system, however this can be very resource consuming, and hence can degrade system performance.
Terminal command is:
balooctl disable
That’s it. Now take your time and get familiar with Linux.
&nbsp;
<br>
<br>
<center>
<p class="small" class="title"><strong>Problems?</strong></p>
<p class="small">
If you encounter problems, simply create an [issue](https://git.pwoss.xyz/desktop/installation/issues).
</p>
</center>

+ 7
- 0
content/mobile/_Footer.md View File

@ -0,0 +1,7 @@
<center>
[&#8679;UP&#8679;](#)
<br>
<br>
<<Navigation("Navigate Mobile", "content/mobile/android/")>>
</center>
[&#60;&#60; back](/)

+ 44
- 0
content/mobile/android.md View File

@ -0,0 +1,44 @@
# Android
<center>
If you want to add your phone-installation, go to [PwOSS - Gitea](https://git.pwoss.xyz/pwoss/wiki/src/branch/master/mobile/android/devices) and start a pull request.
</center>
------
[[_TOC_]]
&nbsp;
# About Android
If you are not familiar with root, TWRP, flashing, etc., you should first take a look at ['About Android'](/content/mobile/android/about-android).
&nbsp;
# Basic installation
The basic installation is for all phones, but is based on the _Samsung Galaxy Note 4_. The installation differs slightly from other brands. However, we may be able to add more brands in the future.
The basic installation is available [here](/content/mobile/android/basic-installation).
&nbsp;
# Samsung
Samsung has quite a few good phones out there. And a lot of official LineageOS ROMs are available. But Samsung is also very annoying. They have so many different kinds of the same phone which is not really obvious.
The __Galaxy Note 4__ for example has __25 different kinds__. That's the reason, you have to find out the model number first before you download / flash any Custom-ROMs, TWRP etc.
Some has another modem, two sim slots or whatever, but the main different can be the CPU. Qualcomms Snapdragon [Wikipedia](https://en.wikipedia.org/wiki/Qualcomm_Snapdragon) or Samsungs Exynos [Wikipedia](https://en.wikipedia.org/wiki/Exynos).
The Snapdragon CPU has a very good support (Custom-ROMs). We suggest to try to get a Snapdragon CPU.
## Galaxy Note 4
Released, October 2014.
The Galaxy Note 4 is still a very good phone. The problem with it it has no official release of _LineageOS_ and so no _LineageOS for microG_. But it is still possible to use another Custom-ROM. We'll go with _Resurrection Remix_ in this tutorial which is official.
### [N910F](/content/mobile/android/devices/samsung/galaxy-note-4/n910f)
### ...
&nbsp;
# LG
## G2
### [D801](/content/mobile/android/devices/lg/g2/d801)
### ...

+ 7
- 0
content/mobile/android/_Footer.md View File

@ -0,0 +1,7 @@
<center>
[&#8679;UP&#8679;](#)
<br>
<br>
<<Navigation("Navigate Mobile", "content/mobile/android/")>>
</center>
[&#60;&#60; back](/content/mobile/android)

+ 164
- 0
content/mobile/android/about-android.md View File

@ -0,0 +1,164 @@
# About Android
<center>
Some information about root, Custom ROMs, TWRP, other projects ...
</center>
------
[[_TOC_]]
# Background
Android is one of the main operating systems (OS) you will find on a smartphone today. It was developed by Google to compete directly with iOS, the operating system found on iPhones. One of the main reasons why Android was so successful was because it could run on many devices thanks to the Open Handset Alliance (OHA), an initiative that would allow manufacturers such as Samsung and LG to develop smartphones that may look and feel different, but still at the same time run the same operating system (with modifications made by the manufacturer).
Google may have prevented a monopoly that may have otherwise existed should Android have never existed, however it isn't all without some catch. Google is notorious for collecting large amounts of private user data, whether you're on a desktop, laptop, or smartphone. On all (Google certified) smartphones, there must be a Play Store and some Google apps (varies between devices). These apps, while useful for a large majority of users, can extract extensive amounts of information based on the user's search history and etc. However, there are solutions to prevent this and hence re-iterates the need of a guide such as this one.
&nbsp;
# Supported phones
If you want to buy a phone or you have already an Android phone you can check the links below if your phone will be supported.
Check the links below for your phone brand like _Samsung Galaxy Note 4_ and your model name like _N910F_.
1. [wiki.lineageos.org/devices/](https://wiki.lineageos.org/devices/)
2. [www.lineageoslog.com/statistics](https://www.lineageoslog.com/statistics)
3. [www.stats.lineageos.org/](https://stats.lineageos.org/)
> If you can't find your phone in the list, that doesn't mean that there are no other options.
> Send us an [email](mailto:pwoss@pwoss.xyz) or create an [issue](https://git.pwoss.xyz/mobile/installation/issues).
&nbsp;
# Bootloader
On some devices, it is necessary to **open** or **unlock** the **bootloader** before you can install a **custom recovery**, **root** or **custom ROM**.
Unlocking the bootloader usually requires the phone to be wiped of all data, meaning that you'll have the backup everything.
Not all smartphone manufacturers allow the unlocking of the bootloader, so if this concerns you, you must do your **research** before purchasing your next smartphone.
Although uncommon, some manufacturers package an “[eFuse - Wikipedia](https://en.wikipedia.org/wiki/EFUSE)” command in their products, which could brick (permanently damage) your device.
&nbsp;
## How to find out if your bootloader is locked
The best way to find out is to have a look at XDA-developers.
1. Visit your device XDA forum -> [XDA Forum](https://forum.xda-developers.com/)
2. Visit XDA-developers news -> [XDA bootloader news](https://www.xda-developers.com/tag/bootloader/)
&nbsp;
# Recovery
A recovery is an independent, lightweight runtime environment that is included on a separate partition from the main Android operating system on all Android devices. As the name suggests, the main purpose of a recovery is to help recover your device to a working state, however it is possible to make your device soft-bricked (unable to boot) if the wrong actions are performed. You can boot directly into recovery mode and use it to factory reset your device, delete the cache partition, or apply software updates.
&nbsp;
## TWRP - Team Win Recovery Project
Over the years, **TWRP** is the most used **custom recovery**. A custom recovery is necessary to flash a custom ROM and hence TWRP is a suitable solution if your device supports it.<br>
TWRP supports touch interactions, encrypted storage, MTP (mass storage), and many more features to satistfy the needs of a power user. <br>
Search for your device [here](https://twrp.me/Devices/) to get TWRP.<br>
More info about TWRP -> [here](https://twrp.me/about/)
&nbsp;
## Clockworkmod recovery
Clockworkmod (CWM) was the de-facto recovery environment used by savvy Android users until TWRP gained traction in the smartphone market. Its interface was very minimal, coloured text on a black background. Controls were handled using the volume buttons and the power key. It is no longer the recommended recovery to use unless you have an older device that doesn't support TWRP (e.g. Samsung Galaxy S). <br>
How to install on your device -> [here](https://www.xda-developers.com/how-to-install-clockworkmod/)
&nbsp;
# Custom ROMs
## Why bother installing a custom ROM?
We are all familiar with the time where your phone decides to play up and refuses to do what you want it to do. Anecdotal evidence has found that **all** smartphones degrade over time due to heat, stress, wear and etc. However this __doesn't__ mean you can't still make improvements on your phone.
One common cause of slowdowns on your smartphone is the presence of bloatware or "bloat". These apps are **unneeded** and **unwanted**, meaning that they take up your important storage space and memory. A custom ROM however **never** contains any bloatware. This will mean that you will be able to reclaim any of the lost storage space and memory and use it for more important applications. This will translate to **better** performance (and sometimes battery life).
&nbsp;
## Custom ROM options
LineageOS isn't the only custom ROM available. There are heaps of other ROMs you can choose from (Resurrection Remix, CR Droid, Paranoid Android, etc.), each coming with their own unique combination of features and apps.
To get started, it is best to consult on a thread over at the XDA-developers forums ([Wikipedia](https://en.wikipedia.org/wiki/XDA_Developers)). XDA is the first address of all your Android needs.
Like other desktop-operating systems (Arch, Debian, Mint, Ubuntu etc.) you have to find out for yourself which ROM suits **you** best.
&nbsp;
## LineageOS
**LineageOS** is an open-source operating system (OS) for your Android device. In the development community, it is often referred to as a __custom ROM__ (or sometimes aftermarket firmware). Android is generally open-source ([AOSP - Android Open Source Project](https://source.android.com/)), however the Google Apps (GApps) or other manufacturer (Samsung, HTC, ...) applications aren't.
Website: [lineageos.org](https://lineageos.org/)
### LineageOS root
LineageOS has their own option to get root access on your phone. Just flash the [zip](https://download.lineageos.org/extras) through TWRP. (later more)
&nbsp;
## LineageOS for microG
This ROM includes already _[F-Droid](https://wiki.pwoss.xyz/Guideline/Mobile/projects#projects_f-droid)_ & _[microG](https://wiki.pwoss.xyz/Guideline/Mobile/projects#projects_microg)_. This makes installation and achieving more privacy very easy!
Website: [lineage.microg.org](https://lineage.microg.org/)
&nbsp;
## Resurrection Remix OS
Resurrection Remix OS is based on LineageOS with much more settings / features.
Website: [resurrectionremix.com](https://www.resurrectionremix.com/)
&nbsp;
&nbsp;
> If you want you can add more ROMs. Got to [PwOSS - Gitea](https://git.pwoss.xyz/PwOSS/Wiki/src/branch/master/Guideline/Mobile)
&nbsp;
# Root
**Root** is required if you want to have **full control** of your **device**. It's necessary for certain apps like AFWall+, XPrivacyLUA etc. (more on this later)<br>
AFWall+, for example, is using the iptables firewall ([Wikipedia](https://en.wikipedia.org/wiki/Iptables)) which you can only be modified if your device is rooted. It's like the administrator of a software.
You have to be very **careful** to use the **right root applications**. Check the mantainer, date (how long is it available) and if it is open source! A _root app_ also has full control over your device! You must remember this whenever you install a _root app_.
Rooting your phone typically voids your **warranty**, however this can be **reversible** depending on a case-by-case basis. We have never had a problem, but that does not change the fact that some manufacturers may not outright accept your phone for repair should it ever be necessary!
Over-the-air (OTA) updates are not possible with root. This means that your device will no longer receive updates from your smartphone manufacturer. This brings us to the use of custom ROMs. **LineageOS** can support your device (security updates, etc.) even if your device is not longer supported by your smartphone manufacturer! All new security patches straight from Google ([Android Security Bulletin](https://source.android.com/security/bulletin)) are included in all official builds of LineageOS.
Applications such as **bank** apps may **stop working** when they **detect a rooted phone**. You can still use your web browser or a laptop/desktop PC, however there are solutions such as **Magisk hide** that can hide root for specific apps.
But **root is not necessary**!<br>
You could go with a custom ROM but there is no need to use root. For privacy reasons, it is easier to use root, but there are some options without root.
&nbsp;
# Projects
A project overview. Perfectly usable for all your privacy needs.
&nbsp;
## F-Droid
__[F-Droid](https://f-droid.org/)__ is the open source software store for your Android phone! It's available since 2010. Actually mostly every alternative is available.
&nbsp;
## Yalp
Yalp store isn't really an application store. Yalp is getting all the apps directly from Google Play Store. Yalp Store is available at [F-Droid](https://f-droid.org/en/packages/com.github.yeriomin.yalpstore/).
Check microG (next page). It's a good combination.
&nbsp;
## microG
[microG](https://microg.org/) isn't a store as well but if you use yalp it is good to have microG too. Some apps are using the old [GCM](https://developers.google.com/cloud-messaging/) or the new [FCM](https://firebase.google.com/docs/cloud-messaging/). This is important to get messages (notifications) from your apps.
&nbsp;
## Magisk
Magisk is now the most used way to get root access. <br>
Back in the days, it was _Chainfire's - SuperSU_, but it was sold to a Chinese company and was no longer trustworthy.
Magisk is open source and became more and more popular after the years. Magisk is actually more than just _to get root access_. It supports modules which could provide apps, tweaks or services. Some applications (bank apps/NFC/games/etc.) will not work if you have a rooted phone, but with Magisk it possible to hide the _root check_ of the certain apps. This hiding capability may eventually stop working as Google makes these checks stricter.
Official Magisk forum thread -> [here](https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)

+ 468
- 0
content/mobile/android/basic-installation.md View File

@ -0,0 +1,468 @@
# Basic Installation
<center>
This is the basic installation. You can use it as a guide.
</center>
------
[[_TOC_]]
# 1. Requirements
This is a little bit tricky! It can be different depends on your phone.
> If you're not sure how it all works, just send us an [email](mailto:pwoss@pwoss.xyz) or create an [issue](https://git.pwoss.xyz/mobile/installation/issues).
## 1.1. Hardware
You need an Android phone. There is no proper way with an Apple phone.
> [Windows 10 Mobile End of Support](https://pwoss.xyz/windows-10-mobile-end-of-support/)
### 1.1.1. Check bootloader
Find out if your phone has the ability to unlock your bootloader.
[xda-developers.com](https://forum.xda-developers.com/) offers a wide selection of phones that will help you find a tutorial on opening your bootloader, if possible.
Straight to your manufacturer:
- [motorola.com](https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b)
- [htcdev.com](https://www.htcdev.com/bootloader)
- [sony.com](https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/#bootloader_guide)
- [lge.com](https://developer.lge.com/resource/mobile/RetrieveBootloader.dev)
- [xiaomi.com](https://account.xiaomi.com/pass/serviceLogin?callback=http%3A%2F%2Fwww.miui.com%2Fextra.php%3Fmod%3Dxiaomi%2Fauthcallback%26followup%3Dhttp%253A%252F%252Fwww.miui.com%252Funlock%252Fapply.php%26sign%3DYzdhOGVjM2ExNDg0YWJlMGUyYTk4NTUwZDY4OGIyZmI5ZmFmZjEzMw%2C%2C&sid=miuibbs&_locale=en)
- *
> Huawei & Honor discontinued support for unlocking the bootloader. There are paid ways out there that I do not like to post here. Sell the phone and buy another one.
> Don't open your bootloader now! Let's do it when we go through the whole installation. Just check it if it's possible or not. If not, you can sell your phone and buy another one. That's the only way, sorry.
&nbsp;
## 1.2. Software
&nbsp;
### 1.2.1. ADB & fastboot drivers
Depends on your operating system (Linux, Windows, Mac) you have to download the driver for ADB & Fastboot connection (computer to phone).
> Got to [searx.pwoss.xyz](https://searx.pwoss.xyz/) (or whatever you prefer) and search for "adb drivers windows linux and mac". There you can follow a tutorial.
&nbsp;
__Arch Linux & Manjaro Linux:__
```
sudo pacman -S android-tools
```
&nbsp;
### 1.2.2. Custom ROM
Download your ROM from [lineage.microg.org](https://download.lineage.microg.org/).
Get the rom to your phone. Use an external _micro SD card_ if it's possible.
&nbsp;
### 1.2.3. TWRP recovery
Get the recovery from [twrp.me](https://twrp.me/Devices/)
&nbsp;
### 1.2.4. Applications
#### 1.2.4.1. Magisk from GitHub:
[Magisk-'latest-version'.zip](https://github.com/topjohnwu/Magisk/releases/)
[MagiskManager-'latest-version'.apk](https://github.com/topjohnwu/Magisk/releases/)
[Magisk-uninstaller-<latest-date>.zip](https://github.com/topjohnwu/Magisk/releases/)
> Magisk is necessary to get root access and to install EdXposed & riru.
#### 1.2.4.2. Riru from GitHub:
[magisk-riru-core-'latest-version'.zip](https://github.com/RikkaApps/Riru/releases/)
> Riru is necessary for EdXposed.
#### 1.2.4.3. EdXposed from GitHub:
[magisk-EdXposed-'latest-version'.zip](https://github.com/ElderDrivers/EdXposed/releases/)
[EdXposedInstaller_'latest-version'.apk](https://github.com/ElderDrivers/EdXposed/releases/)
[EdXposedUninstaller_rec.zip](https://github.com/ElderDrivers/EdXposed/releases/)
> EdXposed is necessary for XPrivacyLua
#### 1.2.4.4. NanoDroid from nanolx.org:
[NanoDroid-BromiteWebView-<latest-date>.zip](https://downloads.nanolx.org/NanoDroid/Stable/)
#### 1.2.4.5. XPrivacyLua from F-Droid:
[eu.faircode.xlua_'latest-version'.apk](https://f-droid.org/en/packages/eu.faircode.xlua/)
> Scroll down to 'Download APK'
#### 1.2.4.6. AFWall+ from F-Droid:
[dev.ukanth.ufirewall_'latest-version'.apk](https://f-droid.org/en/packages/dev.ukanth.ufirewall/)
> Scroll down to 'Download APK'
Get all downloaded applications on your phone. Use an external _micro SD card_ if it's possible.
Leave __eu.faircode.xlua_'latest-version'.apk__, __dev.ukanth.ufirewall_'latest-version'.apk__, __MagiskManager-'latest-version'.apk__ and __EdXposedInstaller-'latest-version'.apk__ on your computer.
&nbsp;
### 1.2.5. Heimdall (Samsung phones only)
Download _Heimdall_ from [glassechidna.com.au](https://glassechidna.com.au/heimdall/)
> This is necessary to install TWRP.
__Arch Linux & Manjaro Linux:__
```
pikaur -S heimdall
```
&nbsp;
# 2. How To
If you got every [requirements](https://guideline.pwoss.xyz/mobile/installation/basic/requirements) then we can go further with the first step (4 steps in total).
Get yourself a coffee or tea and let's go through this.
## 2.1. Step 1 - Bootloader
### 2.1.1. Backup
If you haven't done it already it's now a good time to do it.
Get all your photos, videos, contacts, calendar, etc. on a separate device.
&nbsp;
### 2.1.2. ADB connection & unlock bootloader __(Not for Samsung phones)__
&nbsp;
#### 2.1.2.1. ADB
Go to your __Settings__ and click on __About phone__. Push the __Build number__ _seven times_ or _more_.
Go __back to__ the main view of the __Settings__ and click on __System__ and __Developer options__ (maybe advanced first).
Turn __Android debugging__ _on_.
Connect your phone via USB to the computer.
&nbsp;
### 2.1.3. Unlock bootloader
Follow the instruction of the [requirements - bootloader (manufacturer)](https://guideline.pwoss.xyz/android/installation/basic/requirements/software) to unlock your bootloader.
> When you unlock your bootloader, all files on your phone will be deleted!
After that reboot your phone without any new installation (just to save time).
&nbsp;
### 2.1.4. TWRP __(Not for Samsung phones)__
This can be necessary again:
Go to your __Settings__ and click on __About phone__ of your phone. Push the __Build number__ _seven times_ or _more_.
Go __back to__ the main view of the __Settings__ and click on __System__ and __Developer options__ (maybe advanced first).
Turn __Android debugging__ _on_.
Connect your phone via USB to the computer again. And go through the following commands:
```
adb reboot bootloader
```
```
fastboot flash recovery your-twrp.img
```
```
adb reboot recovery
```
&nbsp;
### 2.1.5. Heimdall __(Samsung phones only)__
&nbsp;
#### 2.1.5.1. Reboot to Bootloader
Reboot your phone and hold __VOL-DOWN__, __Power Button__ and the __Home Button__ until you see a warning message. Now __VOL-UP__ and you'll see an Android logo and "Downloading ..." etc..
Connect your phone via USB to your computer.
&nbsp;
### 2.1.6. Start Heimdall
#### 2.1.6.1. Device detection
Start Heimdall and go to __Utilities__. Click on __Detect__ by _Detect Device_. You can see by _Output_ __Device Detected__.
&nbsp;
#### 2.1.6.2. Create .pit file
Now you have to create a .pit (Partition Information Table) file.
Click on __Save as__ by _Download PIT_ and choose a folder and name.
&nbsp;
#### 2.1.6.3. Flashing TWRP
Go to __Flash__ and click on __Browse__ by _PIT_. Use the just created .pit file.
Click on __Add__ by _Partitions (files)_ and choose by _Partition Details_ / _Partition Name_ __RECOVERY__. Click on __Browse__ by _File_ and choose __your-twrp.img__.
Now click on __Start__.
Check if an installation line appears on your phone.
You can also see a process in Heimdall under _Status_. It should look like this:
```
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
6%
13%
19%
26%
32%
39%
46%
52%
59%
65%
72%
79%
85%
92%
98%
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
```
&nbsp;
#### 2.1.6.4. Trouble?
For Linux.
If you encounter errors while trying to download your .pit file, you must create a new file on your computer and add the following:
```
sudo nano /etc/udev/rules.d/79-samsung.rules
```
```
ATTRS{idVendor}=="04e8", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="04e8", ATTRS{product}=="Gadget Serial", ENV{ID_MM_DEVICE_IGNORE}="1", ENV{MTP_NO_PROBE}="1"
```
ctrl + x & yes
```
sudo systemctl restart systemd-udevd
```
Try it again. You may need to restart Heimdall if it's still running.
&nbsp;
## 2.2. Step 2 - Recovery
### 2.2.1. Reboot to new recovery
After that, you can reboot your phone to the recovery. Hold __VOL-UP__, __Power Button__ and the __Home Button__ until you reach the new recovery TWRP.
&nbsp;
#### 2.2.1.1. WIPE / delete internal storage
Click on __Wipe__ and on __Advanced Wipe__ and select only:
- __Internal Storage__
Now __Swipe to Wipe__.
> Go back to the main view.
&nbsp;
#### 2.2.1.2. Backup with TWRP
Before we flash a custom-ROM let's do a "quick" backup of your system.
Click on __Backup__ and __Select every Partition__ and __Swipe to Backup__.
> Go back to the main view.
&nbsp;
#### 2.2.1.3. WIPE / delete your phone
Click on __Wipe__ and on __Advanced Wipe__ and select only:
- __Dalvik / ART Cache__
- __System__
- __Data__
- __Cache__
Now __Swipe to Wipe__.
> Go back to the main view.
&nbsp;
### 2.2.2. Custom ROM
Click on __Install__ and __Select Storage__ and choose __Micro SD card__.
Look for _lineage-16.0-20190327-microG-<model-number>.zip_ click on it and __Swipe to confirm Flash__. Wait until it's done. And wipe the _Cache_.
> Go back to the main view.
&nbsp;
### 2.2.3. Applications
&nbsp;
#### 2.2.3.1. Magisk, NanoDroid, Riru & EdXposed
Click on __Install__ and __Select Storage__ and choose __Micro SD card__.
Look for __Magisk-'latest-version'.zip__, __NanoDroid-BromiteWebView-'latest-version'.zip__, __magisk-riru-core-'latest-version'.zip__ and __magisk-EdXposed-'latest-version'.zip__.
Click at first on __Magisk-'latest-version'.zip__ and then __Add more Zips__ and add the other files.
Now __Swipe to confirm Flash__.
Go back to the main view and click on __Reboot__ and __System__.
> It may be necessary to start the phone first before installing all these "applications". This means that after installing your custom ROM you will need to boot the system first. Each additional installation of the application must first be started on the system. Install them all separately if you have problems afterwards.
&nbsp;
## 2.3. Step 3 - Applications
### 2.3.1. Internet connection
Turn all your internet connection off at first.
&nbsp;
### 2.3.2. Install Magisk, EdXposed, XPrivacyLUA & AFWall+ applications
&nbsp;
#### 2.3.2.1. On your phone
Go to your __Settings__ and click on __About phone__ of your phone. Push the __Build number__ _seven times_ or _more_.
Go __back to__ the main view of the __Settings__ and click on __System__ and __Developer options__ (maybe advanced first).
Turn __Android debugging__ _on_.
Connect your phone via USB to the computer.
&nbsp;
#### 2.3.2.2. On your computer
Start the terminal and go to the folder where you downloaded __... .apk__ files. Maybe /home/user/Download:
##### 2.3.2.2.1. Magisk
```
adb install MagiskManager-'latest-version'.apk
```
Check your phone for Magisk. Start Magisk and click on the "burger" (three lines top - left) and on modules.
Check if all are selected (Riru - Core, Riru - Ed Xposed). If not do a reboot.
##### 2.3.2.2.2. EdXposed
```
adb install EdXposedInstaller_'latest-version'.apk && adb install eu.faircode.xlua_'latest-version'.apk && adb install dev.ukanth.ufirewall_'latest-version'.apk
```
Check your phone for EdXposed Installer. Start EdXposed Installer and click on the "burger" (three lines top - left) and on modules.
Select _AFWall+_ and _XPrivacyLUA_.
Do a reboot.
&nbsp;
## 2.4. Step 4 - Configuration
### 2.4.1. Internet connection
Turn your Internet on (WIFI or / and LTE).
&nbsp;
### 2.4.2. AFWall+
Start AFWall+ and click on the _three dots_ (top-right) and click on __Preferences__ and on __UI Preferences__
&nbsp;
#### 2.4.2.1. UI preferences
Select:
- Enable Notifications
- Show notification icon
- Rules Progress
- Show UID for apps
- Confirm AFWall+ disable
Go back and click on __Rules/Connectivity__.
&nbsp;
#### 2.4.2.2. Rules / connectivity
Select:
- Active rules
- Roaming control
- LAN control
- VPN control
> Check IPv6 Chains if you are using IPv6.
Go back to the main view (first start of the app).
&nbsp;
#### 2.4.2.3. Allow internet access for certain apps
Select _WLAN, Mobile Connection (2 arrows without roaming (R)) and VPN_ for:
- [1000] Android System, Advanced, ...
- [10008] Media Storage, Download ...
- Android System Web View
- Browser
- F-Droid
- Magisk Manager
- microG DroidGuard Helper
- *
Depending on your application, you may need to give your application access to the Internet when needed. Each time you install an application, a notification is displayed, and you can choose whether this application needs Internet or not. If no pop-up notification is displayed, it may be because the AFWall + message is not working properly or your installed application does not require Internet access.
&nbsp;
### 2.4.3. microG
&nbsp;
#### 2.4.3.1. Permissions
Start the microG application and grant all necessary permissions. Then click on __Self-Check__ and check everything. It should have everything selected. Maybe _UnifiedNlp status_ did not select everything. That's okay.
&nbsp;
#### 2.4.3.2. Google device registration & cloud messaging
Go back to _microG Settings_ and click __Google Device Registration__ and enable it.
The same applies to __Google Cloud Messaging__.
> If you do not install apps from the Play Store via Yalp, you do not need to enable Google.
> If you're using _AdAway_ or other ADS blocking apps on your phone you'll have to add to your _Whitelist_ = __mtalk.google.com__ if you need Google.
&nbsp;
### 2.4.4. XPrivayLUA
This is quite similar like AFWall+.
Start _XPrivacyLUA_ and click on the "burger" (three lines top - left) and select __Notify on new apps__ and __Restrict new apps__.
Example:
- Contact Apps need the possibility to read you contacts. You have to unselect __Get contacts__.
- GPS need access to your Location. You have to unselect __Get location__.
It's actually pretty obvious.
XPrivacyLUA doesn't block the contacts for example. It fakes it.
If you block __Read clipboard__ and you paste a name to your _Contact app_ it doesn't paste the name. It paste _Private_ instead.
Don't forget that.
That's it. Enjoy
&nbsp;
<br>
<br>
<center>
<p class="small" class="title"><strong>Problems?</strong></p>
<p class="small">
If you encounter problems, simply create an [issue](https://git.pwoss.xyz/mobile/installation/issues).
</p>
</center>

+ 8
- 0
content/mobile/android/devices/lg/g2/d801.md View File

@ -0,0 +1,8 @@
# D801
<center>
__!!!Still under process!!!__
</center>
------
[[_TOC_]]

+ 7
- 0
content/mobile/android/devices/samsung/galaxy-note-4/_Footer.md View File

@ -0,0 +1,7 @@
<center>
[&#8679;UP&#8679;](#)
<br>
<br>
<<Navigation("Navigate Mobile", "content/mobile/android/")>>
</center>
[&#60;&#60; back](/content/mobile/android)

+ 404
- 0
content/mobile/android/devices/samsung/galaxy-note-4/n910f.md View File

@ -0,0 +1,404 @@
# N910F
<center>
This tutorial is for Samsung Galaxy Note 4 model N910F.
</center>
------
[[_TOC_]]
# 1. Requirements
## 1.1. Software
&nbsp;
### 1.1.1. Custom ROM
Download your ROM from [resurrectionremix.com](https://get.resurrectionremix.com/?dir=trlte).
Get the rom to your phone. Use an external _micro SD card_ if it's possible.
&nbsp;
### 1.1.2. TWRP recovery
Get the recovery from [twrp.me](https://twrp.me/samsung/samsunggalaxynote4qualcomm.html)
&nbsp;
### 1.1.3. ADB drivers
> Got to [searx.pwoss.xyz](https://searx.pwoss.xyz/) (or whatever you prefer) and search for "adb drivers windows linux and mac". You can follow a tutorial there.
&nbsp;
__Arch Linux & Manjaro Linux:__
```
sudo pacman -S android-tools
```
&nbsp;
### 1.1.4. Heimdall
Download _Heimdall_ from [glassechidna.com.au](https://glassechidna.com.au/heimdall/)
> This is necessary to install TWRP.
__Arch Linux & Manjaro Linux:__
```
pikaur -S heimdall
```
&nbsp;
### 1.1.5. Applications
#### 1.1.5.1. Magisk from GitHub:
[Magisk-'latest-version'.zip](https://github.com/topjohnwu/Magisk/releases/)
[MagiskManager-'latest-version'.apk](https://github.com/topjohnwu/Magisk/releases/)
[Magisk-uninstaller-'latest-version'.zip](https://github.com/topjohnwu/Magisk/releases/)
> Magisk is necessary to get root access and to install EdXposed & riru.
#### 1.1.5.2. Riru from GitHub:
[magisk-riru-core-'latest-version'.zip](https://github.com/RikkaApps/Riru/releases/)
> Riru is necessary for EdXposed.
#### 1.1.5.3. EdXposed from GitHub:
[magisk-EdXposed-'latest-version'.zip](https://github.com/ElderDrivers/EdXposed/releases/)
[EdXposedInstaller_'latest-version'.apk](https://github.com/ElderDrivers/EdXposed/releases/)
[EdXposedUninstaller_rec.zip](https://github.com/ElderDrivers/EdXposed/releases/)
> EdXposed is necessary for XPrivacyLua
#### 1.1.5.4. NanoDroid from nanolx.org:
[NanoDroid-BromiteWebView-'latest-version'.zip](https://downloads.nanolx.org/NanoDroid/Stable/)
#### 1.1.5.5. XPrivacyLua from F-Droid:
[eu.faircode.xlua_'latest-version'.apk](https://f-droid.org/en/packages/eu.faircode.xlua/)
> Scroll down to 'Download APK'
#### 1.1.5.6. AFWall+ from F-Droid:
[dev.ukanth.ufirewall_'latest-version'.apk](https://f-droid.org/en/packages/dev.ukanth.ufirewall/)
> Scroll down to 'Download APK'
#### 1.1.5.7. FakeGapps from F-Droid:
[com.thermatk.android.xf.fakegapps_'latest-version'.apk](https://f-droid.org/en/packages/com.thermatk.android.xf.fakegapps/)
> Scroll down to 'Download APK'
Get all downloaded applications on your phone. Use an external _micro SD card_ if it's possible.
Leave __eu.faircode.xlua_'latest-version'.apk__, __dev.ukanth.ufirewall_'latest-version'.apk__, __MagiskManager-'latest-version'.apk__, __com.thermatk.android.xf.fakegapps-'latest-version'.apk__ and __EdXposedInstaller-'latest-version'.apk__ on your computer.
&nbsp;
# 2. HowTo
If you got every [requirements](/content/mobile/android/devices/samsung/galaxy-note-4/n910f#1-requirements) then we can go further with the first step (4 steps in total).
Get yourself a coffee or tea and let's go through this.
## 2.1. Step 1 - Heimdall
### 2.1.1. Reboot to bootloader
Reboot your phone and hold __VOL-DOWN__, __Power Button__ and the __Home Button__ until you see a warning message. Now __VOL-UP__ and you'll see an Android logo and "Downloading ..." etc..
Connect your phone via USB to your computer.
&nbsp;
### 2.1.2. Start Heimdall
&nbsp;
#### 2.1.2.1. Device detection
Start Heimdall and go to __Utilities__. Click on __Detect__ by _Detect Device_. You can see by _Output_ __Device Detected__.
&nbsp;
#### 2.1.2.2. Create .pit file
Now you have to create a .pit (Partition Information Table) file.
Click on __Save as__ by _Download PIT_ and choose a folder and name.
&nbsp;
#### 2.1.2.3. Flashing TWRP
Go to __Flash__ and click on __Browse__ by _PIT_. Use the just created .pit file.
Click on __Add__ by _Partitions (files)_ and choose by _Partition Details_ / _Partition Name_ __RECOVERY__. Click on __Browse__ by _File_ and choose __twrp-'latest-version'-trlte.img__.
Now click on __Start__.
Check if an installation line appears on your phone.
You can also see a process in Heimdall under _Status_. It should look like this:
```
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
6%
13%
19%
26%
32%
39%
46%
52%
59%
65%
72%
79%
85%
92%
98%
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
```
&nbsp;
#### 2.1.2.4. Trouble?
For Linux.
If you encounter errors while trying to download your .pit file, you must create a new file on your computer and add the following:
```
sudo nano /etc/udev/rules.d/79-samsung.rules
```
```
ATTRS{idVendor}=="04e8", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="04e8", ATTRS{product}=="Gadget Serial", ENV{ID_MM_DEVICE_IGNORE}="1", ENV{MTP_NO_PROBE}="1"
```
ctrl + x & yes
```
sudo systemctl restart systemd-udevd
```
Try it again. You may need to restart Heimdall if it's still running.
&nbsp;
## 2.2. Step 2 - Recovery
### 2.2.1. Reboot to new recovery
After that, you can reboot your phone to the recovery. Hold __VOL-UP__, __Power Button__ and the __Home Button__ until you reach the new recovery TWRP.
&nbsp;
#### 2.2.1.1. WIPE / delete internal storage
Click on __Wipe__ and on __Advanced Wipe__ and select only:
- __Internal Storage__
Now __Swipe to Wipe__.
> Go back to the main view.
&nbsp;
#### 2.2.1.2. Backup with TWRP
Before we flash a custom-ROM let's do a "quick" backup of your system.
Click on __Backup__ and __Select every Partition__ and __Swipe to Backup__.
> Go back to the main view.
&nbsp;
#### 2.2.1.3. WIPE / delete your phone
Click on __Wipe__ and on __Advanced Wipe__ and select only:
- __Dalvik / ART Cache__
- __System__
- __Data__
- __Cache__
Now __Swipe to Wipe__.
> Go back to the main view.
&nbsp;
### 2.2.2. Custom ROM
Click on __Install__ and __Select Storage__ and choose __Micro SD card__.
Look for _RR-P-'latest-version'-trlte-Official.zip_ click on it and __Swipe to confirm Flash__. Wait until it's done. And wipe the _Cache_.
> Go back to the main view.
&nbsp;
### 2.2.3. Applications
&nbsp;
#### 2.2.3.1. Magisk, Riru & EdXposed
Click on __Install__ and __Select Storage__ and choose __Micro SD card__.
Look for __Magisk-'latest-version'.zip__, __NanoDroid-BromiteWebView-'latest-version'.zip__, __NanoDroid-microG-'latest-version'.zip__, __magisk-riru-core-'latest-version'.zip__ and __magisk-EdXposed-'latest-version'.zip__.
Click at first on __Magisk-'latest-version'.zip__ and then __Add more Zips__ and add the other files.
Now __Swipe to confirm Flash__.
Go back to the main view and click on __Reboot__ and __System__.
> It may be necessary to start the phone first before installing all these "applications". This means that after installing your custom ROM you will need to boot the system first. Each additional installation of the application must first be started on the system. Install them all separately if you have problems afterwards.
&nbsp;
## 2.3. Step 3 - Applications
### 2.3.1. Internet connection
Turn all your internet connection off at first.
&nbsp;
### 2.3.2. Install Magisk, EdXposed, XPrivacyLUA & AFWall+ applications
&nbsp;
#### 2.3.2.1. On your phone
Go to your __Settings__ and click on __About phone__ of your phone. Push the __Build number__ _seven times_ or _more_.
Go __back to__ the main view of the __Settings__ and click on __System__ and __Developer options__ (maybe advanced first).
Turn __Android debugging__ _on_.
Connect your phone via USB to the computer.
&nbsp;
#### 2.3.2.2. On your computer
Start the terminal and go to the folder where you downloaded __... .apk__ files. Maybe /home/user/Download:
&nbsp;
__Magisk__
```
adb install MagiskManager-'latest-version'.apk
```
Check your phone for Magisk. Start Magisk and click on the "burger" (three lines top - left) and on modules.
Check if all are selected (Riru - Core, Riru - Ed Xposed). If not do a reboot.
&nbsp;
__EdXposed__
```
adb install EdXposedInstaller_'latest-version'.apk && adb install eu.faircode.xlua_'latest-version'.apk && adb install dev.ukanth.ufirewall_'latest-version'.apk && adb install com.thermatk.android.xf.fakegapps_'latest-version'.apk
```
Check your phone for EdXposed Installer. Start EdXposed Installer and click on the "burger" (three lines top - left) and on modules.
Select _AFWall+_, _FakeGapps_ and _XPrivacyLUA_.
Do a reboot.
&nbsp;
## 2.4. Step 4 - Configuration
### 2.4.1. Internet connection
Turn your Internet on (WIFI or / and LTE).
&nbsp;
### 2.4.2. AFWall+
Start AFWall+ and click on the _three dots_ (top-right) and click on __Preferences__ and on __UI Preferences__
&nbsp;
#### 2.4.2.1. UI preferences
Select:
- Enable Notifications
- Show notification icon
- Rules Progress
- Show UID for apps
- Confirm AFWall+ disable
Go back and click on __Rules/Connectivity__.
&nbsp;
#### 2.4.2.2. Rules / connectivity
Select:
- Active rules
- Roaming control
- LAN control
- VPN control
> Check IPv6 Chains if you are using IPv6.
Go back to the main view (first start of the app).
&nbsp;
#### 2.4.2.3. Allow internet access for certain apps
Select _WLAN, Mobile Connection (2 arrows without roaming (R)) and VPN_ for:
- [1000] Android System, Advanced, ...
- [10008] Media Storage, Download ...
- Android System Web View
- Browser
- F-Droid
- Magisk Manager
- microG DroidGuard Helper
- microG Service Core
- *
Depending on your application, you may need to give your application access to the Internet when needed. Each time you install an application, a notification is displayed, and you can choose whether this application needs Internet or not. If no pop-up notification is displayed, it may be because the AFWall + message is not working properly or your installed application does not require Internet access.
&nbsp;
### 2.4.3. microG
&nbsp;
#### 2.4.3.1. Spoof package signature
Go to your phone's settings and click on __Apps & notifications__, __Advanced__ and __App permission__.
Now click __Spoof package signature__ and click on the _three dots_ (top-right) and on __Show system__ and select _FakeStore_ and _microG Services Core_.
&nbsp;
#### 2.4.3.2. Permissions
Start the microG application and grant all necessary permissions. Then click on __Self-Check__ and check everything. It should have everything selected. Maybe _UnifiedNlp status_ did not select everything. That's okay.
&nbsp;
#### 2.4.3.3. Google device registration & cloud messaging
Go back to _microG Settings_ and click __Google Device Registration__ and enable it.
The same applies to __Google Cloud Messaging__.
> If you do not install apps from the Play Store via Yalp, you do not need to enable Google.
> If you're using _AdAway_ or other ADS blocking apps on your phone you'll have to add to your _Whitelist_ = __mtalk.google.com__ if you need Google.
&nbsp;
### 2.4.4. XPrivayLUA
This is quite similar like AFWall+.
Start _XPrivacyLUA_ and click on the "burger" (three lines top - left) and select __Notify on new apps__ and __Restrict new apps__.
Example:
- Contact Apps need the possibility to read you contacts. You have to unselect __Get contacts__.
- GPS need access to your Location. You have to unselect __Get location__.
It's actually pretty obvious.
XPrivacyLUA doesn't block the contacts for example. It fakes it.
If you block __Read clipboard__ and you paste a name to your _Contact app_ it doesn't paste the name. It paste _Private_ instead.
Don't forget that.
That's it. Enjoy
&nbsp;
<br>
<br>
<center>
<p class="small" class="title"><strong>Problems?</strong></p>
<p class="small">
If you encounter problems, simply create an [issue](https://git.pwoss.xyz/mobile/installation/issues).
</p>
</center>

+ 7
- 0
content/mobile/apple.md View File

@ -0,0 +1,7 @@
# Apple
<center>
If you are an Apple user, you can add some privacy solutions.
Just fork the [wiki](https://git.pwoss.xyz/pwoss/wiki/) and change the [apple.md](https://git.pwoss.xyz/pwoss/wiki/content/mobile/apple.md) file.
</center>
------

+ 7
- 0
content/pwoss/_Footer.md View File

@ -0,0 +1,7 @@
<center>
[&#8679;UP&#8679;](#)
<br>
<br>
<<Navigation("Navigate PwOSS", "content/pwoss/")>>
</center>
[&#60;&#60; back](/)

+ 63
- 0
content/pwoss/faq.md View File

@ -0,0 +1,63 @@
# FAQ
<center>
All questions and answers around PwOSS.
**(Not done)**
</center>
------
[[_TOC_]]
# PwOSS
## What's PwOSS?
## Why .xyz domain?
## Why Gitea?
### Why not GitHub, GitLab or others??
<br>
***
<br>
# Desktop
## Linux
### What about Microsoft and Apple?
### Why Manjaro or Arch?
#### What about Ubuntu, Debian, Mint ...?
<br>
***
<br>
# Server
## Linux
### Software suite
#### Why Seafile and not Nextcloud?
### What about Debian?
<br>
***
<br>
# Mobile
## Android
### What about Microsoft and Apple?
### Software suite
<br>
***
<br>

+ 20
- 0
content/pwoss/gitea.md View File

@ -0,0 +1,20 @@
# Gitea
<center>
All about [PwOSS - Gitea](https://git.pwoss.xyz/)
**(Not done)**
</center>
------
[[_TOC_]]
# Register
# Create a repository
# Fork a repository
# Create an issue
# Create a pull request
# PwOSS organisations

+ 16
- 0
content/pwoss/wiki.md View File

@ -0,0 +1,16 @@
# Wiki
<center>
All about the Wiki.
**(Not done)**
</center>
------
[[_TOC_]]
# All pages
See [all pages](/all-pages) at once.
# How to use the Wiki
# How to create new Wiki pages

+ 7
- 0
content/server/_Footer.md View File

@ -0,0 +1,7 @@
<center>
[&#8679;UP&#8679;](#)
<br>
<br>
<<Navigation("Navigate Server", "content/server/")>>
</center>
[&#60;&#60; back](/)

+ 2292
- 0
content/server/arch-scratch-docu.md
File diff suppressed because it is too large
View File


+ 183
- 0
content/server/arch-x86_64.md View File

@ -0,0 +1,183 @@
# Arch Linux 64-bit
<center>
A 64-bit server offers much more power than a Raspberry Pi. However, the cost of power (electricity) and hardware could be more than a pi.
> There is no image/iso at the moment. We are [working on creating a bootable USB stick](https://git.pwoss.xyz/server/installation). You have to use the combination guide & scratch for now.
</center>
------
[[_TOC_]]
# 1. Requirements
To get your own server you'll need a few things:
Hardware, Software and a little of your time.
&nbsp;
## 1.1. Hardware
### 1.1.1. Minimal system
- 512 megabyte (MB) of memory (RAM)
- 800 megabytes (MB) of hard disk space
- A one gigahertz (GHz) processor
- A broadband internet connection
- x86_64-compatible machine
&nbsp;
### 1.1.2. Recommended system
- 2 gigabyte (GB) of memory (RAM)
- 8 gigabytes (GB) of hard disk space
- A 2 gigahertz (GHz) processor
- A broadband internet connection
- x86_64-compatible machine
&nbsp;
### 1.1.3. System architecture
The following items are also recommended:
- A reliable 1GB (or greater) USB stick
The USB Stick is necessary for the installation of the system. Also, having a reliable USB stick from a reputable brand will help ensure that the process goes smoothly.
&nbsp;
## 1.2. Software
### 1.2.1. Arch ISO
Download the .iso file and the .iso.sig file from some of the listed provider from [archlinux.org](https://www.archlinux.org/download/) and open the md5.txt file.
> Arch Linux is only available for 64-bit systems.
&nbsp;
Check the two files in the same folder with the following command/s:
- for Arch user
- ```pacman-key -v archlinux-<version>-x86_64.iso.sig```
- other [GnuPGP](https://wiki.archlinux.org/index.php/GnuPG) systems
- ```gpg --keyserver pgp.mit.edu --keyserver-options auto-key-retrieve --verify archlinux-<version>-x86_64.iso.sig```
- and check the md5sum with the following command
- ```md5sum archlinux-<version>-x86_64.iso```
> Another method to verify the authenticity of the signature is to ensure that the public key's fingerprint is identical to the key fingerprint of the [Arch Linux developer](https://www.archlinux.org/people/developers/) who signed the ISO-file. See [Wikipedia:Public-key_cryptography](https://en.wikipedia.org/wiki/Public-key_cryptography) for more information on the public-key process to authenticate keys.
&nbsp;
### 1.2.2. (Optional) Etcher
Download Etcher to flash the ISO
- [Etcher](https://www.balena.io/etcher/)
&nbsp;
### 1.2.3. scratch-docu.md
You can follow the [arch-scratch-docu.md](/content/server/arch-scratch-docu) file or download the file from [PwOSS - Gitea](https://git.pwoss.xyz/server/documentation/src/branch/master/arch-x86_64).
&nbsp;
# 2. How To
## 2.1. BIOS
You have to align the boot-start to your USB-Stick.
Depending on your motherboard, you must press the __"esc"__ or __"f2"__ or __"f12"__ or __"end"__ key immediately after the PC starts.
> Check your motherboard/computer manual if no button works or ask us.
&nbsp;
__Go to:__
1. Boot
2. BOOT DEVICE PRIORITY (or similar)
Put the USB at the first place (with F5 and F6). Hit the button _esc_ until _save changes and reset_. Hit __enter__ and __yes__.
Reboot and choose Start: Boot Arch Linux (x86_64)
> After installing your operating system, you need to change back your BIOS settings
&nbsp;
## 2.2. Installation
If you got every [requirements](/content/server/arch-x86_64#1-requirements) then we can go further with the first step (3 steps in total).
Get yourself a coffee or tea and let's go through this.
### 2.2.1. Step 1
#### 2.2.1.1. Flashing the ISO file
```
fdisk -l
```
or with _sudo_
```
sudo fdisk -l
```
(check _of=/dev/sdd_, if it's really your USB Stick!!!)
```
sudo dd bs=4M if=~/Downloads/archlinux-<version>-x86_64.iso of=/dev/sdd
```
> You can also use [Etcher](https://www.balena.io/etcher/) if you prefer a graphical user interface (GUI).
&nbsp;
### 2.2.2. Step 2
#### 2.2.2.1. Create an no-ip account
Follow the link [www.noip.com](https://www.noip.com/sign-up) and create an account and copy your chosen hostname.
You’ll need it for the installation of the server.
&nbsp;
#### 2.2.2.2. The .md file
Go through the [arch-scratch-docu.md](/content/server/arch-scratch-docu) file. Just copy and paste.
&nbsp;
### 2.2.3. Step 3
#### 2.2.3.1. Reboot server
Done? Did you restart your server? Everything seems to be fine?
Good!
&nbsp;
#### 2.2.3.2. Port forwarding
You’ll need the port forwarded to your Raspberry Pi - IP (192.168.1.76 <- can be this one).
The 1194 (udp) port needs to be open in your router for the [VPN connection](https://en.wikipedia.org/wiki/OpenVPN) (Wikipedia link).
> [www.noip.com](https://www.noip.com/support/knowledgebase/general-port-forwarding-guide/) has a good list of some router brands.
> Your router isn’t listed? Just [email us](mailto:pwoss@pwoss.xyz) or create an [issue](https://git.pwoss.xyz/server/installation/issues).
&nbsp;
#### 2.2.3.3. Primary DNS server
Last step will be to change the DNS server. This is necessary to get every device through Pi-Hole.
Login in to your router and change the "primary DNS server" under "DHCP-Server".
> This can be named differently. Depends on your router.
Delete the "secondary DNS server" and save it.
> Might be necessary to re-login all your connected devices to your WIFI/LAN.
That's it.
&nbsp;
<br>
<br>
<center>
<p class="small" class="title"><strong>Problems?</strong></p>
<p class="small">
If you encounter problems, simply create an [issue](https://git.pwoss.xyz/server/installation/issues).
</p>
</center>

+ 9
- 0
content/server/other-arm-devices.md View File

@ -0,0 +1,9 @@
# other ARM devices
<center>
If you want to try another ARM device like the Banana Pi you could check the [raspberry-scratch-docu](/content/server/raspberry-scratch-docu) or the file from [PwOSS - Gitea](https://git.pwoss.xyz/server/documentation/src/branch/master/arm).
The scratch file should work on all ARM devices - [archlinuxarm.org](https://archlinuxarm.org/platforms).
</center>
------

+ 946
- 0
content/server/raspberry-image-docu.md View File

@ -0,0 +1,946 @@
# Raspberry Image Docu
<center>
This is an copy & paste solution for your Raspberry Pi (ARM) server. A software overview and explanation can be found [here](/content/server/software-suite).
</center>
------
[[_TOC_]]
# 1. Important - before you start check following:
1. Your router needs the possibility of port forwarding and the possibility to configure the DNS server for Pi-hole.
2. You’ll need a DynDNS-Domain. For example, at https://www.noip.com/sign-up.
3. You have to connect a USB Stick/External HardDrive
&nbsp;
## 1.1. Info / Tip
Some commands must be changed by you. The keywords will start with '__your-__'.
- your-interface
- your-password
- your-location
- etc.
We will mark it with the words '__Input required:__ ' above the commands.
Hit the tab key for autocompletion when typing commands.
&nbsp;
Flash the PwOSS - Image file on your SD-Card with Etcher or with the following terminal command.
```
sudo dd bs=4M if=/your/path/to/pwoss-raspberry-arch.img of=/dev/mmcblk0
sync
```
**Make sure _/dev/mmcblk0_ is your SD Card!!!**
&nbsp;
## 1.2. SSH without keyboard
Connection from PC / Mobile per Terminal to your Raspberry Pi.
You have to find your local IP address of your raspberry pi to connect per SSH to the terminal.
Terminal command:
```
arp -n | awk '/b8:27:eb/ {print $1}'
```
In my constellation, it's 192.168.1.76. You can find it on your router as well.
&nbsp;
Open your terminal and type:
```
ssh pwoss@192.168.1.76
pwoss
```
&nbsp;
# 2. PwOSS-Image (resize SD CARD)
```
sudo fdisk /dev/mmcblk0
d
2
n
p
2
```
Enter
```
Y
w
sudo reboot now -h
```
```
ssh pwoss@192.168.1.76
pwoss
sudo resize2fs /dev/mmcblk0p2
```
&nbsp;
# 3. Change timezone
```
timedatectl list-timezones
```
Choose your timezone and copy it.
ctrl z
&nbsp;
__Input required:__
```
timedatectl set-timezone your-location
```
ctrl + x
yes
&nbsp;
# 4. Dm-crypt LUKS
```
sudo cryptsetup -v luksFormat /dev/sda
```
YES
&nbsp;
__Input required:__
passphrase=your-password
```
sudo cryptsetup luksOpen /dev/sda externalHD
```
&nbsp;
__Input required:__
passphrase=your-password
```
sudo mkfs.ext4 /dev/mapper/externalHD
sudo mkdir /mnt/externalHD
sudo cryptsetup luksClose externalHD
sudo dd if=/dev/urandom of=/home/pwoss/.key bs=4096 count=4
sudo chmod 400 /home/pwoss/.key
sudo cryptsetup luksAddKey /dev/sda /home/pwoss/.key
```
&nbsp;
__Input required:__
passphrase=your-password
```
sudo nano /etc/crypttab
```
Add to the bottom:
```
externalHD /dev/sda /home/pwoss/.key luks
```
ctrl + x
yes
```
sudo nano /etc/fstab
```
Add to the bottom:
```
/dev/mapper/externalHD /mnt/externalHD ext4 defaults 0 0
```
ctrl + x
yes
Do a reboot.
```
sudo reboot now -h
```
&nbsp;
# 5. Radicale
```
sudo nano /etc/radicale/config
```
Change the IP to yours:
```
hosts = 192.168.1.76:5232
```
ctrl + x
yes
```
sudo nano /etc/radicale/users
```
&nbsp;
</