For some reason I am unable to install any Modules. I've looked online for solutions and the only things I have found were to flash a module manually with TWRP and to check to make sure that the folder MagiskManager exists on your internal storage. The folder existed for me already and flashing manually did not work. Root access works fine however, I can use ABP, Titanium Backup, etc. just fine and Root Checker shows that I have Root properly installed. Here is what the log looks like.
- Copying zip to temp directory
- Installing Wireguard_installer-1.2.zip
- Mounting /system, /vendor
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
inflating: config.sh
inflating: module.prop
*******************************
+-+-+-+-+-+-+-+-+-+
|W|i|r|e|g|u|a|r|d|
+-+-+-+-+-+-+-+-+-+
*******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Found /data/adb/magisk_merge.img
- Mounting /data/adb/magisk_merge.img to /dev/tmp/magisk_img
! /data/adb/magisk_merge.img mount failed...
Failed!
! Installation failed
Also this module was last updated on the 23rd so I'm positive that it is up to date.
Phone: Motorola Moto G5 Plus
Edit: Some spelling mistakes and added some more information
I'm also facing same problem
In the official magisk thread:
"Some Motorolla devices' stock kernel ships with a flawed F2FS implementation. Change to a custom kernel with the fix or format data to ext4."
Basically Moto didn't do a good enough job with f2fs on our device, so magisk manager has trouble with mounting images. SU works, but modules can't install, and twrp flashed modules don't show up anywhere.
The only fix is installing a custom kernel with an f2fs fix, though too often I found custom kernels performed worse than stock.
bazinga137 said:
In the official magisk thread:
"Some Motorolla devices' stock kernel ships with a flawed F2FS implementation. Change to a custom kernel with the fix or format data to ext4."
Basically Moto didn't do a good enough job with f2fs on our device, so magisk manager has trouble with mounting images. SU works, but modules can't install, and twrp flashed modules don't show up anywhere.
The only fix is installing a custom kernel with an f2fs fix, though too often I found custom kernels performed worse than stock.
Click to expand...
Click to collapse
Ah that's unfortunate, however a few modules can be flashed straight from twrp that I've tried already. Don't remember which one I tried though because I bricked my device trying to flash Xposed from the Xposed app instead of the magisk compatible version, luckily though I managed to get it out of bootloop.
You must install http://forum.xda-developers.com/showthread.php?t=3577875
It's the F2FS bug prevention add on for Magisk (>=15.3)
nicolap8 said:
You must install http://forum.xda-developers.com/showthread.php?t=3577875
It's the F2FS bug prevention add on for Magisk (>=15.3)
Click to expand...
Click to collapse
I've just tried this and after flashing in TWRP I get the same errors
nicolap8 said:
You must install http://forum.xda-developers.com/showthread.php?t=3577875
It's the F2FS bug prevention add on for Magisk (>=15.3)
Click to expand...
Click to collapse
It worked perfectly with me.
Related
is there someone who succes in the installation of this app?
when i open it,it ask if i want to install the drivers and stuck and after few seconds it crash
someone can help me with this ?
Many guys use this and there already was enough discussions, there are even seperate threads created with tutorials, use search for once[emoji14]
I managed to get Viper4Android working this way:
First off, I use stock with systemless root and xposed so the many security features included in stock made it a bit tricky. If you use a custom rom with a custom kernel, it's likely a bit easier.
I flashed my stock image from the google website
I flashed a custom kernel and then Supersu and then the lolliviper zip from this thread: http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I installed busybox from the play store, opened the busybox app and let it install.
I disabled selinux enforcing using the app from this thread:
http://forum.xda-developers.com/showthread.php?t=2524485
Then I ran viper4audio and installed the driver from the app
Then I rebooted into twrp and used the terminal to delete /system/etc/audioeffects.conf and rebooted.
Voila, working Viper4android.
exad said:
I managed to get Viper4Android working this way:
First off, I use stock with systemless root and xposed so the many security features included in stock made it a bit tricky. If you use a custom rom with a custom kernel, it's likely a bit easier.
I flashed my stock image from the google website
I flashed a custom kernel and then Supersu and then the lolliviper zip from this thread: http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I installed busybox from the play store, opened the busybox app and let it install.
I disabled selinux enforcing using the app from this thread:
http://forum.xda-developers.com/showthread.php?t=2524485
Then I ran viper4audio and installed the driver from the app
Then I rebooted into twrp and used the terminal to delete /system/etc/audioeffects.conf and rebooted.
Voila, working Viper4android.
Click to expand...
Click to collapse
By the way, you can run a supolicy script for media server instead of disabling selinux because that would increase security risks and don't you mean audio_effects.conf in vendor? IMO better to add v4a entries than delete it, it's there for a reason I would think
hinxnz said:
By the way, you can run a supolicy script for media server instead of disabling selinux because that would increase security risks and don't you mean audio_effects.conf in vendor? IMO better to add v4a entries than delete it, it's there for a reason I would think
Click to expand...
Click to collapse
Yes! Thanks for the corrections! I haven't done it in a while! ?
I managed to have magisk and magiskhide working sucessfully, with some manual tricks and workarounds
There is a bug in f2fs that prevents /data/magisk.img to me mounted writable, so the tweek is just moving that file to the /cache partition, which is ext4 and creating a symlink to the original file.
So the steps for a working magisk is.
- Unlock your bootloader
- Install Twrp
- Flash magisk without mounting data partition and boot once.
- Reboot to recovery and open terminal (advanced)
- move magisk.img to /cache partition, changing name ( example: mv /data/magisk.img /cache/magisk_2.img)
- Create a symlink between_files ( ln -s /cache/magisk_2.img /data/magisk.img)
Would be nice if anybody can try to reproduce.
Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.
lpchaim said:
Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.
Click to expand...
Click to collapse
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.
jblancoperez said:
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.
Click to expand...
Click to collapse
Right. I think I'll try this out today and see how things turn out. As for SafetyNet, I though the unlocked bootloader alone was enough reason for it not to work, is this only for some models?
Update: So, @jblancoperez, I've reproduced your steps and Magisk Manager tells me it's installed but root isn't activated and it doesn't let me do anything else as a result.
Things to have a look,
Please confirm in the terminal if /magisk is mounted.
Go back to TWRP terminal and also confirm if the symlink is OK.
Nice to get the output from /cache/magisk.log
It took me a while to have everything right, doing it on TWRP is not the easiest places to move things around.
So, an update. Your method just wouldn't work for me at all, no matter how many times I tried. What worked was following the first part only, as in unmounting data and then flashing Magisk afterwards. I've tried Xposed and Viper4Android; they worked, but both did have to be flashed through twrp as opposed to Magisk Manager, which would throw an error. Not sure if that's on them or on this particular method. I should mention though that SafetyNet wouldn't pass even before xposed and with the hiding settings, not sure why.
You may want to try the kernel where the f2fs bug is fixed, which may be the cause when Magisk hide is not working which would cause Safetynet to fail.
Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?
tag68 said:
Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?
Click to expand...
Click to collapse
I got bootloop when I install magiks 11.0.
Do you have a logfile of that action in /cache or /cache/recovery which we could show in the Magisk thread?
I was able to upgrade the 10.2 installation.
Will try a new clean installation on the weekend with the f2fs fixed kernel.
I think I got why my procedure is not working for other people. Please try to copy the image instead of moving with the flags preserving de selinux attributes.
jblancoperez said:
Please try to copy the image instead of moving with the flags preserving de selinux attributes.
Click to expand...
Click to collapse
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.
tag68 said:
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.
Click to expand...
Click to collapse
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.
jblancoperez said:
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.
Click to expand...
Click to collapse
cp -a tries to copy attributes including timestamps. But it only succeeds if you are currently running as root.
I wanted to install Viper4android on stock 7.0 march but was unable to do so after following 2-3 different methods. Is there anyone successfully using viper4android on stock? And if not successful them suggest any other sound mod fully working and compatible with stock 7.0 march. I am rooted, elementalX 1.04 + busybox also installed :silly:
You intent with Viper4Aprise?
most of these require permissive selinux and i dont want to do that.
Why? I dont know for what flash permissive, what Is this?
JassyelZ said:
Why? I dont know for what flash permissive, what Is this?
Click to expand...
Click to collapse
selinux can be "enforcing" which is more secure or "permissive" which is less secure. V4A does require permissive kernel generally.
so anyone found a working sound mod for stock rom with selinux enforcing?
nitish_namdev said:
so anyone found a working sound mod for stock rom with selinux enforcing?
Click to expand...
Click to collapse
I've got ARISE running on my device (NPJS25.93-14.4, ElementalX, magisk v13). Note, I'm just running the core modules, any other addons I do not know if you need to tweak further. I have not changed ElementalX's SE Linux permissions, and running 'su getenforce' in a terminal returns as 'enforcing'.
My setup: XT1642, updated to NPJS25.93-14.4, ElementalX, magisk v12/v13 (think if you have SuperSU, should be okay too).
1) Downloaded ARISE Magnum Opus from here: https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 (I currently have the 05/06 build). The download link is the Magnum Opus TM. Also, as I'm using magisk, I downloaded the magisk compatibility module. https://forum.xda-developers.com/an...y-research-t3379709/post71569390#post71569390
2) To configure ARISE before flashing, I extracted arise_customize.prop to /sdcard, and configured install.core to = true, install.v4a_2.5.0.5= to be true (and later found out I needed delete.deep_buffer to = true). Saved the ARISE customise file (I've uploaded my prop file if you want to see my modifications. If you wish to use this file, delete the .txt in the file name so the extension is .prop).
3)Rebooted to TWRP. Backed up. Flashed ARISE Magnum Opus - as configured, it should flash the 2.5.0.5 core module and delete the deep buffer (without deleting deep buffer, I found that ARISE did not process output).
3a)After ARISE, flashed the magisk compatibility module (if you're on SuperSU, you may not have to flash this). With magisk v13, this does not trigger Safety Net.
4)Wipe cache/Dalvik and reboot.
5)As I'm using Poweramp, I had to go to Poweramp Settings > Audio > Advanced Tweaks and disable Direct Volume Control. Also, I disabled the main Equalizer.
Now, ARISE processes headphone output as per the ARISE settings.
I have a problem with rooted tab4 tablet.
When i remount /system to rw, device hangs/freezes (stop responding).
Tested with magisk and SuperSU.
Android 7.1.1
EDIT:
I figured out.
It's necessary to flash through TWRP, a magisk module from dywersant's post.
When module is enabled, it's possible to mount /system as rw, but device will not pass SafetyNet test.
When module is disabled, /system is mounted as ro, any change on this partition will freeze device, but it will pass SafetyNet test.
I use this module only when I Have to.
tgm28 said:
I have a problem with rooted tab4 tablet.
When i remount /system to rw, device hangs/freezes (stop responding).
Tested with magisk and SuperSU.
Android 7.1.1
Click to expand...
Click to collapse
How have got it rooted?
Uqbar said:
How have got it rooted?
Click to expand...
Click to collapse
Just follow instructions in this thread TWRP and ROOT for Tab 4 8/10 (Plus)
Flash magisk, flash magisk module named magisk-remount (from HERE ) - this module is for /system remount (when it is enabled Magisk do not pass SafetyNet test; when disabled it pass)
Probably that's all
tgm28 said:
Just follow instructions in this thread TWRP and ROOT for Tab 4 8/10 (Plus)
Flash magisk, flash magisk module named magisk-remount (from HERE ) - this module is for /system remount (when it is enabled Magisk do not pass SafetyNet test; when disabled it pass)
Probably that's all
Click to expand...
Click to collapse
Thanks. I haven't found any custom ROM (I am looking for a debloated one). Have you?
Uqbar said:
Thanks. I haven't found any custom ROM (I am looking for a debloated one). Have you?
Click to expand...
Click to collapse
No. I use Stock rom with magisk and Twrp.
How bloated is it?
Uqbar said:
How bloated is it?
Click to expand...
Click to collapse
Not heavily like samsung's devices. It's almost clean.
Did you ever find any other ways other than magisk to mount /system as rw without a system freeze?
Does not work.
This method doesn't work, the system is freeze anyway.
arminass said:
This method doesn't work, the system is freeze anyway.
Click to expand...
Click to collapse
What's news? Is there any other way?
I use Magisk 20.3 or 20.4 on my two tablets.
One tablet is under stock Android 8.1.0
and another is under LineAgeOS16 - Android 9 Pie.
Both, give su for applications and ADB, but don't have system root for system folder.
@krchat - did you try installing the zip in this post to see if you could write /system?
drizzle123 said:
@krchat - did you try installing the zip in this post to see if you could write /system?
Click to expand...
Click to collapse
yes, no luck.
krchat said:
yes, no luck.
Click to expand...
Click to collapse
It's a complete pain. I heard its problems with Magisk? Anyhow I installed magisk 19.3 - booted then installed the remount zip, rebooted again - checked the system was RW, then installed magisk 20.4. All seems well for me
arminass said:
Does not work.
This method doesn't work, the system is freeze anyway.
Click to expand...
Click to collapse
Hello, have you found a way to write to the system partition? My los17.1 write system partition will freeze. I'm going crazy!
asphalt73 said:
Hello, have you found a way to write to the system partition? My los17.1 write system partition will freeze. I'm going crazy!
Click to expand...
Click to collapse
Nope.
Did it work even with dm-verity?
I got it to work - installed magisk via twrp and was able to use su and run scripts at boot <3
I installed magisk and I can write files to /system, but when I reboot the device the files are removed from /system. What do I need to do so that files that are written to /boot or /system are persisted across reboot?
My main goal is to be able to update init.rc so that I can have the device power on when plugged into a charger
drizzle123 said:
I got it to work - installed magisk via twrp and was able to use su and run scripts at boot <3
Click to expand...
Click to collapse
I use Magic 20.3 or 20.4 on my two tablets.
One tablet is under stock Android 8.1.0
and another is under LineAgeOS16 - Android 9 Pie.
Both, give su for applications and ADB, but don't have system root for system folder.