Hi guys, im here coz currently i cant edit the file on stock. It always discard the changes on reboot. I have the latest magisk stable, have installed it with dm-verity disabled, and flashed on recovery the dm-vrity universal ZIP. Ive tried the magisk module for dual speaker, changing the module file with my mixer_paths_changes... and no sucess (i did it on A9 sucessfully).
Any suggestion? I only want to set all the AVC Volume from all DAC Outputs to "0".
Related
have anyone successfully installed drivers and ran Viper4android on HTC One A9 on Nougat 7.0?
please let me know..
Im on European Nougat 7.0, S-OFF, TWPR Installed, Rooted, Busybox installed, SElinux Permissive..
after i installed V4A (flashed zip via TWRP), driver installed but it repeatedly asks to install driver on every reboot..
i also tried moving v4a into system but still problem persist.
V4A not working , any fix for this?
Fixed..
Viper4Arise working like charm
scroll down, find reply by Fudgehog, click mediafire link, download zip.. thanks @Fudgehog
enter recovery TWRP 3.0.3-8, enter in Terminal, setenforce 0, flash the downloaded zip, reboot..
done, enjoy :highfive:
I had played around with this myself.
Try booting to TWRP, on the cleanest rom you can, terminal emulate setenforce 0, then flash this zip. Let me know if it works. Works on my stock rooted A9 developer, WNC's Rom.
Also on a friends M9 his phone did the same as mine where it would show numbers in TWRP then reboot instantly. I injected the apk and lib folder into system app on his phone, didn't work but then with permissive in TWRP, Flashing the numbers zip worked. Make sure you have Captains latest TWRP.
You can also try using Kernel Adiutor to set SELinux to permissive on boot. Make a file in system/etc/init.d called "setperm08", and edit it as a text file and put in #!/system/sh
setenforce 0
http://www.mediafire.com/file/suwzbl0l78guuwz/ARISE+Sound+Systems+Numbers+3.5.zip
Fudgehog said:
Try booting to TWRP, on the cleanest rom you can, terminal emulate setenforce 0, then flash this zip. Let me know if it works. Works on my stock rooted A9 developer, WNC's Rom.
Also on a friends M9 his phone did the same as mine where it would show numbers in TWRP then reboot instantly. I injected the apk and lib folder into system app on his phone, didn't work but then with permissive in TWRP, Flashing the numbers zip worked. Make sure you have Captains latest TWRP.
You can also try using Kernel Adiutor to set SELinux to permissive on boot. Make a file in system/etc/init.d called "setperm08", and edit it as a text file and put in #!/system/sh
setenforce 0
http://www.mediafire.com/file/suwzbl0l78guuwz/ARISE+Sound+Systems+Numbers+3.5.zip
Click to expand...
Click to collapse
superb.. thanx man.. :laugh:
it worked like charm :highfive:
You already know bud!
You're welcome, glad I could help! I hope more people find this thread and use my information, I tried to give you every possible solution I could.
So.. where do I start..
After I rooted my phone with magisk and twrp -------------------->(I had a qualcomm crashdump crash when I tried to boot from the twrp .img and I found a way around it)
I tried installing some magisk modules.(first time installing a magisk module ever)
2-3 modules later I noticed that some modules should have an app installed after reboot but I didnt saw any new app despite of having no errors in the terminal while installing.
I tried:
--Installing newer beta magisk version (17.2)
--Reinstalling the module
--Complete factory reset with the unbrick tool (msmdownloadtool) and all over again.
--Installing bluspark recovery (and then all over again)
--Installing bluspark kenel (and then all over again)
--Changing data filesystem partition to F2FS (but OOS didnt like it and bootloop)
--Installing the .zip modules from twrp (didnt work) (probably cause of encryption but if I find a new module I want to install I dont want to factory reset every time)
--Installing xXx No limits magisk rom
And I am here to ask for help because I really do not know what to do.
Thank you :/
ps.I am new to this forum so do not take it for granted to know even some basic stuff
First do NOT use f2fs it's junk. Use Google for more information on that file system
I'm using the canary version of Magisk for the Q beta 6. Yesterday I tried to install a self made module to get rid of screenshot sounds (the one on the rep isn't working because Google changed the path. But as I installed it, I can only remember that the last line was "Magisk manager will be removed and your device will reboot in a moment" or something like that
Well, the manager is still installed, but Magisk itself got uninstalled. Besides the fact that I have no clue why that happened, now I can't install it. TWRP doesn't support Q. So I got the Q image from Google, extracted the boot.img and let Magisk Manager patch it (with preserve force encryption and Preserve AVB 2.0/dm-verity turned on) and flash it through Fastboot (fastboot flash boot magisk-boot.img) but it's still not installed. And without TWRP of course I can't flash the uninstaller zip (no clue what was actually removed).
Is there a way through adb or fastboot to find out what's left of the Magisk installation and remove that? Or any other solution I didn't think of?
Ok, via adb is not an option since both /data and /cache refuse permissions so I can't even get logs to find out what happened.
Does anyone have a working pre-patched boot.img? I don't know if that Manual method isn't working because patching isn't really working or because the Magisk files are still present and the module is still conflicting with Magisk. And I don't want to do a factory reset
Nevermind. It was a faulty Magisk database, I had to uninstall and reinstall it to solve the problem
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
MichRT said:
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
Click to expand...
Click to collapse
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
You have to use last magisk (above 19.4 if my memories are right).
HpNoTiQ said:
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Click to expand...
Click to collapse
This looks like it might work, so thank you! I found a similar, though different solution (below)
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
I ran into the issue that while boot-looping with a magisk patched boot img, I wasn't able to run the command, adb wasn't finding the phone. I tried again after booting TWRP and it basically threw an 'error - command not found'.
HpNoTiQ said:
You have to use last magisk (above 19.4 if my memories are right).
Click to expand...
Click to collapse
I think you are right, in beta/canary channel
@Tulsadiver gave me a hand with this, see here: https://forum.xda-developers.com/showpost.php?p=80398385&postcount=35997
Thank you guys!
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
You could use DFE (If you want unencrypted data) or use magisk module for recovery. to remove unwanted magisk modules
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
There is magisk module which check on start of the phone if any module makes a bootlop and disable it. Magisk Bootloop saver on github
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
Power phone off completely. Power on and when MIUI logo shows on screen hold volume down button until phone boots, this will disable all magisk modules you have installed. It's called magisk safe mode. You can now enter magisk app and enable modules one by one until you find the culprit.
Sidenote: I upgraded from xiaomi.eu 12.0.6 to 13.0.3 using fastboot. TWRP was unable to decrypt when I booted to recovery to install magisk after update. I rebooted back to MIUI and disabled pin and fingerprint. Rebooted back to TWRP and was able to access data and install magisk from the downloads folder. So try disabling screen lock and see if TWRP is working then.
Well orangefox has magisk manager built in, so modules can be removed with a swipe
you can navigate to data/adb/modules folder in twrp file manager without decryption needed and delete module folder.
worked for me on android 12.
I got stuck at Xiaomi logo after installing some module. The storage is encrypted on Android 12, decryption in recovery is not possible at the moment. So using OrangeFox or deleting /data/... is not possible.
The only solution that worked for me was accessing the safe mode and running this command from adb shell.
magisk --remove-modules