Assistant
New threads need to be created only inroot partition! In the future, they will be processed by moderators.
If you posted a new version of the program, please notify the moderator by clicking the "Complaint" button on your message.
Catalog of Android programs
REPLY |
® Magisk - The Universal Systemless Interface | Route Manager and Off-System Platform |
Message#1 26.09.16, 23:35 | |
Brain user [offline] Group: Curators Messages 12775 Check in: 09.12.11 Samsung Galaxy Tab S 8.4 LTE Reputation: 5322 | Magisk - The Universal Systemless Interface downloadStable official version: 18.1 / v7.1.1 Last update of the program in the header:28.03.2019 Magisk Module Collectionsavagemessiahzine.com | Magisk Module Discussionsavagemessiahzine.com | Fans Magisk Clubsavagemessiahzine.com | Google Pay does not work!savagemessiahzine.com | GitHub module selection | Selection of XDA modules | Themes XDA Modules For the operation of the program requires root user rights. Short description: An open source utility that allows you to install various system applications and mods in systemless mode and hide the root from any applications and services. Description An open source utility that patches the kernel and allows you to get root-rights (MagiskSU) and install various system applications and modes in systemless mode, i.e., without changing the / system partition. Allows you to run scripts at various stages of mounting and replace files (for example, build.prop) before mounting the / data partition. Allows you to hide the presence of root / unlocked bootloader / permissive-mode SELinux from various banking / email / gaming applications and payment service Android Pay, as well as calmly receive OTA-updates of stock firmware. About the application
XDA home page Github releases Important information and FAQ Important information:
Installation / Removal Instructions
useful links
Stable official version: 18.1 Message №21767, author Alex0047 Official beta version: 19.0 В® Magisk - The Universal Systemless Interface (Post Alex0047 # 83836942) Current official versionCANARY v19.0 (19005) / v7.1.1 (207) Mad_Johnny Past versionsCANARY v19.0 (19004) / v7.1.1 (206) Mad_Johnny [19.0 (19003) | 7.1.1 (205)] Displax [19.0 (19002) | 7.1.1 (205)] Displax [18.2 (18122) | 7.0.0 (200)] Displax [18.2 (18121) | 7.0.0 (199)] Displax [18.2 (18120) | 7.0.0 (199)] Displax [18.2 (18119) | 7.0.0 (199)] Displax [18.2 (18118) | 7.0.0 (198)] Displax [18.2 (18117) | 7.0.0 (197)] Displax [18.2 (18116) | 7.0.0 (196)] Displax [18.2 (18115) | 7.0.0 (196)] Displax [18.2 (18114) | 7.0.0 (194)] Displax Modified Magisk Versions Magisk Manager in settings by kirill22092 Magisk Manager Mod, by Vildanoff Magisk Manager by vsmhell Easy mod repack Magisk 5.5.3 and magisk-installer 15.2: В® Magisk - The Universal Systemless Interface (Post Alex.Strannik # 60100798) Past versions Version: 18.0 stable Message No. 18938, author Alex0047 Version: 17.1 stable ® Magisk - The Universal Systemless Interface (Post Displax # 76613184) Version: 16.7 beta В® Magisk - The Universal Systemless Interface (Post Displax # 75219232) Version: 16.6 beta В® Magisk - The Universal Systemless Interface (Post Displax # 74879510) Version: 16.4 beta В® Magisk - The Universal Systemless Interface (Post Alex0047 # 72861219) Version: 16.0 stable В® Magisk - The Universal Systemless Interface (Post Displax # 70622711) Magisk-uninstaller-20171123.zip(2.64 MB) MagiskManager-v5.4.3.apk(2.29 MB) Magisk-Xposed-Uninstaller_v1.0.zip(16.23 KB) Magisk-uninstaller-20170813.zip(2.76 MB) MagiskManager-v5.1.1.apk(4.5 MB) Magisk-v13.3.zip(5.04 MB) Magisk-v12.0.zip(6.15 MB) Magisk-v11.6.zip(6.15 MB) Magisk Manager_v4.2.7.apk(3.55 MB) Magisk-uninstaller-20170206.zip(338.04 KB) Magisk-v11.1.zip(5.72 MB) MagiskManager-v4.2.6.apk(3.52 MB) Magisk-uninstaller-20170102.zip(338.31 KB) Magisk-v10.2.zip(5.65 MB) Magisk-v7.zip(2.18 MB) Magisk-uninstaller.zip(185.44 KB) Magisk-v6.zip(2.72 MB) Magisk_Manager_v1.2.apk(78.07 KB) Beta Magisk: Official beta on XDA | Unofficial beta on xda and Repository Safetynet Props Mi5 Gitlab Mi5 passing SafetyNet with unlocked bootloader! XDA Install and uninstall past versions of Magisk Install Magisk v14.0: If you already have Magisk installed with MagiskSU root 1) Install / update Magisk Manager:MagiskManager-v5.4.3.apk(2.29 MB) 2) Install / update Magisk from Magisk Manager, restart the device. If you have some other root, while there is no root or Magisk Manager cannot be updated from Magisk Manager 1) Get rid of a third-party root, if there is one (ask questions about this in the theme of this root or in the theme of the firmware of your device).If you have SuperSU, the easiest way is to flasharchive with delete script. 2) Restore the stock kernel (reinstalling the kernel itselfor reinstalling the entire firmware completely - your choice). Ask questions about this in the theme of the firmware of your device. 3) If the old Magisk is already installed, delete it by flashing the FlashFire uninstallerMagisk-uninstaller-20171123.zip(2.64 MB) After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache. 4) Flash archive or archive with Magisk: [attachment = "11596902: Magisk-v14.0.zip"] 5) Install Magisk Manager:MagiskManager-v5.4.3.apk(2.29 MB) Uninstall Magisk v14.0 Stitch in the recovery or FlashFire uninstaller Magisk-uninstaller-20171123.zip (2.64 MB) After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache. If your recovery curve and uninstaller did not help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox. NB! Magisk makes a backup of the kernel in / data / stock_boot_ before performing the patching<sha1>.img.gz, so if you have problems, you can always manually unpack the backup, flash the kernel in TWRP and so bring the device back to life. If you already have Magisk installed with MagiskSU root 1) Install / update Magisk Manager:MagiskManager-v5.1.1.apk(4.5 MB) 2) Install / update Magisk from Magisk Manager, restart the device. If you have some other root, while there is no root or Magisk Manager cannot be updated from Magisk Manager 1) Get rid of a third-party root, if there is one (ask questions about this in the theme of this root or in the theme of the firmware of your device).If you have SuperSU, the easiest way is to flasharchive with delete script. 2) Restore the stock kernel (reinstalling the kernel itselfor reinstalling the entire firmware completely - your choice). Ask questions about this in the theme of the firmware of your device. 3) If the old Magisk is already installed, delete it by flashing the FlashFire uninstallerMagisk-uninstaller-20170813.zip(2.76 MB) After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache. 4) Flash archive with Magisk in recovery or FlashFire:Magisk-v13.3.zip(5.04 MB) 5) Install Magisk Manager:MagiskManager-v5.1.1.apk(4.5 MB) Uninstall Magisk v13.3 Stitch in the recovery or FlashFire uninstaller Magisk-uninstaller-20170813.zip (2.76 MB) After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache. If your recovery curve and uninstaller did not help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox. NB! Magisk makes a backup of the kernel in / data / stock_boot_ before performing the patching<sha1>.img.gz, so if you have problems, you can always manually unpack the backup, flash the kernel in TWRP and so bring the device back to life. Install and uninstall Magisk v12 Installing Magisk v12.0: If you already have root-rights supported by Magisk (MagiskSU, Magisk phh's superuser or the official non-system SuperSU): 1) Install / update Magisk Manager:MagiskManager-v4.3.3.apk(3.44 MB) 2) Install / update Magisk from Magisk Manager, restart the device. If you have some other root, there is no root yet, or it was not possible to install Magisk from Magisk Manager: 1) Restore the stock kernel (reinstalling the kernel itselfor reinstalling the entire firmware completely - your choice). Ask questions about this in the theme of the firmware of your device. 2) If the old Magisk is already installed - delete it by flashing the uninstaller or FlashFire into the recoveryMagisk-uninstaller-20170608.zip(617.59 KB) After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache. 3) Determine the root:
Uninstall Magisk v12.0: Flash Uninstaller or FlashFire Recovery Magisk-uninstaller-20170608.zip (617.59 KB) After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache. If your recovery curve and uninstaller did not help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox. NB! Magisk makes a backup of the kernel in / data / stock_boot_ before performing the patching<sha1>.img.gz, so if you have problems, you can always manually unpack the backup, flash the kernel in TWRP and so bring the device back to life. Install and Uninstall Magisk v11.6 Magisk v11.6 does not work on: Pixel / Pixel XL and some Asus devices. It may not work correctly (Magisk Hide and, as a result, SafetyNet will not work) on Samsung stock firmware and their mods. Installing Magisk v11.6: If you already have root-rights (installed MagiskSU, Magisk phh's superuser or the official non-system SuperSU): 1. Install / Update Magisk Managerfrom google playor from here:Magisk Manager_v4.2.7.apk(3.55 MB) 2. Install / update Magisk from Magisk Manager-a, reboot the device. If you do not have root-rights yet or you could not install Magisk from Magisk Manager: 1. (Recommended) Restore the stock kernel. 2. If the old Magisk is already installed - delete it by flashing the uninstaller using FlashFire or FlashFire [attachment = "9940712: Magisk-uninstaller-20170320.zip"] 3. Determine the root: - If you need easy hiding of the root and a minimum of problems with SafetyNet (i.e. a minimum of problems with Android / Samsung Pay, banks, games), choose MagiskSU. In this case, you must first flash in recovery or FlashFireMagisk-v11.6.zip(6.15 MB) If there is no root, Magisk will install it on the MagiskSU device. - If you have Android 6+ and you needSuperSUflashingSuperSUBefore installing Magisk. Then to hide the root rootsuhide, because Magisk itself does not hide SuperSU. Then already flashingMagisk-v11.6.zip(6.15 MB) 4. Install Magisk Managerfrom google playor from here:Magisk Manager_v4.2.7.apk(3.55 MB) Uninstall Magisk v11.6: Flash Uninstaller in Flash Recovery or FlashFire [attachment = "9940712: Magisk-uninstaller-20170320.zip"] If your recovery curve and uninstaller didn't help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox. Install and uninstall Magisk v11.1 Magisk v1-11.1 does not work for: Sony devices with stock cores, Pixel / Pixel XL, some Asus devices. It may not work correctly (Magisk Hide and, as a result, SafetyNet will not work) on Samsung stock firmware and their mods. Installing Magisk v11.1: If you already have root-rights (installed MagiskSU, Magisk phh's superuser or the official non-system SuperSU): 1. Install / Update Magisk Managerfrom google playor from here:MagiskManager-v4.2.6.apk(3.52 MB) 2. Install / update Magisk from Magisk Manager-a, reboot the device. If you do not have root-rights yet or you could not install Magisk from Magisk Manager: 1. (Recommended) Restore the stock kernel. 2. If the old Magisk is already installed - delete it by flashing the uninstaller or FlashFire into the recoveryMagisk-uninstaller-20170206.zip(338.04 KB) 3. Determine the root: - If you need easy hiding of the root and a minimum of problems with SafetyNet (i.e. a minimum of problems with Android / Samsung Pay, banks, games), choose MagiskSU. In this case, you must first flash in recovery or FlashFireMagisk-v11.1.zip(5.72 MB) If there is no root, Magisk will install it on the MagiskSU device. - If you have Android 6+ and you needSuperSUflashingSuperSUBefore installing Magisk. Then to hide the root rootsuhide, because Magisk itself does not hide SuperSU. Then already flashingMagisk-v11.1.zip(5.72 MB) 4. Install Magisk Managerfrom google playor from here:MagiskManager-v4.2.6.apk(3.52 MB) Uninstall Magisk v11.1: Flash Uninstaller or FlashFire Recovery Magisk-uninstaller-20170206.zip (338.04 KB) If your recovery curve and uninstaller did not help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox. Install and uninstall Magisk v10.2 Installing Magisk v10.2: If you have Android 6 and have a non-system SuperSU installed / have already installed Magisk v7 + with phh's superuser: 1. InstallMagiskManager-v3.1.apk(3.43 MB) 2. Install / update Magisk (and phh's superuser, if installed) from the Magisk Manager, restart the device. If you do not yet have a root / Magisk is already below v7 /, you could not install Magisk from Magisk Manager: 1. If you already have an old Magisk installed - remove it by flashing the Magisk Uninstaller:Magisk-uninstaller-20170102.zip(338.31 KB) 2. Choose the root. - If you need easy hiding of the root and SafetyNet worker (i.e. a minimum of problems with Android / Samsung Pay, banks, games), choosephh's superuser. In this case, you must first flash in recovery or FlashFireMagisk-v10.2.zip(5.65 MB) If there is no root on the device, Magisk will install phh's superuser for you. You will only need to installphh's root manager.apk. - If you have Android 6 and you needSuperSU, first (!) flashing in recovery or FlashFireSuperSU(like nonsystem!), and then flashingMagisk-v10.2.zip(5.65 MB) 3. InstallMagiskManager-v3.1.apk(3.43 MB) 4. (Optional) To hide the root, flashingsuhide, because Magisk itself does not hide SuperSU. Uninstall Magisk v10.2: Flash Uninstaller or FlashFire Recovery Magisk-uninstaller-20170102.zip (338.31 KB) If your recovery curve and uninstaller did not help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox. Install and uninstall Magisk v9 Installing Magisk v9: 1. If you have Android 6 and installed. non-system SuperSU / already installed Magisk v7 + with phh's superuser: - InstallMagisk Manager v2.5.apk, install / update Magisk (and phh's superuser, if installed) from the Magisk Manager, restart the device. 2. If you don’t have root / there is already a Magisk below v7 / it was not possible to install Magisk from Magisk Manager: - If you already have an old Magisk installed - delete it by flashing it in recoveryMagisk Uninstaller. - Choose the root. a) If you need phh's superuser, first flash it in recovery or FlashFireMagisk v9.zipthen flashingphh-superuser-magisk-r266-2.zipand installphh's superuser.apk. b) If you have Android 6 and you need SuperSU, first flash it in recovery or FlashFireSuperSUand then flashingMagisk v9.zip. - InstallMagisk Manager v2.5.apk. Uninstall Magisk v9: flashing in recovery or flashfire Magisk Uninstaller . If your recovery curve and uninstaller did not help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox. Installing and uninstalling Magisk v6-8 Magisk v8 Installing Magisk v8: 1. If you have installed of. non-system SuperSU or already installed Magisk v7 with phh's superuser: - PutMagisk Manager v2.1.apk, install / update Magisk from Magisk Manager and restart the device. 2. If you do not have a root / Magisk is already below v7 / Magisk Manager wasn’t put Magisk Manager: - If you already have an old Magisk installed - delete it by flashing it in recoveryMagisk Uninstaller. - Stitch in recoveryMagisk v8.zipandphh-superuser-magisk.zip. - PutMagisk Manager v2.1.apkandphh's superuser.apk. Uninstall Magisk v8: stitching in recovery Magisk Uninstaller . If your recovery curve and uninstaller did not help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox. Magisk v7 Installing Magisk v7: 1. Make a nandroid backup. 2. Return the / boot and / system partitions to the original stock state,completelyDelete the root and Xposed, if they are installed (for all information about this, look in their topics!). If you want to use a custom kernel, sew it before installing the Magisk. 3. You decide which root you want to use -SuperSUorphh's superuser. If SuperSU - immediately put it, all questions about this ask inhis topic(to work with Magisk SuperSU must be set tonon-systemBefore installing Magisk!). If you decide to use phh's SuperUser, put it after installing Magisk (see below modules for Magisk, p. 1). 4. Stitch in recoveryMagisk-v7.zip(2.18 MB) 5. To manage Magisk modules, install a shell -MagiskManager-v2.0.apk(4.13 MB) You can also install Magisk from Magisk Manager itself (if you have custom recovery). Uninstall Magisk v7: stitching in recovery Magisk-uninstaller-20161004.zip (412.81 KB) Magisk v6 1. Make a nandroid backup. 2. Return the / boot and / system partitions to the original stock state,completelyDelete the root and Xposed, if they are installed (for all information about this, look in their topics!). If you want to use a custom kernel, sew it before installing the Magisk. 3. Stitch in recoveryMagisk-v6.zip(2.72 MB) 4. Choose a root for Magisk (see below modules for Magisk, p. 1). 5. To control the root and SELinux mode, install the shell -Magisk_Manager_v1.2.apk(78.07 KB) Uninstall Magisk v6: stitching in recovery Magisk-uninstaller.zip (185.44 KB) Discussion of the modules is now in the next branch. It does not discuss the unlock, installation of custom recovery, replacement of cores, backups and flashing! Handle it to the topic of your device! For filling caps contact in QMS Post has been editedesleer - 24.04.19, 10:24 Reason for editing: Magisk v19.0 (19005) / v7.1.1 (207) [CANARY] |
Message#42 12.10.16, 10:31 | |
re-direct-er [offline] Group: Curators Messages 10879 Check in: 29.05.10 Asus ZenFone 5 ZE620KL Reputation: 825 | ilfat12and I tell you againthirdalready that I personally! I did not change the boot, not only did I stock it. And what do you have to say to that? Let me remind you that we have already discussedfrom here Post has been editedscile - 12.10.16, 10:32 -------------------- Prize winner in the nominationCurator 4 '17 |
Message#43 12.10.16, 10:45 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | My last phrase yesterday: scile, I expressed only my thoughts) Your device is not at hand, I can not say anything, everything is possible as you say And it’s not the first time that I’m telling you too, that I don’t know why OTA doesn’t arise, but in theory, with the integrity of the relevant sections, OTA should stand up. It is possible, of course, that there are still some nuances, for example, as in your case. I do not detract from your professionalism in flashing your smartphone, so I don’t need to prove that OTA really doesn’t get onto your device after using a temporary TV set. So you can wrap up;) |
Message#44 12.10.16, 17:38 | |
re-direct-er [offline] Group: Curators Messages 10879 Check in: 29.05.10 Asus ZenFone 5 ZE620KL Reputation: 825 | ilfat12, In general, the question was asked not in vain and put an edge: derisive: The solution was found:Club owners Asus Zenfone 2 Laser ZE500KL / ZE500KG (Post by gavrila # 54018605) The only thing I can not remember is whether all TvRP issue a request for a recording mode) -------------------- Prize winner in the nominationCurator 4 '17 |
Message#45 12.10.16, 18:11 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | The only thing I can not remember is whether all TvRP issue a request for a recording mode) Yes, he did everything right. The only thing is, if you do not delete Magisk, but simply restore the stock boot, for example, the same TVRP (previously made backup or boot.img from the fastboot archive) or fastboot, then after updating it will be enough to flash only Magisk v7, you will not have to sew all the modules again, it is more convenient in my opinion, if there are a lot of modules)) Personally, I would do that :) P.S. The easiest option is to return the stock kernel, it is through the same temporary TVRP to flash the backup boot made by Magisk, which is in the root of the data section (/data/stock_boot.img), which Magisk itself does when deleting itself, only it also magisk. img deletes where everything is. By the way, the author saws Magisk hide and this is good news :) Post has been editedilfat12 - 12.10.16, 18:30 Reason for editing: Typo |
Message#46 12.10.16, 18:23 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | Although no, the easiest option is to flash the stock booth via the fastboot, since we still need it to download a temporary TVRP. Then a temporary TVRP and rushed)) Although again, no)) For this option, you need a firmware archive for the fastboot. Extra zamorochki. Through TVRP is still easier. In any case, any option can be used. Who is more convenient)) Post has been editedilfat12 - 12.10.16, 18:44 |
Message#47 12.10.16, 22:41 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | I was confused now on the topic of TWRP vs OTA. First I figured out whether the hash of the system section changes depending on the selected mode of operation when the TV is first run or after resetting its settings. Indeed, the hash changes, it is enough to select the mode and immediately restart the recovery without doing anything else. It turns out that the choice of mode itself already changes the system. I used to assume (nothing based on anything, just speculation) that this is just some kind of protective option against an accidental change of the system)) As a result, the OTA, of course, is not installed. It was necessary, by the way, to roll back to the previous version of the firmware to check it. Experiments with checking the hash carried out three times, the hash is changed and always the same) Also, experiments have shown that on my device, on others it is also possible, OTA does not check what is installed in the recovery section. That is, when TvRP is installed and booted into the temporary stock recovery command: fastboot boot recovery.img OTA is installed without problems. But the boot partition changes are no longer tolerated. From the DPR itself, as expected, it is also not installed, it immediately gives an error 7. The conclusion is: the TvRP mode with respect to the system section should be selected Read Only, while the TVRP can be set to a constant, and the OTA can be sewn from the temporary stock recovery. There is no special difference, you still need a computer, but TVRP on board will never hurt and as a bonus, in the extreme case, you can flash OTA without a computer, restoring the recovery from the same TVRP, but you will need a computer to flash Magisk again. |
Message#48 13.10.16, 15:50 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | I have been waiting for such an opportunity for a long time, to have a root with the support of OTA. But, since on the Nexus 5X I do not use the root out of the box (as you want stability) are you interested in what manipulations to do? The steps are as follows: 1) Unlock bootloader.Keep in mind, as a rule, all data on the smartphone is deleted. Everything is clean.So take care of the backup. 2) Download temporary TVRP in Read Only mode. 3) Flash SuperSU 2.78 SR1 4) If you want to flash non-systemic Xposed 86.2 from topjohnwu. This version is intended to be installed together with SuperSU. 5) Install FlashFire from the market. 6) Upon receipt of the OTA agree to download, but do not install. Most likely the zip will be in the cache section. Flash it from FlashFire, by no means out of recovery, since Ruth will fly off and remember his name, you will need a computer again. Before this case, deal with FlashFire what and how. Yesterday I personally tested it, no errors, everything is beautifully updated. FlashFire will restore the boot itself, flash the update, restore the Route and reboot the device. And backup will do, if necessary. The perfect solution if only Ruth and Xposed are needed. This is all provided FlashFire supports your device. |
Message#49 13.10.16, 15:53 | |
Guru [offline] Group: Friendssavagemessiahzine.com Messages 2277 Check in: 03.02.15 Huawei P10 VTR-L09 Reputation: 122 | [email protected], 15:50 Unlock bootloader. Keep in mind, as a rule, all data on the smartphone is deleted. Everything is clean. Why is that? Nothing was removed even after the firmware, not to mention the bootloader. : yes2: -------------------- Huawei P10 VTR-L29 |
Message#50 13.10.16, 16:05 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | 888nnI know that there are ways to unlock without deleting, but it is still better to be safe. Many on this stung. In general, it is so intended that all user data is deleted during this operation for security reasons. Fastboot oem unlock is supposed to delete user data. Unlock ways and their consequences are best viewed in the subject of your device. I just cautioned just in case))) Post has been editedilfat12 - 13.10.16, 16:12 Reason for editing: Added |
Message#51 13.10.16, 16:15 | |
Guru [offline] Group: Friendssavagemessiahzine.com Messages 2277 Check in: 03.02.15 Huawei P10 VTR-L09 Reputation: 122 | ilfat12Of course, backup should be done without any questions. But here is to remove a forced, controversial statement. Although he is a supporter of the "clean" installation. -------------------- Huawei P10 VTR-L29 |
Message#52 13.10.16, 16:30 | |
Local [offline] Group: Friendssavagemessiahzine.com Messages 332 Check in: 30.04.08 Xiaomi Mi A2 Lite 3/32 Reputation: 14 | |
Message#53 13.10.16, 16:43 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | |
Message#54 13.10.16, 17:11 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | s710,Moreover, even BusyBox is not installed systematically if there is a non-system SuperSU, but you probably don’t need it))) The most important thing with the help of the root is that you do not accidentally hook the system))) so it is important that you are going to do this using the root)) Post has been editedilfat12 - 13.10.16, 17:12 |
Message#55 13.10.16, 17:24 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2905 | |
Message#56 13.10.16, 17:44 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | gavrila, like in modules)) But so far there are few of them. For example, I made one module for myself, I shove there everything I want to change in the system. For example, all sorts of helpers for programs that need to be systemic for getting great features, changing codec configs so that ac3 is out of the box, changing a dialer to a modified one. You can delete system applications without touching the system. The truth for this, I use the Titanium (freeze), but the opportunity is there. You can change the parameters of build.prop. Probably something else can be done. By the way, non-system viper4andriod is available as a module. I edit directly zip itself using X-Plorer. In Magisk, the built-in BusyBox and in my opinion the hosts file is mounted on top of the system one for programs such as AdAway. But I use the Xposed MinMinGuard module. In applications, it cuts ads better, but it does not cut in browsers, unlike the version with hosts. Well, about something like that)) Simply put, you can do almost anything with the system and it will remain even after the update. But not everyone needs this) Post has been editedilfat12 - 13.10.16, 17:59 |
Message#57 13.10.16, 17:59 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2905 | [email protected], 17:44 In Magisk built-in BusyBox Where is he? I did not find it in the / magisk section Ahhh .. Lies in / data / magisk without symlink .. and it does not link anywhere .. With such a bizybox, there is no sense for the console command busybox to my android in this case is unfamiliar Copied the busybox binary from / data / magisk to / magisk / phh / bin and commanded busybox --install -s / system / xbin Now all the links on the ground Post has been editedgavrila - 13.10.16, 18:12 -------------------- gavrila |
Message#58 13.10.16, 18:10 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | |
Message#59 13.10.16, 18:15 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | Lies in / data / magisk without symlink .. and it does not link anywhere .. There is no sense with such a bizybox Dial in the terminal $ PATH and it will be still more clear))) Post has been editedilfat12 - 13.10.16, 18:16 |
Message#60 13.10.16, 18:17 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2905 | [email protected], 18:10 but all utilities are there and the system sees them Really)) I just can not see the root of the program® Secure Settingsin conjunction with the mag and phh-root .. All other applications of the root see -------------------- gavrila |
Message#61 13.10.16, 18:21 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | gavrilaWell, if the applications see, then I think this is enough)) I have Root Check, for example, sees Ruth, and BusyBox does not, but it is clear why))) Post has been editedilfat12 - 13.10.16, 18:22 Reason for editing: Typo |
mobile version | Now: 04/28/19, 20:56 |