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: 5334 | 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 (218)] Displax Past versionsCANARY [19.4 (19301) | 7.2.0 (216)] Displax [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 Version: 16.7 beta Post Displax Version: 16.6 beta Post Displax Version: 16.4 beta Post Alex0047 Version: 16.0 stable Post Displax Version: 15.4 beta 15.4 (1540) | 5.6.0 (100) Displax 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 - 10.06.19, 17:04 Reason for editing: 19.4 (19301) | 7.2.0 (218) |
Message#21922 21.05.19, 12:27 | |
Local [offline] Group: Friendssavagemessiahzine.com Messages 136 Check in: 01.02.17 ZTE Nubia Z9 mini Reputation: 11 | |
Message#21923 21.05.19, 13:45 | |
Local [offline] Group: Friendssavagemessiahzine.com Messages 211 Check in: 27.11.14 Reputation: 0 | Hello, how not to get "magisk not installed" in magisk manager? On Xiaomi Redmi 6, such a problem was, the manager was hidden, after the update I started writing "magisk not installed". The problem was not solved then due to a number of circumstances. Now we need to upgrade from 19.1 to 19.2, the manager is also hidden. How to avoid "magisk not installed"? |
Message#21924 21.05.19, 14:41 | |
Visitor [offline] Group: Active users Messages 23 Check in: 18.03.13 Samsung Galaxy A8 + (2018) SM-A730F Reputation: 2 | In general, Magisk works very badly, the screen is constantly twitching, applications hang and fall off. Post has been editediMiKED - 21.05.19, 19:33 Reason for editing: Edited post at the request of the user |
Message#21925 21.05.19, 14:48 | |
Not guru [offline] Topics Curator Group: Curators Messages 3299 Check in: 23.05.12 Motorola Moto Z3 Play Reputation: 1013 | probably in it. Stock problems are always less. With custom 50/50. I would advise you to try installing a clean boot and immediately magisk.zip Well, probably set to clean. In fact, there are not many options, especially when using the method with the hidden Magisk Manager. What is this firmware? I did not see it in the branch of the apparatus. In general, Magisk works very badly, the screen is constantly twitching, applications hang and fall off. And how in the joke about the bad performers of the Beatles: rofl: Post has been editedesleer - 21.05.19, 15:24 -------------------- |
Message#21926 21.05.19, 14:53 | |
Visitor [offline] Group: Active users Messages 23 Check in: 18.03.13 Samsung Galaxy A8 + (2018) SM-A730F Reputation: 2 | esleer https: //forum.xda-deve…ings-lightrom-t3909159The branch of the device is simply not updated. I don’t think it’s about the firmware, as for me it’s the same stock, only with a couple of tweaks and no garbage. I put Magisk on the stock, the same problem. Post has been editedInfinite_1st - 21.05.19, 14:53 |
Message#21927 21.05.19, 14:58 | |
Not guru [offline] Topics Curator Group: Curators Messages 3299 Check in: 23.05.12 Motorola Moto Z3 Play Reputation: 1013 | Not really. There is a custom kernel at least. I did not read further. Then you just had no luck.Is that pick up version of Magisk, which will work more or less stable. Post has been editedesleer - 21.05.19, 15:13 -------------------- |
Message#21928 21.05.19, 15:02 | |
Visitor [offline] Group: Active users Messages 23 Check in: 18.03.13 Samsung Galaxy A8 + (2018) SM-A730F Reputation: 2 | Is it? The description says stock pie kernel, Magisk is normally updated with it, unlike the custom one.Quantumwhich just falls off. Then I'll try to change the version, thanks. Post has been editedInfinite_1st - 21.05.19, 15:12 |
Message#21929 21.05.19, 15:16 | |
Not guru [offline] Topics Curator Group: Curators Messages 3299 Check in: 23.05.12 Motorola Moto Z3 Play Reputation: 1013 | Infinite_1st, In any case, you should go to your branch and describe the situation there. All the same, there the percentage of users will be more with this device. Perhaps even someone will be with the same use case. I think this is over. Issues of firmware, cores in this thread are not discussed. P.S. I do not protect Magisk, because there are tens of thousands of scripts, if not more. Simply, in practice, a greater percentage of positive rutting of the stock firmware is, but here, too, there are a lot of pitfalls. From this, only in one’s own practice one can understand whether it is successful or not. Post has been editedesleer - 21.05.19, 15:33 Reason for editing: P.S. -------------------- |
Message#21930 21.05.19, 16:08 | |
Local [offline] Group: Friendssavagemessiahzine.com Messages 211 Check in: 27.11.14 Reputation: 0 | |
Message#21931 21.05.19, 16:17 | |
007 [offline] Group: Friendssavagemessiahzine.com Messages 12867 Check in: 10.03.17 Xiaomi Redmi Note 4X Snapdragon 3/32 Reputation: 2720 | So with the ark install .. -------------------- |
Message#21932 21.05.19, 16:17 | |
Not guru [offline] Topics Curator Group: Curators Messages 3299 Check in: 23.05.12 Motorola Moto Z3 Play Reputation: 1013 | Not. Just delete the existing one and install the usual Magisk.apk. And it is better to remove the hidden, through TWRP, clean it with an aninstaller, flash a clean boot and immediately a new Magisk.zip. So there will be more chances of successful rutting. -------------------- |
Message#21933 21.05.19, 16:22 | |
Local [offline] Group: Friendssavagemessiahzine.com Messages 136 Check in: 01.02.17 ZTE Nubia Z9 mini Reputation: 11 | Strange on RR 5.8.5 there was no such thing, but the version of the magic does not affect? I stitched version 18.1 errors and crashes compared to 19.1 and 19.2 was not. Post has been editedoleg_91 - 22.05.19, 12:19 |
Message#21934 21.05.19, 16:28 | |
Sur [offline] Group: Friendssavagemessiahzine.com Messages 8876 Check in: 28.05.14 Samsung Galaxy Note 4 SM-N910C Reputation: 2029 | They say it appears then whenbuild conflict. I.e: Feedback. It is necessary to remove the old MM and update the new one. After that, it was updated and showed that magisk was updated. Post has been editedMAOQ - 21.05.19, 17:12 -------------------- SM-N910C | 4 Mq. |
Message#21935 21.05.19, 20:23 | |
Ophiuchus [offline] Group: Friendssavagemessiahzine.com Messages 12479 Check in: 24.02.13 Huawei Mate 10 Pro 6/128 Reputation: 2666 | |
Message#21936 21.05.19, 20:27 | |
Experienced [online] Group: Friendssavagemessiahzine.com Messages 692 Check in: 01.04.13 Samsung Galaxy S5 SM-G900F Reputation: 7 | |
Message#21937 21.05.19, 20:31 | |
Pro Move Grandfather [offline] Group: Friendssavagemessiahzine.com Messages 6231 Check in: 04.10.11 DEXP Ixion ML350 Force PRO Reputation: 849 | |
Message#21938 21.05.19, 20:34 | |
Ophiuchus [offline] Group: Friendssavagemessiahzine.com Messages 12479 Check in: 24.02.13 Huawei Mate 10 Pro 6/128 Reputation: 2666 | |
Message#21939 21.05.19, 20:39 | |
Experienced [offline] Group: Friendssavagemessiahzine.com Messages 669 Check in: 07.04.13 Pocophone F1 6/128 Reputation: 73 | All Adaway works, I have written that I can not copy the file host? Android version 9 Post has been editeddvs19 - 21.05.19, 20:49 Reason for editing: Added -------------------- Redmi 3S 3/32 - Xiaomi Redmi Note 4X 4/64 - Pocophone F1 6/128 |
Message#21940 21.05.19, 20:40 | |
Experienced [online] Group: Friendssavagemessiahzine.com Messages 692 Check in: 01.04.13 Samsung Galaxy S5 SM-G900F Reputation: 7 | |
Message#21941 21.05.19, 20:44 | |
Pro Move Grandfather [offline] Group: Friendssavagemessiahzine.com Messages 6231 Check in: 04.10.11 DEXP Ixion ML350 Force PRO Reputation: 849 | It works for me.In the settings manager.In general, there will be no notifications. Post has been editedGoshvit - 21.05.19, 20:46 -------------------- "Here you will inevitably become holy. Even worse." © c / f "They fought for their homeland." |
mobile version | Now: 12.06.19, 05:36 |