I rooted my Motorola One Macro yesterday, I unlocked bootloader and installed Magisk. I don't have custom recovery beacuse i had problem with installing it. Root Checker says root is properly installed on my device, but I have somme issues with getting things to work. I downloaded Magic Mask Repo, and tried installing Energized module. It downloaded suscessfully, but installation doesn't seem to do anything even after reboot. I also tried installing it manually with Magisk, but I got this in console:
- Copying zip to temp directory
! Unzip error
Pasting uzipped energized folder to /data/adb/modules makes it appear in module section in Magisk, but still it don't work. Material Terminal says acces denied after typing in energized - m command. Reinstallation of Magisk didnt helped. I dont really want to factory reset my phone, is there anything that i can do?
_lama195 said:
I rooted my Motorola One Macro yesterday, I unlocked bootloader and installed Magisk. I don't have custom recovery beacuse i had problem with installing it. Root Checker says root is properly installed on my device, but I have somme issues with getting things to work. I downloaded Magic Mask Repo, and tried installing Energized module. It downloaded suscessfully, but installation doesn't seem to do anything even after reboot. I also tried installing it manually with Magisk, but I got this in console:
- Copying zip to temp directory
! Unzip error
Pasting uzipped energized folder to /data/adb/modules makes it appear in module section in Magisk, but still it don't work. Material Terminal says acces denied after typing in energized - m command. Reinstallation of Magisk didnt helped. I dont really want to factory reset my phone, is there anything that i can do?
Click to expand...
Click to collapse
this is an easy one....
that error *usually* implies youve downloaded a master zip of a github repo, and not a zip file from the releases section
if you went to
GitHub - Magisk-Modules-Repo/energizedprotection: Energized Protection Magisk Module.
Energized Protection Magisk Module. Contribute to Magisk-Modules-Repo/energizedprotection development by creating an account on GitHub.
github.com
and then downloaded the zip it will NOT work, and they dont have a release
so heres the easy fix, and why it fails
1) unzip the file, you'll get a folder (energizedprotection-master)
Note this is why magisk wont install it, it expects to find files (especially crucial files to tell it how to install the module) and folders in the root directory, not a single folder with nested files and folders under it...
2) go into energizedprotection-master folder
3) select all files/folders
4) zip the selected contents into a new zip file (ideally with 7zip - WinRAR can create dud zips)
5) move that zip to device and flash
Ideally you'll install Fox's Magisk Module Manager and use that for most modules - energized may not be on it - download the .apk
Release Release v2.0.2 · Fox2Code/FoxMagiskModuleManager
Please read the full changelog. It contains very important information on the future of this app and caveats when updating. Release notes: https://www.androidacy.com/magisk-module-download-simplifi...
github.com
the old magisk repo was decommisioned....
It works now, I greatly appreciate it, thanks!
73sydney said:
this is an easy one....
that error *usually* implies youve downloaded a master zip of a github repo, and not a zip file from the releases section
if you went to
GitHub - Magisk-Modules-Repo/energizedprotection: Energized Protection Magisk Module.
Energized Protection Magisk Module. Contribute to Magisk-Modules-Repo/energizedprotection development by creating an account on GitHub.
github.com
and then downloaded the zip it will NOT work, and they dont have a release
so heres the easy fix, and why it fails
1) unzip the file, you'll get a folder (energizedprotection-master)
Note this is why magisk wont install it, it expects to find files (especially crucial files to tell it how to install the module) and folders in the root directory, not a single folder with nested files and folders under it...
2) go into energizedprotection-master folder
3) select all files/folders
4) zip the selected contents into a new zip file (ideally with 7zip - WinRAR can create dud zips)
5) move that zip to device and flash
Ideally you'll install Fox's Magisk Module Manager and use that for most modules - energized may not be on it - download the .apk
Release Release v2.0.2 · Fox2Code/FoxMagiskModuleManager
Please read the full changelog. It contains very important information on the future of this app and caveats when updating. Release notes: https://www.androidacy.com/magisk-module-download-simplifi...
github.com
the old magisk repo was decommisioned....
Click to expand...
Click to collapse
Hey I am trying to install BCR - Module module from github " https://github.com/chenxiaolong/BCR " but I am unable to install it in magisk. It is throwing the same error . Can you help me with that ? Thanks in advance
Arnavsingh7075 said:
Hey I am trying to install BCR - Module module from github " https://github.com/chenxiaolong/BCR " but I am unable to install it in magisk. It is throwing the same error . Can you help me with that ? Thanks in advance
Click to expand...
Click to collapse
go to the Releases section on the right of the page with Version 1.29 and green latest to the right of it, scroll down to assets and click on BCR-1.29-release.zip to download the module...this WILL flash, or your money back...
....like my earlier post says, youre probably downloading the master or source code which wont work unless you unpack and repack it (and then sometimes not, if they havent actually compiled the apk if theres an apk component), if there is a Release section with active Releases, use that....
73sydney said:
go to the Releases section on the right of the page with Version 1.29 and green latest to the right of it, scroll down to assets and click on BCR-1.29-release.zip to download the module...this WILL flash, or your money back...
....like my earlier post says, youre probably downloading the master or source code which wont work unless you unpack and repack it (and then sometimes not, if they havent actually compiled the apk if theres an apk component), if there is a Release section with active Releases, use that....
Click to expand...
Click to collapse
You are an absolute hero, thank you so so much for this
73sydney said:
go to the Releases section on the right of the page with Version 1.29 and green latest to the right of it, scroll down to assets and click on BCR-1.29-release.zip to download the module...this WILL flash, or your money back...
....like my earlier post says, youre probably downloading the master or source code which wont work unless you unpack and repack it (and then sometimes not, if they havent actually compiled the apk if theres an apk component), if there is a Release section with active Releases, use that....
Click to expand...
Click to collapse
Bro what abt this it's having same issue is there any other way rather unzip and zip it again https://github.com/rithvikvibhu/nh-magisk-wifi-firmware
Related
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is oppo neo 7 android 5.1
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Didgeridoohan said:
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Click to expand...
Click to collapse
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
rajoholic said:
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
Click to expand...
Click to collapse
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Didgeridoohan said:
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Click to expand...
Click to collapse
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
I m also facing same problem
rajoholic said:
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is Micromax canvas nitro a310 current android version is cyanogen mode 13
Click to expand...
Click to collapse
rajoholic said:
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
Click to expand...
Click to collapse
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
sorry bout that. i just search the google free and temporary storage online. haha! thank you for the help. I'll try what u just said
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
rajoholic said:
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
Click to expand...
Click to collapse
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Didgeridoohan said:
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
rajoholic said:
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
Click to expand...
Click to collapse
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Didgeridoohan said:
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Click to expand...
Click to collapse
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
rajoholic said:
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
Click to expand...
Click to collapse
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Didgeridoohan said:
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Click to expand...
Click to collapse
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
rajoholic said:
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
Click to expand...
Click to collapse
Sir, did you manage to install? when i tried to install log is failed.
Hello, I need help installing and configuring Magisk on my tablet. Here is why and what I'm trying to do:
On my Samsung SM-T350, I originally installed TWRP and then installed a custom ROM which has root access (as far as I know, stock recovery is no longer on device). I recently installed a particular app and it indicates the program will not run all of the features because it has detected 'root' access. The suggestion online to work around this problem has been to install Magisk.
From this, I first went to the Magisk Manager website and download the 5.4.3apk and installed it. Then when I open the Magisk Manager app, it asks me if I want to 'Install Magisk-v14.0.zip now'. If I click 'install', a list of choices pop up (Download Zip Only, Patch Boot Image File, Direct Install). Which should I choose? I don't remember which of these I tried, but I recall it didn't work or didn't do anything.
So in the mean time, I downloaded the Magisk-v14.0.zip file locally to my tablet (Downloads folder). I 'think' the proper way to install is to boot into TWRP, then select 'Install', then navigate to the Magisk-v14.0.zip and then install image? Is that correct, or will this attempt to install over my custom ROM? What is the proper way to finish the installation?
Thanks in advance!
Does anyone have any suggestions?? Thanks
First - the "Magisk Manager website" is not a place you want to visit. It is not an official source for anything Magisk and should not be trusted. Only download from xda or @topjohnwu's GitHub.
Second - if you're already rooted you need to first unroot. Read more on installing Magisk in the release thread and the Installation and troubleshooting thread. Most, if not all your queries should be answered there.
Hello Everyone,
This is a collection of modules and a 1 flashable zip to enable aptX and aptx-HD on Oreo ROMs that doesn't have them...
the original files are taken from OnePlus OOS Oreo ROM, this should work (one of the options) on any OReo ROM, it may also work on N Roms but that's is not tested.
all modules flash the lib files to different places (or to all places), please the options, and select what is appropriate to you.
Bug reporting.
if you're going to report any issue please attach a log (the log should be taken before enabling Bluetooth and should record it being enabled and then being connected to an aptX enabled device)
Updated on January 6th 2018:
- 3 Magisk Modules added Description bellow for each.
- all 3 modules are based on the latest 1500 (15.0) Magisk template.
- APTX-enabler.zip is not a Magisk Module it's a recovery flashable zip, Description bellow.
should Works On All Oreo Roms.
Requirement:
-Root
-Root file manager
-Recovery (TWRP) for flashable Zip
A- Manual Installation:
1- download & extract the zip attached. ( APTX-enabler)
2- copy the files from System/vendor/lib64 folder to same place on your device, 0644 permission to both.
2- copy the files from System/lib and System/lib64/ folders to same place on your device, 0644 permission to both.
3- open build.prob in a text editor (or through the file manager) and add the following line at the end of it.
Code:
persist.bt.enableAptXHD=true
persist.service.btui.use_aptx=1
persistent.bt.a2dp_offload_cap=sbc-aptx-aptXHD
5- reboot
B- Flashable Zip Installation
1- reboot to TWRP
2- flash APTX-enabler.zip
3- reboot
C-Magisk Module
1- Download one of the 3 modules (discretion bellow)
2- install through Magisk manager
3- reboot
Modules Description:
A- aptX-HD_OreoEnablerOOS.zip , add the lib files only to System/vendor/lib64/ , some Roms like OOS Oreo Roms only require that for aptX to be enabled, it's not only for OOS other Roms use that too, if you don't know Use option C.
B- aptX-HD_OreoEnabler2.zip , add the lib files to system/lib and system/lib64 only... some roms like Nitrogen doesn't require to add any Libs on the vender folder, if not sure also use Option C.
C- aptX-HD_OreoEnabler.zip, this will add the lib files to ALL possible places, insuring that no matter what ROM you have aptX works...if you don't know which folder your ROM uses either ask the Rom Dev or use this option.
Old lib Files and modules can still be found on the following folder
https://drive.google.com/open?id=1aJQiFlzFgQmDJb08QZ_NMLUc0eKqBPry
Credits to
@Riku Azhurlar for initial flashable zip
@simonsmh for the Initial Magisk Module
@bmg1001 & @ossito2012 for initial aptx files
OnePlus for Current aptX lib files
theduke7 said:
Hello Everyone,
This is a collection of modules and a 1 flashable zip to enable aptX and aptx-HD on Oreo ROMs that doesn't have them...
the original files are taken from OnePlus OOS Oreo ROM, this should work (one of the options) on any OReo ROM, it may also work on N Roms but that's is not tested.
all modules flash the lib files to different places (or to all places), please the options, and select what is appropriate to you.
Bug reporting.
if you're going to report any issue please attach a log (the log should be taken before enabling Bluetooth and should record it being enabled and then being connected to an aptX enabled device)
Updated on January 6th 2018:
- 3 Magisk Modules added Description bellow for each.
- all 3 modules are based on the latest 1500 (15.0) Magisk template.
- APTX-enabler.zip is not a Magisk Module it's a recovery flashable zip, Description bellow.
should Works On All Oreo Roms.
Requirement:
-Root
-Root file manager
-Recovery (TWRP) for flashable Zip
A- Manual Installation:
1- download & extract the zip attached. ( APTX-enabler)
2- copy the files from System/vendor/lib64 folder to same place on your device, 0644 permission to both.
2- copy the files from System/lib and System/lib64/ folders to same place on your device, 0644 permission to both.
3- open build.prob in a text editor (or through the file manager) and add the following line at the end of it.
5- reboot
B- Flashable Zip Installation
1- reboot to TWRP
2- flash APTX-enabler.zip
3- reboot
C-Magisk Module
1- Download one of the 3 modules (discretion bellow)
2- install through Magisk manager
3- reboot
Modules Description:
A- aptX-HD_OreoEnablerOOS.zip , add the lib files only to System/vendor/lib64/ , some Roms like OOS Oreo Roms only require that for aptX to be enabled, it's not only for OOS other Roms use that too, if you don't know Use option C.
B- aptX-HD_OreoEnabler2.zip , add the lib files to system/lib and system/lib64 only... some roms like Nitrogen doesn't require to add any Libs on the vender folder, if not sure also use Option C.
C- aptX-HD_OreoEnabler.zip, this will add the lib files to ALL possible places, insuring that no matter what ROM you have aptX works...if you don't know which folder your ROM uses either ask the Rom Dev or use this option.
Old lib Files and modules can still be found on the following folder
https://drive.google.com/open?id=1aJQiFlzFgQmDJb08QZ_NMLUc0eKqBPry
Credits to
@Riku Azhurlar for initial flashable zip
@simonsmh for the Initial Magisk Module
@bmg1001 & @ossito2012 for initial aptx files
OnePlus for Current aptX lib files
Click to expand...
Click to collapse
No problem mate. We're you able to fix my installer with the new lib files okay? Or do you need me to touch up on itt
Riku Azhurlar said:
No problem mate. We're you able to fix my installer with the new lib files okay? Or do you need me to touch up on itt
Click to expand...
Click to collapse
to be honest mate i just updated the libs and permission, i personally use the module and they work, but the flashable file was reported by several people on my other thread on OP3 forums to be working... i wouldn't mind if you took a little look at the script
I have the nexus 6p with nitrogen 8.1 wich one Can not do without to use;;;;
Στάλθηκε από το Nexus 6P μου χρησιμοποιώντας Tapatalk
theduke7 said:
to be honest mate i just updated the libs and permission, i personally use the module and they work, but the flashable file was reported by several people on my other thread on OP3 forums to be working... i wouldn't mind if you took a little look at the script
Click to expand...
Click to collapse
instead of doing resetprop just put the props in system.prop file
theduke7 said:
to be honest mate i just updated the libs and permission, i personally use the module and they work, but the flashable file was reported by several people on my other thread on OP3 forums to be working... i wouldn't mind if you took a little look at the script
Click to expand...
Click to collapse
Apart from what @JohnFawkes mentions above, you also need to configure the config.sh file to actually run the post-fs-data.sh script (POSTFSDATA=true) or the system.prop file if you decide to use that (PROPFILE=true).
Also, since you're providing these files for manual install you should remove the placeholder file from /system. This file may cause bootloops since some devices can't take adding new files or folder directly to the root of /system.
JohnFawkes said:
instead of doing resetprop just put the props in system.prop file
Click to expand...
Click to collapse
Didgeridoohan said:
Apart from what @JohnFawkes mentions above, you also need to configure the config.sh file to actually run the post-fs-data.sh script (POSTFSDATA=true) or the system.prop file if you decide to use that (PROPFILE=true).
Also, since you're providing these files for manual install you should remove the placeholder file from /system. This file may cause bootloops since some devices can't take adding new files or folder directly to the root of /system.
Click to expand...
Click to collapse
I used to have the flags in as described but the new OOS update responds only to the post-fs-data.sh, I forgot to enable it and remove the place holder file... I will remedy that and update them
Modules updated according to above suggestions.
matrixios01 said:
I have the nexus 6p with nitrogen 8.1 wich one Can not do without to use;;;;
Στάλθηκε από το Nexus 6P μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
it depends on your rom, you can ask your rom dev which folder to place the lib files at at download the one corresponding to that... the aptX-HD_OreoEnabler.zip file should work for all roms cause it adds the libs to all possible places, but at least in my opinion this should be the last thing to try,
If Nitrogen in Nexus works the same way it does on OP3 the file aptX-HD_OreoEnabler2.zip should work for you...
theduke7 said:
to be honest mate i just updated the libs and permission, i personally use the module and they work, but the flashable file was reported by several people on my other thread on OP3 forums to be working... i wouldn't mind if you took a little look at the script
Click to expand...
Click to collapse
Sure I'll take a look here in a few when I get home. Also I didn't keep up on it. Did the magisk modules get updated to the newer template for magisk 15? Never know if the magisk dev will enforce it eventually if not I can do that too I've got nothing else to do lol
Riku Azhurlar said:
Sure I'll take a look here in a few when I get home. Also I didn't keep up on it. Did the magisk modules get updated to the newer template for magisk 15? Never know if the magisk dev will enforce it eventually if not I can do that too I've got nothing else to do lol
Click to expand...
Click to collapse
yes my friend it's updated to 15 template, i had it on the older template on the other thread on OP3 forums, but decided to download and update to the new one when creating this thread.
theduke7 said:
yes my friend it's updated to 15 template, i had it on the older template on the other thread on OP3 forums, but decided to download and update to the new one when creating this thread.
Click to expand...
Click to collapse
Cool just checking my luck always seems to be they release new templates and then stop allowing them eventually.
Does the manual install work without Magisk? I have an S8+ with locked bootloader (no custom recovery), but rooted, so was just wondering.
Thanks for the module.
I installed Magisk module type c but the codecs were not enabled.
logcat said I have aptx and aptx hd in local capability but not in selectable capability.. only SBC and AAC there.
My phone is Essential ph-1 and I found another module in ph-1 forom but it is basically same.
I thought I need special codec config file but nothing contained a sort of config.
EDIT: nvm, my device just does not support aptX, so tried another one and it worked!
Could this work on any Oreo smartphone? For example on a Honor 9 running RR-OS Oreo? I read that the CPU was not compatible with Apt-X.
fl0wfr said:
Could this work on any Oreo smartphone? For example on a Honor 9 running RR-OS Oreo? I read that the CPU was not compatible with Apt-X.
Click to expand...
Click to collapse
If the CPU isn't compatible... why are all the AptX libs in their place in stock rom? (At least in EMUI 8)
Thanks for the hard work on this port. Wasn't able to get the Magisk module working on Magisk 16. But was able to get the standalone systemless flash package working just fine on a LineageOS 15.1 port to my Nexus 5 which has been really awesome.
Just installed via Magisk and says enabled, but when I go to developer options under Bluetooth it still only says Aptx, i had this before. How do I know if aptx-hd is enabled?
OGNinjaDon said:
Just installed via Magisk and says enabled, but when I go to developer options under Bluetooth it still only says Aptx, i had this before. How do I know if aptx-hd is enabled?
Click to expand...
Click to collapse
Your device support the aptx-hd codec?
Dev can you include compatibility with AML?
Does nexus 6p only support Aptx? Because I tried to enable the other Aptx HD codec and not active. Only Aptx.
Hi,
this module installs OxygenOS 4.7+ (what I know is which from 4.7.0 to 5.0.3 it's the same) Bootanimation systemlessly.
Instructions:
- Download the .zip file with your phone
- Flash the downloaded .zip in Modules section in Magisk Manager
- Reboot your phone twice (in my case, the first time I got Liquid Remix Oreo Bootanimation, which my OnePlus 5T runs :silly
Credits:
@dabistduja wich provided to me OOS Bootanimation
I got a bootloop. The animation worked just fine, but at some point it freezes and my phone reboots itself. I've removed all files from this module, according to this guide, but for some reason I'm still getting the animation and the bootloop. Any ideas?
EDIT: I figured it out. I had to remove /cache/magisk_mount/system/media/bootanimation.zip as well.
I didn't find anything relevant in the logs so I won't even bother to post it here. It's also worth mentioning that my phone is encrypted, and it seems to me that the freezing/reboot happens right before I'm about to see that screen prompting for my password.
@alessio89g May I come with a few of suggestions?
First, since you're copying the animation zip to /cache you don't really need to mount it to /system. You could keep the zip in the common folder, of the zip, copy it to the module folder during installation, and then copy it from there.
Second, since you're copying the zip to a place that isn't affected by the installed module, also place a script in post-fs-data.d or service.d (service.d is preferred, but might not be possible depending on the rest of the setup) that can delete the zip and itself if the module has been uninstalled. If you don't do this, the animation zip has to be manually removed when they module had been uninstalled.
Third, you can avoid the second reboot when installing the module if you also run the copy to /cache command during installation.
Edit: @robotsrules Thank you. I'll update that part of the guide with info about removing other files that might be placed by modules.
Didgeridoohan said:
@alessio89g May I come with a few of suggestions?
First, since you're copying the animation zip to /cache you don't really need to mount it to /system. You could keep the zip in the common folder, of the zip, copy it to the module folder during installation, and then copy it from there.
Second, since you're copying the zip to a place that isn't affected by the installed module, also place a script in post-fs-data.d or service.d (service.d is preferred, but might not be possible depending on the rest of the setup) that can delete the zip and itself if the module has been uninstalled. If you don't do this, the animation zip has to be manually removed when they module had been uninstalled.
Third, you can avoid the second reboot when installing the module if you also run the copy to /cache command during installation.
Edit: @robotsrules Thank you. I'll update that part of the guide with info about removing other files that might be placed by modules.
Click to expand...
Click to collapse
Thanks for your suggestions, but I think I understood half of what you said, a bit 'because of my bad English, and a little' because I'm not a Magisk script expert.
If you want to edit and improve the module, you're welcome.
Hi,
I need a simple module that only replace a file on /system with Magisk 24.3 and Zigisk.
I'm not a dev and I tried myself with no success by following the instructions: https://topjohnwu.github.io/Magisk/guides.html.
Is someone can do it please !!
nabsboss said:
Hi,
I need a simple module that only replace a file on /system with Magisk 24.3 and Zigisk.
I'm not a dev and I tried myself with no success by following the instructions: https://topjohnwu.github.io/Magisk/guides.html.
Is someone can do it please !!
Click to expand...
Click to collapse
I would recommend using MMT-Extended (Magisk Module Extended), for one thing its a complete template....
GitHub - Zackptg5/MMT-Extended: Magisk Module Template Extended
Magisk Module Template Extended. Contribute to Zackptg5/MMT-Extended development by creating an account on GitHub.
github.com
1) Download the zip by clicking on the Code button, then download zip and extract the MMT-Extended-master folde inside the zip, and then rename it as you wish for your module
2) Read this guide, prolly easier to understand than the official TJW info for a beginner
For a simple /system file replacement module, steps 1,2,3,4,8, should be all you need to do, and then zip (must be zip, not RAR or 7z) up the folder and test
When you have at least tried following the guide, and if you fail, then come back with what you have tried (with a LOT more detail on what youre trying to achieve) and someone will help you.
There is no "create a module for me" service on XDA, you must be willing to at least try first....