[HELP] This zip is not a Magisk Module - Magisk

Hi guys,
Just to be clear I have googled and searched xda for answers but I have come up empty.
I've tried to create a magisk module (attached) and I followed this guide:
https://topjohnwu.github.io/Magisk/guides.html
But somehow somewhere I messed up, because whenever I try to sideload it through Magisk Manager I get an error message saying:
This zip is not a Magisk Module
I've uploaded the Zip in some hope that someone can point out where I've gone wrong because I've got no clue.
The logic is quite simple, all I need done is the files I've placed in System to overwrite the existing ones in system.
- I don't need customize.sh
- I don't need any scripts run in boot (so no post-fs-data.sh or service.sh)
- I've overwritten update-binary with latest module_installer.sh
- I've triple checked that my module.prop is correct.
- README.md isn't a priority since I'm not planning on uploading this to the repo anyways.
I will be very grateful for any and all help!
Thank you all in advance.

The zip is simply broken (somehow). Try repackaging it, or using another program to create it.

Kyuubi10 said:
Hi guys,
Just to be clear I have googled and searched xda for answers but I have come up empty.
I've tried to create a magisk module (attached) and I followed this guide:
https://topjohnwu.github.io/Magisk/guides.html
But somehow somewhere I messed up, because whenever I try to sideload it through Magisk Manager I get an error message saying:
This zip is not a Magisk Module
I've uploaded the Zip in some hope that someone can point out where I've gone wrong because I've got no clue.
The logic is quite simple, all I need done is the files I've placed in System to overwrite the existing ones in system.
- I don't need customize.sh
- I don't need any scripts run in boot (so no post-fs-data.sh or service.sh)
- I've overwritten update-binary with latest module_installer.sh
- I've triple checked that my module.prop is correct.
- README.md isn't a priority since I'm not planning on uploading this to the repo anyways.
I will be very grateful for any and all help!
Thank you all in advance.
Click to expand...
Click to collapse
Possibly the line endings were messed up. Anyway, I just repackaged everything for you, and the install went through for me. Have a look at the attached zip.

Add an empty line under #MAGISK in updater-script.

shadowstep said:
Possibly the line endings were messed up. Anyway, I just repackaged everything for you, and the install went through for me. Have a look at the attached zip.
Click to expand...
Click to collapse
Thank you soo much!
This worked I'm so happy.
Interesting that the line endings were messed up, i was editing the scripts on a Chromebook, which I assumed would do Unix line endings.
Evidently not.
More googling for me
Thank you once again!

shadowstep said:
Possibly the line endings were messed up. Anyway, I just repackaged everything for you, and the install went through for me. Have a look at the attached zip.
Click to expand...
Click to collapse
I am also having the same problem, I made a module and the installation shows the same message "this is not a magisk module", would you like to see about it? That would help a lot
In fact how do I attach the file to my comment?

guitardedhero said:
Add an empty line under #MAGISK in updater-script.
Click to expand...
Click to collapse
This simple fix worked for me. Thanks!

hey guys,
i tried editing the updater-script but it seems that there's already an empty line. also, i've tried unzipping zipping the file that i wanted but it won't work. i want to install the
Bluetooth-HID-Enabler by lorebadtime but im having a trouble. any help?

Related

[MOD][TEMPLATE] Magisk Module Template with EvilTheme Patcher

Hello everyone.
This is a little mod to the Magisk Module Template that allows you to patch APK files on-the-fly and have them created as a Magisk Module.
For example, you could have a modified camera module for your ROM, where this patcher would replace the classes.dex file with mods, then pack that as a Magisk Module, using the original file found in the /system (ROM)
For some of the devs that have been around for a while, you would be aware of the old VRTheme modding system, which would allow you to patch files on-the-fly. EvilTheme is basically a newer version of that, so combined with Magisk can be very useful
Here's what this module CAN do:
Replace resources.arsc, classes.dex, AndroidManifest.xml, and META-INF folder
Replace compiled res folders / files
Here's what this module CAN'T do:
Replace files in res/values or smali folders
How to use EVilTheme
(Example using /system/priv-app/SecSettings2.apk)
In the eviltheme folder, go to system and make a folder called priv-app. Inside it, make another folder called SecSettings2.apk
Now make folders as necessary, according to the location of the files you want to theme. For example, battery_icon_50.png is located in res/drawable-hdpi, so make a folder named res inside SecSettings2.apk.
Inside it, create a folder named drawable-hdpi, then paste your new battery_icon_50.png inside.
Repeat step 2 until you've placed your theme files in their appropriate locations.
When you're done, go back to the root folder of the theme (the one that contains eviltheme, engine, etc.) and put all the objects in a ZIP file.
You should use Deflate compression with compression level on Normal, but if your theme is huge, you can safely try compressing using Deflate and the level set to Ultra or whatever high level is available.
Test your mod.
For information regarding the Magisk Module subbmision etc, please read the information HERE
Link to Github Repository: HERE
Enjoy
Nice! Sounds interesting!
I've been using vrtheme for years and even contacted spanna aabout adapting the script to achieve modding of live system files this eliminating the need for recovery zips and even Aroma!
So I have a question about the use and locations of the asset files.
Would it be possible to change, at least the location from which the files get pulled from and placed into the execute folders?
So basically could it be set to pull the image/resource, whatever file from either a data folder or my preference, sd storage?
I've used an asset folder built into my system for similar commands, but with enough options and large files the system partition can get extremely crowded.
Does my question make sense?
Basically i would like to eliminate a big section of my packed 2gb Aroma zip. About 700mb is all vrtheme injected compiled files.
Either way I will definitely be looking into this!
Thanks
stangdriver44 said:
Nice! Sounds interesting!
I've been using vrtheme for years and even contacted spanna aabout adapting the script to achieve modding of live system files this eliminating the need for recovery zips and even Aroma!
So I have a question about the use and locations of the asset files.
Would it be possible to change, at least the location from which the files get pulled from and placed into the execute folders?
So basically could it be set to pull the image/resource, whatever file from either a data folder or my preference, sd storage?
I've used an asset folder built into my system for similar commands, but with enough options and large files the system partition can get extremely crowded.
Does my question make sense?
Basically i would like to eliminate a big section of my packed 2gb Aroma zip. About 700mb is all vrtheme injected compiled files.
Either way I will definitely be looking into this!
Thanks
Click to expand...
Click to collapse
You could, but you would have to look at update-binary and installtheme.sh, then modify it for your needs. So instead of copying the modded files from the flashable zip, you would just have to remove the unzip function and change the path of where they are unzipped to to the location of where the files are on your data partition.
Give it a try
so with this I can technically change the rotation of an app without ever messing with the apk? I've tried editing the AndroidManifest.xml, but after editing I've never been successful putting it back into the apk
dimm0k said:
so with this I can technically change the rotation of an app without ever messing with the apk? I've tried editing the AndroidManifest.xml, but after editing I've never been successful putting it back into the apk
Click to expand...
Click to collapse
If you plan to change androidmanifest.xml you will have to include the newly created META-INF folder for it too.
Could this be used to convert substratum themes to work systemlessly with magisk?
Sent from my Pixel using XDA Labs
qwer777 said:
Could this be used to convert substratum themes to work systemlessly with magisk?
Sent from my Pixel using XDA Labs
Click to expand...
Click to collapse
If you're talking about pre-packaged APK theme files, no it probably won't work, as they still need to be installed.
This is more for files that are already installed that require patching.
Nice work
Got one question - is it possible to modify classes.dex if .apk file is not in system folder? I mean for example, if system app gets updated, it creates new folder in data/app/ with the name of the package and with either -1, -2 or whetever number at the end (ex. data/app/com.google.android.youtube-2).
Do I need to just integrate update into system and then modify it? Or just create new folder in eviltheme one with data/... instead of system/...?
Thanks
I tried to modify system/framework/framework-res.apk/res/drawable-xxhdpi-v4/default_wallpaper.jpg, but unfortunately it did not work. Neither on InFocus M808/mod stock 6.0(mt6753) nor on SamsungS5Neo/mod stock 6.0.1(exynos7580)
Both tried with official Magisk 12.0 and newest beta.
nevermind i didn't read all the way
drei.liter.milch said:
I tried to modify system/framework/framework-res.apk/res/drawable-xxhdpi-v4/default_wallpaper.jpg, but unfortunately it did not work. Neither on InFocus M808/mod stock 6.0(mt6753) nor on SamsungS5Neo/mod stock 6.0.1(exynos7580)
Both tried with official Magisk 12.0 and newest beta.
Click to expand...
Click to collapse
Started another try to replace some icons. did not work. am I missing something or is this template just faulty?
anybody who got this working?
drei.liter.milch said:
Started another try to replace some icons. did not work. am I missing something or is this template just crap?
anybody who got this working?
Click to expand...
Click to collapse
That was a bit rude.
Edit: better to give some details on what you've actually done, maybe even upload your files. Easier to find any faults on your side or possible bugs that way.
I want to add the clock onto my lockscreen statusbar. Would this help me achieve that?
Didgeridoohan said:
That was a bit rude.
Edit: better to give some details on what you've actually done, maybe even upload your files. Easier to find any faults on your side or possible bugs that way.
Click to expand...
Click to collapse
yes ok, the word "crap" maybe was a little bit over the top. i'm sorry for that. I just would like to know, if anybody can report this module/template as working. If so, I would go on looking for the error on my side.
I've actually followed exactly the guide given in OP. (It seems not that tricky to me)
-placed folder tree system/framework/framework-res.apk/res/drawable-xxhdpi-v4/ in the eviltheme-folder and put my default_wallpaper.jpg file in drawable-xxhdpi-v4 folder
-edited module.prop und config.sh
-zipped the whole template folder
-installed via magisk manager
-rebooted
tried with to different phones, beta and official magisk (see my first post)
I'll reproduce my logs and attach them later.
anyway thanks for the hint
drei.liter.milch said:
yes ok, the word "crap" maybe was a little bit over the top. i'm sorry for that. I just would like to know, if anybody can report this module/template as working. If so, I would go on looking for the error on my side.
I've actually followed exactly the guide given in OP. (It seems not that tricky to me)
-placed folder tree system/framework/framework-res.apk/res/drawable-xxhdpi-v4/ in the eviltheme-folder and put my default_wallpaper.jpg file in drawable-xxhdpi-v4 folder
-edited module.prop und config.sh
-zipped the whole template folder
-installed via magisk manager
-rebooted
tried with to different phones, beta and official magisk (see my first post)
I'll reproduce my logs and attach them later.
anyway thanks for the hint
Click to expand...
Click to collapse
Flash Via Recovery, it may work. didnt work for me when i installed from magisk manager.
btw i have a question, is there any way to remove a file from the apk?
shekhawat2 said:
Flash Via Recovery, it may work. didnt work for me when i installed from magisk manager.
btw i have a question, is there any way to remove a file from the apk?
Click to expand...
Click to collapse
thx, i'll try that. which magisk-version do you use? and i guess maybe you can remove a file by placing a dummy.
drei.liter.milch said:
thx, i'll try that. which magisk-version do you use? and i guess maybe you can remove a file by placing a dummy.
Click to expand...
Click to collapse
No brother, I want to delete the file, not to replace it with dummy file. Replacing with dummy file will give system ui FCs.
I saw something delete.list in the installtheme.sh, but I don't know how to use it. If anyone can help, pls help me.
BTW I am using Magisk v12.
shekhawat2 said:
No brother, I want to delete the file, not to replace it with dummy file. Replacing with dummy file will give system ui FCs.
I saw something delete.list in the installtheme.sh, but I don't know how to use it. If anyone can help, pls help me.
BTW I am using Magisk v12.
Click to expand...
Click to collapse
Ok, I see. Perhaps you find sth about it in the vrtheme-topic. Btw. flashing in recovery doesn't work either. I'm not messing around with this anymore and continue using flipster :good:
Where can we download? I want to change Viber's background to pure black so I will change the AndroidManifest. Will this theoretically work?
I was wondering what, if anything, I would need to change for this to work on a pixel. On Pixel's, the install path is system/system. I couldn't tell whether or not this could detect the correct path on its own.
Edit: Never mind. I got it to work.

[Module] Custom Systemless Boot Animation

Hello!
I had a lot of trouble making my phone show custom boot animation so I put together this. Hopefully I can help you set custom boot animation systemlessly.
Since Magisk 16.4, the boot animation can not be loaded from user data fs, this is the simplest method I'm aware of.
What do you need?
Magisk 18+
Android 5+
Custom bootanimation.zip
This repository (github.com/MCBlesk/Systemless-Boot-Animation)
Steps
Download the Github repository
Replace bootanimation.zip in /system/media/
Zip all files in the repository
Install with Magisk Manager
Not working?
Make sure your bootanimation.zip file is not compressed! (store compression)
Put an empty line after the last instruction in desc.txt
Make sure images are valid PNGs
Refer to googlesource (android.googlesource.com/platform/frameworks/base/+/master/cmds/bootanimation/FORMAT.md)
Try installing the module with provided bootanimation.zip. If it does work, your bootanimation.zip is most probably invalid. If it doesn't, the module probably doesn't work on your device.
Didn't help? Ask! I spent a lot of time messing things up and hopefully have some overview...
Sorry I have links in this format, I can't post external links yet...
Warning: If you don't replace the bootanimtion.zip, my stupid face will scare you every time you reboot the phone.
After zipping the repo, when I try to flash magisk says is not a valid module zip :S
eXtremeDevil said:
After zipping the repo, when I try to flash magisk says is not a valid module zip :S
Click to expand...
Click to collapse
Could you post the zip? Or send it to me, if you don't feel comfortable with sharing it publicly... I'll be happy to help.
Sure, I can post it here, but I can't just right now. I'll post soon
OK, now it flashses, but it doesn't work. The zip is attached.
Phone is OP2, latest Magisk, on Resurrection Remix 7.0.2 (Pie 9).
Thanks in advance.
The bootanimation.zip is being replaced, but it seems that not fast enough to apply on boot.
eXtremeDevil said:
The bootanimation.zip is being replaced, but it seems that not fast enough to apply on boot.
Click to expand...
Click to collapse
Hey again, sorry for the delay. There was a lot going on. I we looked into this on friend's OnePlus2 Lineage16 and everything worked.
I looked into Magic Mount and the boot process again and bootanim service is guaranteed to start AFTER post-fs-data (where Magisk replaces it).
If your /system/media folder doesn't contain bootanimation-encrypted.zip (which has a higher priority and I didn't work around it - not intentionally) I am not sure how to help you. Sorry.
Sorry for my late response as well. I really appreciate your efforts, but now I have a different phone and although I keep my old OP2, this issue is not worth it anymore.
Thanks again!

[HELP] This zip is not a Magisk Module! Simple System UI sound replacement

Hello, first post.
I've been looking for the better half of two days to figure this out and the only thing that comes close is a similar thread here:
https://forum.xda-developers.com/t/help-this-zip-is-not-a-magisk-module.4087019/
I tried creating a really simple module to replace a few System UI sounds, but I keep running into this error when installing. The resolution to the above thread was one of the mods repacked the OPs zip and it worked, and something about "Possibly the line endings were messed up."
Not sure what I have done wrong, I followed the guide at https://topjohnwu.github.io/Magisk/guides.html
I am not super tech savvy when it comes to actually creating stuff, Ive always been able to follow along other peoples instructions but I cant find anything to get this done.
Now android 11 doesn't allow mounting the system partition as RW I thought that I could do it with Magisk, but I'm at a loss of what to do now.
I have attached my module zip.
Any help would be massively appreciated! -PlutoniumRobot
You need to move the module contents to the root of the zip.
https://www.didgeridoohan.com/magisk/Magisk#hn_Zip_is_not_a_Magisk_module
Didgeridoohan said:
You need to move the module contents to the root of the zip.
https://www.didgeridoohan.com/magisk/Magisk#hn_Zip_is_not_a_Magisk_module
Click to expand...
Click to collapse
I believe the contents are at the root of the zip; meta-inf, module.prop, system. Am I missing something?
Not in the zip you have attached to the 1st post. They're in a folder named "Pixel Sounds" (and also doubled inside the "__MACOSX" folder), so you'll have to move them out from there...
Didgeridoohan said:
Not in the zip you have attached to the 1st post. They're in a folder named "Pixel Sounds" (and also doubled inside the "__MACOSX" folder), so you'll have to move them out from there...
Click to expand...
Click to collapse
Wow I am such an idiot. Thank you. Is it worth removing the post for my stupidity?
You're not at all the first to make that mistake, and definitely won't be the last (why do you think I have that section in the Magisk troubleshooting guide?)...
If you absolutely want the thread deleted I'm sure that can be arranged. Report the 1st post and a moderator that is assigned to this area of XDA can take care of it (I'm assigned to the Samsung forums, so I'm here I'm just another forum member but with a fancy badge).
But I'd recommend keeping it, since there's a real chance that someone will bump into this thread at some point (just like you found the other thread), and will be glad to find the info to help them with the same issue.

How to properly compress Magisk module .zip

Hello,
I'm trying to create my own Magisk module based on working modules and referencing the module instructions. Before getting too far, I wanted to make sure that the compression process worked correctly.
So, I downloaded a .zip module from the Magisk app (e.g. Wifi5ghzdisabler), moved .zip to my Ubuntu 20.04 PC using Google Drive, extracted the .zip (using Extract Here in Files context menu), compressed the module folder back to a .zip file (using Compress... in Files context menu) and then moved the new .zip back to the phone using Google Drive. No changes to any files were made. Then, I tried to install it from storage in the Magisk app (v23.0) on a OnePlus Nord N100 running Android 10, but I encountered the following error.
Installation Failed!
- Copying zip to temp directory
! Unzip error
Is this a compression issue or a permissions issue on the phone? I'm probably missing something simple. Thanks in advance.
DanHoliday said:
Hello,
I'm trying to create my own Magisk module based on working modules and referencing the module instructions. Before getting too far, I wanted to make sure that the compression process worked correctly.
So, I downloaded a .zip module from the Magisk app (e.g. Wifi5ghzdisabler), moved .zip to my Ubuntu 20.04 PC using Google Drive, extracted the .zip (using Extract Here in Files context menu), compressed the module folder back to a .zip file (using Compress... in Files context menu) and then moved the new .zip back to the phone using Google Drive. No changes to any files were made. Then, I tried to install it from storage in the Magisk app (v23.0) on a OnePlus Nord N100 running Android 10, but I encountered the following error.
Installation Failed!
- Copying zip to temp directory
! Unzip error
Is this a compression issue or a permissions issue on the phone? I'm probably missing something simple. Thanks in advance.
Click to expand...
Click to collapse
You should upload your zip.
Thanks for the reply.
I've attached the original WiFi5GhzDisabler-v1(1).zip module downloaded from inside the Magisk app.
I've also attached WiFi5GhzDisabler-v1(1)-re-compressed.zip after downloading, extracting and re-compressing the original module it as described in my first post. I didn't make any changes to the files/folders themselves. I did notice they are different sizes (6.1KB original versus 8.6KB re-compressed).
I'm trying to learn more about the correct compression process/tool for these modules. I searched the forum and found a thread with a similar issue. Basically, the OP shared a .zip file that didn't work and another member did something and uploaded a "fixed" version with minimal insight into how it was done.
[HELP] This zip is not a Magisk Module
I would assume there isn't anything wrong with the files in the original module since it was probably reviewed before it was hosted in the Magisk app. It is also strange that the .zip file downloaded from the github repos for various modules don't work for me either, but that may be a separate issue.
Any ideas? The instructions do not include how to compress the module.
Take a close look at the original zip again, and compare it to the one you recompressed. You've put all the files in a directory inside the zip, in comparison to putting them directly in the root of the zip...
There's your problem.
Didgeridoohan said:
You've put all the files in a directory inside the zip, in comparison to putting them directly in the root of the zip...
There's your problem.
Click to expand...
Click to collapse
You're exactly right. I was incorrectly zipping the module folder itself rather than the files inside the folder. As you correctly pointed out, this creates a folder inside the zip that adds an extra layer between the files and the root of the zip.
Wow, what a simple mistake. With your help, the recompressed module installs fine now. I was able to install my own module too!
Thank you so much for your help. My issue has been resolved.

[REQUEST] Module to replace a file in vendor/etc

I have an LG V60 phone and I would like to put the phone in "high impedance mode" all the the time for more power to the earphones even if they are less than 50 ohm impedance.
In LG V40/50, it was very simple by rooting the phone and making some modifications in the one of the files that was in the "vendor/etc" directory. The problem with LG V60 is it does not allow any write access to the vendor folder at all.
So the only feasible option that I can think of is to create a Magisk module that replaces the original file with the modified one. My biggest disadvantage is not knowing anything about writing codes including Magisk module ones. So I was wondering if anyone could create a Magisk module that would replace the original file through Magisk?
ADDTIONAL INOFRMATION:
I am running Magisk 25 on a fully rooted LG V60.
The file that needs to be changed is mixer_paths.xml and it resides in the "vendor/etc" folder. I have created the modified file.
So if someone is able to develop a module to accomplish this, I will place the modified file in the "system/vendor/etc" folder of the Magisk module, as I understand it.
Many thanks for your support!
You can use this template system in future as its super easy
The template itself is here
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
click the Code button, then download zip
then extract the zip into a folder and rename the folder "MMT-Extended-master" to the something more meaningful, like the name of your module
Read the wiki and docs here to go step by step to create your first module:
Home
Magisk Module Template Extended. Contribute to Zackptg5/MMT-Extended development by creating an account on GitHub.
github.com
Notably the heading:
How do I make a MMT Extended mod?​
The steps for a simple file addition/replacement module, which are simple, should be steps 1-4, then 8. Then zip up the modules (as a zip) and test.
For you, if you read along (in Step 3) you will need to create a folder vendor, under the existing system one, and then a further etc folder under vendor, and put the necessary file (mixer_paths.xml in there.
If you try and fail, post back and someone will assist. But we prefer people to at least read the documentation and try first, ideally...this is the way the great didgeridoohan mentored myself and many others, he was not big on spoonfeeding
Imagine the satisfaction you might get finding out youre capable of such feats...i promise its not rocket surgery
Feel free to PM even, if you get stuck and think you have a silly question - of course knowing me, and i do, you'll probably get an even sillier, and off topic answer as well...
hint: you can knock out this basic module in far far less time than it took me to write all this
Thank you!
So my changes look like this:
1. Put the modified file in the system/vendor/etc folder of the Magisk module.
2. Made the needed changes to the customize.sh as attached.
Royaltiger said:
Thank you!
So my changes look like this:
1. Put the modified file in the system/vendor/etc folder of the Magisk module.
2. Made the needed changes to the customize.sh as attached.
Click to expand...
Click to collapse
Yes, though you'll need to uncomment (remove the leading #) from the set_perm lines to make them active, also you only really need the 2nd one
Royaltiger said:
Thank you
73sydney said:
Yes, though you'll need to uncomment (remove the leading #) from the set_perm lines to make them active, also you only really need the 2nd one
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So I made the module with the suggested changes in customize.sh and put the modified mixer_path.xml file in the system/vendor/etc folder of the module. Module installs fine with Magisk but when it reboots, the device hangs on the initial LG screen and does not go anywhere from there.
I am attaching the customize.sh snapshot. Also, attached is the module file.
See here under "Disabling/uninstalling modules manually" if youre not able to boot
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
I am assuming that it is not possible to accomplish what I wanted to achieve.
Royaltiger said:
I am assuming that it is not possible to accomplish what I wanted to achieve.
Click to expand...
Click to collapse
mixer_paths files have been replaced for years, long before magisk even...i did it back as far as the Galaxy S2 from memory, so im not sure why this didnt work for you, was the mxer_paths file specifically for your device? i have no clear idea why it hasnt worked for you
this thread has a guide to making /system RW, so you could manually copy the file and overwrite it, but id really consider how much you want to replace mixer_paths before i set out to do that
V60 Bootloader Unlock and Magisk Root
Earlier today I was alerted to https://www.cnblogs.com/yanhua-tj/p/15525593.html which has the actual firehose and steps to unlock! However it seems to be in Simplified Chinese so I'll translate it here for you. The firehose is attached below...
forum.xda-developers.com
73sydney said:
mixer_paths files have been replaced for years, long before magisk even...i did it back as far as the Galaxy S2 from memory, so im not sure why this didnt work for you, was the mxer_paths file specifically for your device? i have no clear idea why it hasnt worked for you
this thread has a guide to making /system RW, so you could manually copy the file and overwrite it, but id really consider how much you want to replace mixer_paths before i set out to do that
V60 Bootloader Unlock and Magisk Root
Earlier today I was alerted to https://www.cnblogs.com/yanhua-tj/p/15525593.html which has the actual firehose and steps to unlock! However it seems to be in Simplified Chinese so I'll translate it here for you. The firehose is attached below...
forum.xda-developers.com
Click to expand...
Click to collapse
Actually I had no problem in editing the mixer_tavil.xml file in LG V40/50. But when it comes to LG V60, the file is read-only. There is no way to edit it due to dynamic partition. Hence, I was seeking the only option available i.e., via Magisk module.
Royaltiger said:
Actually I had no problem in editing the mixer_tavil.xml file in LG V40/50. But when it comes to LG V60, the file is read-only. There is no way to edit it due to dynamic partition. Hence, I was seeking the only option available i.e., via Magisk module.
Click to expand...
Click to collapse
So, I encountered the same problem and found what you did wrong. I was able to write my own Magisk module and it works wonderfully. It took so much time to understand how to do it because there is no proper tutorial.
If you are still active and trying to know how to do it the right way, here comes the explanation:
The Replace = " /system/vendor/etc/ " must not be written as it completely wipes the actual folder from your phone. This is why you were not able to turn the phone on. It should be like this:
Replace = " " (That part must be blank)
The rest of the code is good. If you try it like this now, you will see it will work, just like mine did.
Cheers
Does not work. May I see your module? Please upload it here as attachment.
I even put my edited file under /data/adb/modules/<my directory>/system/vendor/etc. It shows up in Magisk as a module and the file loads (as it is not visible in file explorer) but there is no change in volume. So the thing is not working.

Categories

Resources