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.
Related
If you enable or update an Xposed module and get stuck in a boot-loop, your options are limited. You basically just have access to recovery. I got stuck in this situation and had trouble finding out how to disable Xposed via recovery.
To disable Xposed completely from recovery,
Boot into custom recovery
Go to File Manager (usually under Advanced)
Navigate to /data/data/de.robv.android.xposed.installer/conf/modules.list
Delete modules.list
Reboot System
The deleted file simply controls which Xposed modules are loaded on startup. Deleting the file disables all Xposed modules.
After you reboot, all of your Xposed tweaks will be disabled. To re-enable Xposed modules, simply start up the Xposed Installer app. Then go to modules and make any change. This will re-create the modules.list file that you deleted in recovery.
There might be quite a lot of people who already know but this is for the benefit of those who don't know and end up wiping data and flashing everything from scratch.
A sensible flasher would download the xposed remover zip that's in the same op before installing.
@HKZync You save my all efforts. Great help bro. n my note 5 I had the issue and your trick worked.
---------- Post added at 09:36 AM ---------- Previous post was at 09:34 AM ----------
RJTBVK said:
A sensible flasher would download the xposed remover zip that's in the same op before installing.
Click to expand...
Click to collapse
You are suggesting to remove complete xposed framework instead of just disabling and enabling modules.
Thanks. Been having trouble with this just now. I used to have to flash the uninstaller and stuff. Big time saver this is
Sent from my Samsung Galaxy S4 using XDA Labs
thanks, exactly the infos i've been serching for.
Recovered from bootloop!
Thank you. The information provided here saved me.
You saved my life Bro!!!
It worked like a charm.
May God bless you.
HKZync said:
If you enable or update an Xposed module and get stuck in a boot-loop, your options are limited. You basically just have access to recovery. I got stuck in this situation and had trouble finding out how to disable Xposed via recovery.
To disable Xposed completely from recovery,
Boot into custom recovery
Go to File Manager (usually under Advanced)
Navigate to /data/data/de.robv.android.xposed.installer/conf/modules.list
Delete modules.list
Reboot System
The deleted file simply controls which Xposed modules are loaded on startup. Deleting the file disables all Xposed modules.
After you reboot, all of your Xposed tweaks will be disabled. To re-enable Xposed modules, simply start up the Xposed Installer app. Then go to modules and make any change. This will re-create the modules.list file that you deleted in recovery.
There might be quite a lot of people who already know but this is for the benefit of those who don't know and end up wiping data and flashing everything from scratch.
Click to expand...
Click to collapse
This doesn't work for me. I go to advanced, then file manager, then to the data folder, but then my only option is "up a level". I can't select more folders within the data folder.
This is not a problem when navigating on the sd card, only when navigating on the root of the phone.
seventieslord said:
This doesn't work for me. I go to advanced, then file manager, then to the data folder, but then my only option is "up a level". I can't select more folders within the data folder.
This is not a problem when navigating on the sd card, only when navigating on the root of the phone.
Click to expand...
Click to collapse
Is the data partition mounted (select it under "Mount")?
RJTBVK said:
A sensible flasher would download the xposed remover zip that's in the same op before installing.
Click to expand...
Click to collapse
right, but what if u cant flash with the recovery....
I got stuck too, so uninstalled xposed.
Now, when I look in xposed, I cannot disable the modules (because they all say they need an updates XposedBridge). The checkboxes are disabled, so I cannot remove a specific module to test if that module was the culprit.
How can I disable some xposed modules, then reinstall xposed?
Found this, am trying atm: https://forum.xda-developers.com/xposed/xposed-modules-desactivator-t3372942
This one actually works. It keeps the xposed framework, but removes all checkmarks for the modules, that way the modules are not loaded on boot.
Great job thanks,??
HKZync said:
If you enable or update an Xposed module and get stuck in a boot-loop, your options are limited. You basically just have access to recovery. I got stuck in this situation and had trouble finding out how to disable Xposed via recovery.
To disable Xposed completely from recovery,
Boot into custom recovery
Go to File Manager (usually under Advanced)
Navigate to /data/data/de.robv.android.xposed.installer/conf/modules.list
Delete modules.list
Reboot System
The deleted file simply controls which Xposed modules are loaded on startup. Deleting the file disables all Xposed modules.
After you reboot, all of your Xposed tweaks will be disabled. To re-enable Xposed modules, simply start up the Xposed Installer app. Then go to modules and make any change. This will re-create the modules.list file that you deleted in recovery.
There might be quite a lot of people who already know but this is for the benefit of those who don't know and end up wiping data and flashing everything from scratch.
Click to expand...
Click to collapse
You saved my day, very helpful tip.
Thanks.
Best regards
mkpcxxl
is this still working for 7.1 rovo magisk xposed ?? v88.1 ??
Good to know for when I ever get in a bootloop, only problem is there's no conf folder to be found lol..
I do have a shared_prefs folder with some files in it though.. So should I delete one of these files when I ever get in a bootloop?
Noisecake said:
Good to know for when I ever get in a bootloop, only problem is there's no conf folder to be found lol..
I do have a shared_prefs folder with some files in it though.. So should I delete one of these files when I ever get in a bootloop?
Click to expand...
Click to collapse
Enabled_modules.xml
Btw. it's much easier to press 5x hardware key during boot than manipulating files via recovery.
Thank you so much! ♥
HKZync said:
If you enable or update an Xposed module and get stuck in a boot-loop, your options are limited. You basically just have access to recovery. I got stuck in this situation and had trouble finding out how to disable Xposed via recovery.
To disable Xposed completely from recovery,
Boot into custom recovery
Go to File Manager (usually under Advanced)
Navigate to /data/data/de.robv.android.xposed.installer/conf/modules.list
Delete modules.list
Reboot System
The deleted file simply controls which Xposed modules are loaded on startup. Deleting the file disables all Xposed modules.
After you reboot, all of your Xposed tweaks will be disabled. To re-enable Xposed modules, simply start up the Xposed Installer app. Then go to modules and make any change. This will re-create the modules.list file that you deleted in recovery.
There might be quite a lot of people who already know but this is for the benefit of those who don't know and end up wiping data and flashing everything from scratch.
Click to expand...
Click to collapse
Made an account just to thank you! Saved me from having to flash my phone!
HELP! Nothing is in that file and still stuck in bootloop
Does anyone know how to disable/ uninstall a specific xposed module via recovery?
The AROMA package in question is this one. I've posted a couple of times in that thread, but it appears the developer has abandoned it, and I'd like to take up repackaging the installer (which modifies /system), into a Magisk module. Has anyone got any idea how I can go about doing it, preferably with 'options' attached, i.e. users can choose which apps/widgets they would like installed.
Scramjet said:
The AROMA package in question is this one. I've posted a couple of times in that thread, but it appears the developer has abandoned it, and I'd like to take up repackaging the installer (which modifies /system), into a Magisk module. Has anyone got any idea how I can go about doing it, preferably with 'options' attached, i.e. users can choose which apps/widgets they would like installed.
Click to expand...
Click to collapse
For me its just impossible to "convert an AROMA Installer into a Magisk Module", Magisk is an "system", AROMA Installer is an custom recovery feature. The first thing is for the android system, the second is for an custom recovery.
The second problem: you cannot implementing an "select menu" in an Magisk module that would managing the Magisk stuff.
Rom said:
For me its just impossible to "convert an AROMA Installer into a Magisk Module", Magisk is an "system", AROMA Installer is an custom recovery feature. The first thing is for the android system, the second is for an custom recovery.
Click to expand...
Click to collapse
What I meant is for the payload in the installer, to be converted into a Magisk module. They both serve a similar purpose: to add/change/replace/remove files from the filesystem. One does it directly, the other, 'systemlessly'.
Rom said:
The second problem: you cannot implementing an "select menu" in an Magisk module that would managing the Magisk stuff.
Click to expand...
Click to collapse
That's OK. What if we know exactly what to select in the Aroma installer, and then create the Magisk module based on just that?
Scramjet said:
What I meant is for the payload in the installer, to be converted into a Magisk module. They both serve a similar purpose: to add/change/replace/remove files from the filesystem. One does it directly, the other, 'systemlessly'.
That's OK. What if we know exactly what to select in the Aroma installer, and then create the Magisk module based on just that?
Click to expand...
Click to collapse
I haven't got more knowledges in that to answer u about your question, maybe another devs could help u..sorry
Scramjet said:
The AROMA package in question is this one. I've posted a couple of times in that thread, but it appears the developer has abandoned it, and I'd like to take up repackaging the installer (which modifies /system), into a Magisk module. Has anyone got any idea how I can go about doing it, preferably with 'options' attached, i.e. users can choose which apps/widgets they would like installed.
Click to expand...
Click to collapse
** shameless advertising
Try this module template
https://forum.xda-developers.com/apps/magisk/module-template-magisk-module-template-t3620235
It can install both in /system and magisk. And I can also guide you with putting options in the installer (in shell)
Scramjet said:
The AROMA package in question is this one. I've posted a couple of times in that thread, but it appears the developer has abandoned it, and I'd like to take up repackaging the installer (which modifies /system), into a Magisk module. Has anyone got any idea how I can go about doing it, preferably with 'options' attached, i.e. users can choose which apps/widgets they would like installed.
Click to expand...
Click to collapse
I have one that works great for me. What I did was remove the installtheme.sh type run _programs from updater_script for all the mods. Instead the "installs" collected in a magisk module. After all was installed that was wanted I had one install that you chose that zipped the magisk template module to the sdcard. After the Aroma finished, in TWRP you hit the back button. Go to install, find that zip and flash it. I used the evilvrtheme magisk template.
It's going to take some time for you, you have to make a module for each option.
One module for HMS_Gallery_GP2 another one for HMS_Music_GP and so on.
Then delete apk from that Aroma Installer and put your modules there. Last step is to modify updater-script to flash relative module for each option instead of extracting apks into /system partition
Here is an exert from my updater-script. The first one is the module zip maker. The other two are examples of the mods bring installed. The second thing being extracted is the magisk config.sh. i have these in separate folders in my Aroma, one for each configuration I have. My default is empty of system installs since my mods are almost entirely vrtheme mods. This is the one sticky area because the wrong config.sh file can cause problems. I only have a few that need system installs. If you default to empty, the worst thing that can happen is the system mod doesn't install. The alternative is a messed up phone.
Scramjet said:
What I meant is for the payload in the installer, to be converted into a Magisk module. They both serve a similar purpose: to add/change/replace/remove files from the filesystem. One does it directly, the other, 'systemlessly'.
That's OK. What if we know exactly what to select in the Aroma installer, and then create the Magisk module based on just that?
Click to expand...
Click to collapse
Did you ever get your Aroma installer going?
Tulsadiver said:
Did you ever get your Aroma installer going?
Click to expand...
Click to collapse
No, I haven't really worked on it yet. Got sidetracked by life—I'm planning on trying to get it to work this weekend, but no promises.
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
zdimension said:
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
Click to expand...
Click to collapse
Use mount-magisk.zip found in collection of modules thread and delete the folder via twrp in /magisk
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
zdimension said:
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
Click to expand...
Click to collapse
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
gonsa said:
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
Click to expand...
Click to collapse
Start reading the thread from the beginning and you'll find it.
gonsa said:
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
Click to expand...
Click to collapse
Install "Uninstaller Mod Magisk" from TWRP. Then go in the TWRP terminal and type uninmod_magisk and follow the instructions.
please post the link to thread unistaller magisk module, to other users follow the solution!
edit:
there is https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
nodio said:
please post the link to thread unistaller magisk module, to other users follow the solution!
edit:
there is https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Click to expand...
Click to collapse
Not working for me!
I will uninstall "Audio Compatibility Patch" V1.0 from zackptg5 & ahrion
In Magisk Manger Status is always " Module will be updated at the next start"
If i use the "TWRP-Uninstaller" the Modul is not in List!
dewois said:
Not working for me!
I will uninstall "Audio Compatibility Pach" V1.0 from zackptg5 & ahrion
In Magisk Manger Status is always " Module will be updated at the next start"
If i use the "TWRP-Uninstaller" the Modul is not in List!
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
".... Go the module folder under /sbin/.core/img ..."
I dont have this folder in /sbin!
tobi14 said:
".... Go the module folder under /sbin/.core/img ..."
I dont have this folder in /sbin!
Click to expand...
Click to collapse
If you have a current version of Magisk installed, yes you do. Enable viewing hidden files and folders in your file explorer. The dot at the beginning of the folder name means it's hidden...
zdimension said:
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
Click to expand...
Click to collapse
If you can launch TWRP then :
Check magisk.img exist
1. Go to "advanced" and then click on "File Explorer".
2. Check there is "magisk.img" file under "/data"
Backup magisk.img
1. Go to "advanced" and then click on "terminal command".
2. type following command
Code:
cp /data/magisk.img /data/magisk.img.bk
Mount magisk.img
1. Make a temp folder
Code:
mkdir /mktmp
2. Mount magisk.img to /mktmp
Code:
mount -o loop /data/magisk.img /mktmp
3. Navigate to mktmp and remove your module
Code:
cd /mktmp
rm -rf /mktmp/xxxx
Unmount magisk.img and reboot to check if it's work
1. Unmount magisk.img
Code:
umont /mktmp
2. Leave terminal and reboot the phone
3. Enjoy!
mklee11224 said:
If you can launch TWRP then :
Check magisk.img exist
1. Go to "advanced" and then click on "File Explorer".
2. Check there is "magisk.img" file under "/data"
Backup magisk.img
1. Go to "advanced" and then click on "terminal command".
2. type following command
Code:
cp /data/magisk.img /data/magisk.img.bk
Mount magisk.img
1. Make a temp folder
Code:
mkdir /mktmp
2. Mount magisk.img to /mktmp
Code:
mount -o loop /data/magisk.img /mktmp
3. Navigate to mktmp and remove your module
Code:
cd /mktmp
rm -rf /mktmp/xxxx
Unmount magisk.img and reboot to check if it's work
1. Unmount magisk.img
Code:
umont /mktmp
2. Leave terminal and reboot the phone
3. Enjoy!
Click to expand...
Click to collapse
Thanks mate ! it worked like a charm !
just use "ls" command on step 3 after changing directory to mktmp , to show installed modules.:silly:
My Phone Specification : Moto X Play ------ 7.1.1 Stock Firmware -------- Squid kernel --------- rooted using Magisk ------ systemless xposed module "xposed_25" installed using magisk module(Uninstalled by this method !) .:victory:
Tanks a lot!
Crossbreeder lite made my phone unusable. Working fine again!
magisk.img not found in /data
This works like charm, if you can't find the magisk.img in `/data` check `/data/adb` ... I hope this work .
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
Own domain huh? Business growing? Hehehe I only came for the uninstall zip, hey quick question, I'm on a micro sd-less phone (big news), still a flashaholic, kinda, but my phone so happens to require a data format every time for gsi's, where would you recommend keeping the "things to keep on your device" (Magisk related) so i don't have to carry an otg and drive everywhere i go? Thank you sir, you almost get more thanks than posts! Talk about reputation!
culiacanazo said:
Own domain huh?
Click to expand...
Click to collapse
I keep a few of them around. It was nice to finally find a good use for that one...
but my phone so happens to require a data format every time for gsi's, where would you recommend keeping the "things to keep on your device" (Magisk related) so i don't have to carry an otg and drive everywhere i go?
Click to expand...
Click to collapse
Do you have to completely wipe the device? Or can you keep internal storage intact? If not, it sounds like you're out of luck.
Nice thread hijack, by the way... :laugh:
Didgeridoohan said:
Do you have to completely wipe the device?
Click to expand...
Click to collapse
Well i do a factory reset, flash system img and reboot, let it loop because it will, and then do a data format before it will boot, so system, caches, and data go... (Huawei, see)
Didgeridoohan said:
Nice thread hijack, by the way... :laugh:
Click to expand...
Click to collapse
I kinda stayed on topic didn't i? :crying:
You linked to your help guide which i read the beginning of that by the way has nothing to do with the help you offered to the op and reminded me of my struggles with a totally different device and problem!!
It's like how I'm related to my grandma's cousin's wife's sister's doctor's neighbor's son's friend, ain't it?
Sent from my Huawei Mate 10 Pro using XDA Labs
Would be cool if someone could share the adb solution. In the FAQ is just written "email me for this" wtf?!? It is ****ing anoying to reflash the whole system everytime a module isnt working (yeah thats what you need to do if your device doesnt have twrp, and a lot of a/b devices dont have twrp). Also you need to delete all user datas because you flashed the system new and the new system doesnt know the encryption key for the user datas. There need to be a better solution than using twrp or email the dev for adb solution.
The easiest way would be to make it possible that magisk manager can manage (remove/deactivate) the modules while there is no patched boot.img installed. This would solve all problems related to a/b devices without twrp and magisk modules (not booting or anything else) just flash stock boot.img remove the problematic module flash patched boot.img and done. This is not possible because the module section in magisk manager is hidden when there is no patched boot.img installed.
Second thing i noticed, magisk manager doesnt reset the active modules when you wipe the app data. This should be a MUST. Would also solve the problem of not booting modules without wiping the whole system on a/b devices without twrp.
Apply .disable_magisk
saturday_night said:
Would be cool if someone could share the adb solution. In the FAQ is just written "email me for this" wtf?!? It is ****ing anoying to reflash the whole system everytime a module isnt working (yeah thats what you need to do if your device doesnt have twrp, and a lot of a/b devices dont have twrp). Also you need to delete all user datas because you flashed the system new and the new system doesnt know the encryption key for the user datas. There need to be a better solution than using twrp or email the dev for adb solution.
The easiest way would be to make it possible that magisk manager can manage (remove/deactivate) the modules while there is no patched boot.img installed. This would solve all problems related to a/b devices without twrp and magisk modules (not booting or anything else) just flash stock boot.img remove the problematic module flash patched boot.img and done. This is not possible because the module section in magisk manager is hidden when there is no patched boot.img installed.
Second thing i noticed, magisk manager doesnt reset the active modules when you wipe the app data. This should be a MUST. Would also solve the problem of not booting modules without wiping the whole system on a/b devices without twrp.
Click to expand...
Click to collapse
Hi!. I have this user of XDA Dev. hanging out for a time... well the fact is I'm new. My problem (not the only one) maybe merge a kind of solution to this. And this could be putting the ".disable_magisk" blank file inside the cache partition as an ADB Sideload update.
Next to this. I've found that to do that it's not as simply as it seems to be cause I'm on a Samsung Galaxy S7 Nougat 7.0 Version. And all the examples with update-binary file I have, are from downgrade versions...
I'm stuck in a bootloop due to the Magisk Xposed SDK 24 module. I think this module & encription is not good (as I've read on the Xpose module thread).
So, here I'm asking how to make an script to run directly on the Stock recovery using ADB Sideload, which will put the blank ".disable_magisk" file inside the /cache partition. I need just this, and I think this could help some people who are stuck on this issue.
Now, I have this Thread. But really I need the advice of an expert telling me what to do in order to achieve this. As I think this is an easy labor, but you have to know how to do it... If someone is able to clarify please, I will appreciate so much.
Thanks!
---------- Post added at 05:51 PM ---------- Previous post was at 05:41 PM ----------
neromanello said:
Hi!. I have this user of XDA Dev. hanging out for a time... well the fact is I'm new. My problem (not the only one) maybe merge a kind of solution to this. And this could be putting the ".disable_magisk" blank file inside the cache partition as an ADB Sideload update.
Next to this. I've found that to do that it's not as simply as it seems to be cause I'm on a Samsung Galaxy S7 Nougat 7.0 Version. And all the examples with update-binary file I have, are from downgrade versions...
I'm stuck in a bootloop due to the Magisk Xposed SDK 24 module. I think this module & encription is not good (as I've read on the Xpose module thread).
So, here I'm asking how to make an script to run directly on the Stock recovery using ADB Sideload, which will put the blank ".disable_magisk" file inside the /cache partition. I need just this, and I think this could help some people who are stuck on this issue.
Now, I have this Thread. But really I need the advice of an expert telling me what to do in order to achieve this. As I think this is an easy labor, but you have to know how to do it... If someone is able to clarify please, I will appreciate so much.
Thanks!
Click to expand...
Click to collapse
I need to know how to locate the mount point of my /cache partition at the stock recovery ADB Sideload. Then, to mount it, transfer the blank file to it, and then unmount /cache. I think it's an easy labor. So here my incomplete updater-script:
ui_print("Trying to make an script with ADB Sideload..."); CRLF
ui_print("Creating file to disable Magisk Modules..."); CRLF
I NEED THE MOUNT POINT HERE CRLF
ifelse package_extract_file(".disable_magisk", "/cache/.disable_magisk") == "t", ui_print("OK!"), ui_print("Failed!"); CRLF
UNMOUNT COMMAND HERE. CRLF
--last blank line--
So, I need to complete that, BUT things gets difficult when I need the update-binary for my Nougat 7.0 version, and to sign the whole .zip file in order my stock recovery recognizes it. I think this last thing could be made by this Thread. But really I don't know. Please help.
Thanks!.
I made the two modules attached in this post using the new module template, but after installing them, at the reboot the phone stuck on "pre-bootanimation screen" (Google logo).
The issues started when I updated Magisk v13.3 to v14, whit the same issue, but the modules used the previous template (they worked with Magisk v13.3). So, thinking the issue was caused by the template version, I updated them whit the newest, but nothing changed.
I also tried to install them one at time, without the other… same situation.
What's wrong?
Nexus 5, Screw'd ROM 7.1.2 with its Kernel, no other mods.
You have left the placeholder file in the system folder. That then get's Magic Mounted to /system, which didn't used to be an issue, but from v14.0 (and the betas v13.4-6) adding new files to the root of /system causes a bootloop. It's under investigation...
Remove those files from your zips and you should be good to go.
Thank you, now they work!
I think that "DeleteMe" could be a better filename for the placeholder file! ?
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