website: update translation (#2226)

This commit is contained in:
igor
2024-12-13 01:22:07 -03:00
committed by GitHub
parent 57d4758cd2
commit a634ec2bfc
19 changed files with 108 additions and 108 deletions

View File

@@ -6,11 +6,11 @@ When flashing a device, we may encounter situations when the device becomes "bri
In KernelSU, the following situations may cause boot brick when flashing the boot partition:
1. You flashed a boot image in the wrong format. For example, if your phone's boot format is `gz`, but you flashed an `lz4` format image, then the phone will not be able to boot.
2. Your phone needs to disable AVB verification in order to boot properly (usually requiring wiping all data on the phone).
3. Your kernel has some bugs or is not suitable for your phone to flash.
1. You flashed a boot image in the wrong format. For example, if your device's boot format is `gz`, but you flashed an `lz4` format image, then the device will not be able to boot.
2. Your device needs to disable AVB verification in order to boot properly (usually requiring wiping all data on the device).
3. Your kernel has some bugs or is not suitable for your device to flash.
No matter what the situation is, you can recover by **flashing the stock boot image**. Therefore, at the beginning of the installation tutorial, we strongly recommend that you back up your stock boot before flashing. If you haven't backed up, you can obtain the original factory boot from other users with the same device as you or from the official firmware.
No matter what the situation is, you can recover by **flashing the stock boot image**. Therefore, at the beginning of the installation tutorial, we strongly recommend that you back up your stock boot before flashing. If you have not backed up, you can obtain the original factory boot from other users with the same device as you or from the official firmware.
## Brick by modules