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: 5332 | Magisk - The Universal Systemless Interface downloadStable official version: 19.3 / v7.2.0 Last update of the program in the header:5.06.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 receive on some devices OTA-update stock firmware. About the application
XDA home page Github releases Important information and FAQ Important information:
Installation / Removal Instructions
Useful links and solutions from furumchan
Stable official version: 19.3 Magisk v19.3 | v7.2.0 MONSTER_PC Official beta version: 19.0 19.0 | v7.1.1 Alex0047 Current official versionCANARY: 19.4 [19.4 (19301) | 7.2.0 (216)] Displax Past versionsCANARY [19.3 (19203) | 7.2.0 (214)] Displax [19.3 (19202) | 7.2.0 (214)] Displax [19.3 (19201) | 7.2.0 (214)] Displax [19.2 (19102) | 7.1.2 (212)] Displax v19.2 (19101) / v7.1.2 (209) Mad_Johnny v19.0 (19005) / v7.1.1 (207) Mad_Johnny 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 [18.0 (19001) | 6.1.0 (166)] gjf [17.4 (17309) | 6.0.1 (155)] gjf Modified Magisk Versions Magisk Manager in settings by kirill22092 Magisk Manager Mod, by Vildanoff Magisk Manager MD2 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: 19.2 stable Alex0047 Version: 19.1 stable Displax Version: 18.1 stable Alex0047 Version: 18.0 stable Alex0047 Version: 17.4 r29 UNOFFICIAL Post Cosiopey Version: 17.4 r28 UNOFFICIAL Post Cosiopey Version: 17.4 r27 UNOFFICIAL Post Cosiopey Version: 17.4 r26 UNOFFICIAL Post Cosiopey Version: 17.4 r24 UNOFFICIAL Post Thoughts Version: 17.4 r21 UNOFFICIAL Post Thoughts Version: 17.1 stable (Post Displax # 76613184) Version: 16.7 beta (Post Displax # 75219232) Version: 16.6 beta (Post Displax # 74879510) Version: 16.4 beta (Post by Alex0047 # 72861219) Version: 16.0 stable (Post Displax # 70622711) Magisk-Xposed-Uninstaller_v1.0.zip(16.23 KB) Beta Magisk: Official beta on XDA | Unofficial beta on xdaandRepository 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 boot (reinstalling the boot 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 with Magisk in recovery or FlashFire:Magisk-v14.0.zip(5.53 MB) 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 you have a recovery curve and the uninstaller did not help, restore the stock boot and manually delete /data/magisk.img, / cache / magisk, / data / busybox. NB! Magisk makes a backup boot to / data / stock_boot_ before performing patching<sha1>.img.gz, so if you have problems, you can always manually unpack the backup, flash the boot 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 boot (reinstalling the boot 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 you have a recovery curve and the uninstaller did not help, restore the stock boot 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 boot 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 you have a recovery curve and the uninstaller did not help, restore the stock boot and manually delete /data/magisk.img, / cache / magisk, / data / busybox. NB! Magisk makes a backup boot to / data / stock_boot_ before performing patching<sha1>.img.gz, so if you have problems, you can always manually unpack the backup, flash the boot 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 ManagerMagisk 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 stock boot. 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 ManagerMagisk 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 boot 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 boot, 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 ManagerMagiskManager-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 stock boot. 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 ManagerMagiskManager-v4.2.6.apk(3.52 MB) Uninstall Magisk v11.1: Flash Uninstaller or FlashFire Recovery Magisk-uninstaller-20170206.zip (338.04 KB) If you have a recovery curve and the uninstaller did not help, restore the stock boot 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 you have a recovery curve and the uninstaller did not help, restore the stock boot 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 - Yesterday 22:51 Reason for editing: Module Addresses, by Goshvit |
Message#82 15.10.16, 00:00 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | |
Message#83 15.10.16, 00:02 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2907 | |
Message#84 15.10.16, 00:11 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | |
Message#85 15.10.16, 00:24 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2907 | dadimon29, Sp? Or AP? Sorry, I overlooked the question about the info about android pey. I saw only about sbonlayn. Only yesterday I cleaned out the supersu from the sberbank, returned phh. What's the problem with AR? Posted on 10/15/2016, 00:25: In the same place everything seems to be registered in the config file. Not comfortable to me -------------------- gavrila |
Message#86 15.10.16, 00:35 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | There is an unofficial Guy in the market. Chinfire writes that there is no such thing at the moment, as if hinting that he will be, but for the time being, use an unofficial type. suhide 0.55 bypasses the latest Safety Net update. Even topjohnwu (author Magyska) says that if Magisk burns, then use SuperSU + suhide, emphasizing that today it is a better solution in terms of hiding. I apologize that without proofs. By the way, the author of phh and topjohnwu saw their Skryvalschiki. Post has been editedilfat12 - 15.10.16, 01:17 |
Message#87 17.10.16, 12:46 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2907 | |
Message#88 17.10.16, 14:44 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | strange of course)), I have no problems. I personally do not use Sberbank Online for want of a card, but in the SuperSU topic I was suggested that the best root checker is Sberbank Online))) I decided to check my bundle Magisk + Xposed + SuperSU + suhide. The result is interesting of course. First it gives: And after a couple of seconds, this: P.S. I apologize for the misinformation, it's not like that.I reinstalled Sberbank Online and forgot to put a tick in the suhide. In fact, with suhide enabled, this whole bundle (Magisk + Xposed + SuperSU + suhide) is being tested by Sberbank Online. P.P.S. A bunch of Magisk + Xposed + phh is also tested by Sberbank Online. What, in principle, already reportedgavrila, only here Xposed was added) Post has been editedilfat12 - 17.10.16, 17:53 |
Message#89 17.10.16, 18:20 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | [email protected], 18:59 The presence of idle bizybox is tantamount to its absence. I repaired myself like this: In the /magisk/.core/ folder I put the symlink on the / data / busybox / folder for the symlinks to the bizybox applets are there. And in the resulting folder /magisk/.core/busybox/ put the symlink on the binary / data / magisk / busybox Now the bizybox works wherever it should You will be surprised at my simlink that you have already created there. Therefore, I have all the BusyBox applets visible to the system. Removed Magisk completely and reinstalled. I wandered into /magisk/.core/ and was surprised that there was really no symlink to the folder / data / busybox / and then I remembered that the last time I climbed in the settings of the Magisk Manager and touched the BusyBox on / off button. Despite the fact that the jackdaw is by default, BusyBox is turned off from the box. If you uncheck, exit the application and log in again, the jackdaw will still stand. It seems that this is a bug of the application. It is necessary to remove the checkbox and reinstall, then the symlink in /magisk/.core/ will appear on the folder with the bizybox applets, more precisely with the symlinks on them. That is, if the daw is on exiting the application, then BusyBox will be activated, if not, then no. The only thing is that the symlink to the bizybox binary itself will still need to be created manually, otherwise applications using bizybox applets directly through a call to the bizybox will be desperate)) |
Message#90 20.10.16, 09:30 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2907 | The manager himself updated from the manager to 2.1 and magic to 8, phh stopped seeing su, needs to be updated, but does not update .. I deleted the magic, installed the magic 8 and phh from scratch, but the update su is also required .. How to fix it? While rolled back to 7 -------------------- gavrila |
Message#91 20.10.16, 10:32 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | gavrila, I'm fine with phh. I do not even know what to offer. It can reinstall the apk itself or clear the data. Also pay attention to Magisk Hide. Maybe because of him. I turned it on and after the first reboot, even the Magisk Manager itself did not see Ruth and even his modules. I rebooted again and everything became normal, but not a single application was seen by Ruth. I had to shut down and restart again. This implementation of Magisk Hide is no good. I had other difficulties. Could not update Magisk Manager from the application itself. Crashed with an error. And when I tried to update myself, Magisk said that it was not a Magisk module. That is, I pressed the update button and wrote to me like that. Do not think that I tried to install the downloaded zip as a module)) In the end, I made everything from recovery. The symlink on the bizybox box went off naturally. It is necessary to create it somewhere else or to make a module at all and install it at boot. Post has been editedilfat12 - 20.10.16, 10:33 Reason for editing: Typo |
Message#92 20.10.16, 10:39 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2907 | |
Message#93 20.10.16, 10:50 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | |
Message#94 20.10.16, 10:52 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2907 | |
Message#95 20.10.16, 23:16 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | Into its universal module added the creation / re-creation of a symbolic link to busybox each time it is loaded. Updates are no longer scary))) And this is the only thing that this module does. From his junk cleaned. Maybe someone will come in handy) All that you want to add to the system section of your android simply add to the system folder of this archive and flash it or install it through the Magisk Manager. You can edit the archive applicationX-plore. By default, folders are merged with existing ones. The existing file is replaced, the missing one is created. To completely replace the existing folder, add an empty file named ".replace". In principle, everything is simple :) All-In-One-Magisk-Module.zip(7.86 KB) Post has been editedilfat12 - 21.10.16, 07:36 |
Message#96 21.10.16, 09:27 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2907 | |
Message#97 21.10.16, 11:05 | |
gavrila [offline] Group: Banned Messages 19699 Check in: 27.04.06 Reputation: 2907 | |
Message#98 21.10.16, 11:42 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | gavrilaTo replace build.prop, you need a module working from the cache section. You can redo this module. In fact, it differs from the base one only in my data in module.prop and the line added in post-fs-data.sh ln -s / data / magisk / busybox / data / busybox / busybox About build.prop. If you need to change only some values ​​and these values ​​are not read only, that is, the corresponding lines do not begin with ro., Then you can not even redo my module, but simply add the necessary line to post-fs-data.sh, for example setprop dalvik.vm.heapsize 1024m setprop ro.sf.lcd_density 240 |
Message#99 21.10.16, 13:26 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | An example of a module for changing the Read Only parameters of build.prop. Took from repository. Google_Assistant-v1.5.zip(6.92 KB) I guess I understood why my cache mode module did not get out of the manager, there was no magisk folder. Now gets up. But not completely removed, but like this module. From the cache is removed, and from / magisk must be removed by hand. Post has been editedilfat12 - 21.10.16, 13:32 Reason for editing: Error |
Message#100 21.10.16, 17:52 | |
Old resident [online] Group: Friendssavagemessiahzine.com Messages 951 Check in: 17.07.13 Oneplus one Reputation: 107 | It turns out the basic module has been updated. Corrections concern only CACHE modules. If you make yourself such a module, then make it based on it. magisk-module-template.zip(6.72 KB) A link to the instructions for creating modules is in the header. The instruction is in English. |
Message#101 23.10.16, 18:34 | |
Local [offline] Group: Friendssavagemessiahzine.com Messages 255 Check in: 11.05.07 Oneplus 5T 8/128 Reputation: 139 | downloaded from the manager and tried to put through it on the LG G2. Now when loading it writes: boot certification verify secure booting error! the inscription disappears and is not loaded further. The second problem - fastboot does not see the phone, writes <waiting for device> Drivers are installed. Accordingly, it did not work in temporary recovery. LG Flash Tool phone sees, flashed on D80230D_00_EUR.kdz Magisk manager can not put anything on the stock, I put the root through the LG One Click Root. Post has been editedJormovich - 23.10.16, 19:11 |
mobile version | Now: 09.06.19, 13:26 |