![]() ![]() Prerequisite: Your device must be rooted. This method is suitable for any installation (not limited to initial installation or subsequent upgrades), as long as you use TWRP. Use adb to put AnyKernel3-*.zip into the phone /sdcard and choose to install it in the TWRP GUI or you can directly adb sideload AnyKernel-*.zip to install.66, then you should download the file AnyKernel3-android12-5.10.66_yyyy-MM.zip (where yyyy is the year and MM is the month). From the Release page of KernelSU, download the zip package starting with AnyKernel3 that matches your phone version for example, the phone kernel version is android12-5.10.Prerequisite: Your device must have a custom Recovery, such as TWRP if not or only official Recovery is available, use another method. Repair the boot.img manually and install it.Install with fastboot using the boot.img provided by KernelSU.Install with a kernel flash app, such as Franco Kernel Manager.There are several installation methods for KernelSU, each suitable for a different scenario, so please choose as needed. If you need to flash, please always refer to the kernel version!! Introduction If the Android system is upgraded later, the kernel version will generally not change. ![]() If you find that your kernel version is android12-5.10.101, but your Android system version is Android 13 or other please don't be surprised, because the version number of the Android system is not necessarily the same as the version number of the Linux kernel The version number of the Linux kernel is generally consistent with the version of the Android system that comes with the device when it is shipped. Please note: Kernel version and Android version are not necessarily the same! Most should have this disabled by default.Note that the SubLevel in the kernel version is not part of the KMI! That means that 5.10.101-android12-9-g30979850fc20 has the same KMI as 5.10.137-android12-9-g30979850fc20! Kernel version vs. Usage of the trash utility for removable drives can (usually) be configured from the respective OS. This can usually be checked for by searching for a hidden “Trash” folder on the connected drive (this will vary for each OS): If you were managing files from an external source such as another computer, ensure that its Trash bin is emptied as well while the drive is connected. Files that are deleted via the network share aren't sent to the trash can. Click on Edit in the menu bar located at the top of the screen in the file manager, then go to Preferences and uncheck the “Move deleted files to “trash can” instead of erasing from disk” checkbox. If you'd like to avoid this issue in the future you can tell the file manager to not use your trash folder and default to instantly deleting files. Batocera Nation's video demonstrating this procedure. The rm -rf /path/to/somewhere command is capable of destroying your hard-drive, so be very careful with your spelling on this. You can also do this via SSH by running rm -rf /userdata/system/.local/share/trash/. If so, you can forcefully remove the files by navigating to /userdata/system/.local/share/Trash/files, selecting everything and pressing + to delete all the contents. If you've already done that and still get the error, it could be that Trash Can has failed to actually removed the files. Perhaps the Trash folder still has your files stored on the drive? You can clear these out by going to the file manager ( on the system list), clicking Trash Can and clearing it out. Write themes for batocera-emulationstation.Redirect upgrades from any board to my own builds. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |