cannot pass safety net on miui 10 global beta .
i installed root using magisk 16.
everything works fine ( Gcam, viper4droid etc)
but my safetynet is broken.
cts profile mismatch is true.
i m unable to find any solution.
tried universal safety net fix through twrp it says no magisk installed but root is working properly.
can anyone fix it?
wirex13 said:
cannot pass safety net on miui 10 global beta .
i installed root using magisk 16.
everything works fine ( Gcam, viper4droid etc)
but my safetynet is broken.
cts profile mismatch is true.
i m unable to find any solution.
tried universal safety net fix through twrp it says no magisk installed but root is working properly.
can anyone fix it?
Click to expand...
Click to collapse
Install the fix through magisk directly. Not twrp.
change your device fingerprint in build. prop file.. and then reboot ..voila!
you can replace fingerprint with stable rom v9. 5.13
Can anyone share the stable rom's fingerprint from their device?? It will be very helpful.
Edit :-I have found a fix and stable rom's fingerprint in this thread.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
And its working very well. Hope that helps you. Ask me if you need any help about enabling this module because its a bit different than others.
otonieru said:
Install the fix through magisk directly. Not twrp.
Click to expand...
Click to collapse
its says
Copying zip to temp directory - Installing ... Failed! !
wirex13 said:
its says
Copying zip to temp directory - Installing ... Failed! !
Click to expand...
Click to collapse
If that so, theres chance your magisk installation was derp. Try reinstalling magisk first. Or use the safetynet prop fix module, not the universal one.
RockStar8 said:
Can anyone share the stable rom's fingerprint from their device?? It will be very helpful.
Edit :-I have found a fix and stable rom's fingerprint in this thread.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
And its working very well. Hope that helps you. Ask me if you need any help about enabling this module because its a bit different than others.
Click to expand...
Click to collapse
i used above steps but in terminal it says
"the settings boot script does not appeared to run during boot"
this means the module doesn't work.
dipak9477 said:
change your device fingerprint in build. prop file.. and then reboot ..voila!
you can replace fingerprint with stable rom v9. 5.13
Click to expand...
Click to collapse
can u provide ro fingerprint
ro.build.fingerprint =
wirex13 said:
i used above steps but in terminal it says
"the settings boot script does not appeared to run during boot"
this means the module doesn't work.
Click to expand...
Click to collapse
The module itself has Redmi Note 5 Pro Oreo MIUI 9.5 Stable signature added in its database. You just need to download and flash the module from magisk and reboot. Then open terminal and run command su then allow root access then run command props choose change device signature then choose Redmi Note 5 Pro then Confirm and Reboot. Just remember to reboot after installing the module and then use terminal commands.
dipak9477 said:
change your device fingerprint in build. prop file.. and then reboot ..voila!
you can replace fingerprint with stable rom v9. 5.13
Click to expand...
Click to collapse
just replace miui version in ro. build. fingerprint with V9.5.13.0.OEIMIFA
Related
First of all i think there is a need in common thread about Magisk.
I am on XT1685 with 137-35 ver. and exprerienced some Magisk issues. MagiskSU works well on 12.0, 13 beta and 13.3. But SafetyNet is not. My particular problem is not mountable magisk.img. And there is a suggestion that may be caused by f2fs issue on some Lenovo devices (or something else). In different threads there are a lot of different messages about working/not working SafetyNet so i think we need clarification. Most people don't even bother to point out OS version, stock, custom kernel, model etc. So let try to gather information about issue together.
SafetyNet status: not pass
Model: XT1685
OS: Stock 137-35
Kernel: Stock
Magisk: 13.3
Have you also tried the universal safetynet fix and it still doesn't pass?
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Dahenjo said:
Have you also tried the universal safetynet fix and it still doesn't pass?
Click to expand...
Click to collapse
Magisk modules don't work with stock kernel
For OP, you should try a custom kernel, probably this will fix your safety issue
atrac17 said:
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Click to expand...
Click to collapse
Same there. Yesterday flashed attack11 Extended Kernel V4 for NPN25.137-35 then flashed Magisk 13.3. All is green without USNF. Tried V5 but there was broken camera.
CaptPetrenko said:
Same there. Yesterday flashed attack11 Extended Kernel V4 for NPN25.137-35 then flashed Magisk 13.3. All is green without USNF. Tried V5 but there was broken camera.
Click to expand...
Click to collapse
V5 is for -67. That's why you had trouble.
atrac17 said:
V5 is for -67. That's why you had trouble.
Click to expand...
Click to collapse
Yeap.
Have you faced issue that folder binders or folder mounter not working of any kind. If you got a working then tell me. I am on 35
manjot7798 said:
Have you faced issue that folder binders or folder mounter not working of any kind. If you got a working then tell me. I am on 35
Click to expand...
Click to collapse
What do you exactly mean? In my case Magisk could not mount magisk.img into /magisk on system start
CaptPetrenko said:
What do you exactly mean? In my case Magisk could not mount magisk.img into /magisk on system start
Click to expand...
Click to collapse
I mean folder mount apps, the app in which you can free space, in which you have to mount the folder or can search it up on play store as folder mount or app2s all in one tool. It didn't seem to work on magisk 13.3 whereas it worked on magisk 11.6
manjot7798 said:
I mean folder mount apps, the app in which you can free space, in which you have to mount the folder or can search it up on play store as folder mount or app2s all in one tool. It didn't seem to work on magisk 13.3 whereas it worked on magisk 11.6
Click to expand...
Click to collapse
Can not say something about that. I never mounted folders. Use only Root Explorer for file managing. Do you have problems with SafetyNet? Could you send Magisk log? May be your mounting problem has common roots with stock kernel issue and read-only preferences
XT1687
NPNS25.137-33-5
Security patch level is May 1, 2017
I used this video as my guide: youtube[dot]com/watch?v=zUPTFnzAvSo
Root was successful with Magisk 13.3 (including installation of ElementalX-G5-1.01) but ctsProfile and basicIntegrity are false with Safety Net check. The creator of the video had us flash universal safety net fix v1.zip and updated safety net fix v2.zip which I did, but the SafetyNet check still fails. On his video, both items passed.
Not sure what went wrong for me.
He advised users (in the comments) to flash a different kernel, then flash the two safety net zip files again. Good advice or not? Can someone elaborate?
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Quote:
Originally Posted by atrac17
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
After updating to v. 14.0 ctsProfile error occured. I rolled back to 13.3 version but there was the same error. I flashed the latetst beta of universal fix and ctsProfile check went through. Don't know would it work with 14.0 ver.
brandonsisco said:
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Click to expand...
Click to collapse
CaptPetrenko said:
After updating to v. 14.0 ctsProfile error occured.
Click to expand...
Click to collapse
Hi,
Most of the work regarding the cts check can be done with a custom kernel.
And one relevant factor is remove the parameters "androidboot.verifiedbootstate" and "androidboot.veritymode" from the command-line (patching the "/proc/cmdline" file).
See this post: http://forum.xda-developers.com/showpost.php?p=73712158&postcount=471
If you like to pass the SafetyNet, then first use a patched kernel or request to developers to include this patch!
Don't waste your time with other complex solutions!
Hi,
If you like to pass SafetyNet in stock and have full support for Magisk then install this kernel:
https://forum.xda-developers.com/showpost.php?p=73783900&postcount=483
Regards.
Lineage OS 14.1 & LOS kernel with Magisk 14 does not pass.
brandonsisco said:
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Quote:
Originally Posted by atrac17
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Click to expand...
Click to collapse
I changed to the v4 extended kernel, Magisk V14.0, and also getting all green on the SafetyCheck with the 35 rom. BUT MagiskHide does not work: when I look at the logs I see
fopen:/magisk/.core/hidelist failed with 2: No such file or directory
Does MagiskHide work for you?
Yes working for me I suspect you have mounting error above that in log?
---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------
I suggest install stock then extended kernel then magick fresh
snaggletooth1 said:
XT1687
NPNS25.137-33-5
Security patch level is May 1, 2017
I used this video as my guide: youtube[dot]com/watch?v=zUPTFnzAvSo
Root was successful with Magisk 13.3 (including installation of ElementalX-G5-1.01) but ctsProfile and basicIntegrity are false with Safety Net check. The creator of the video had us flash universal safety net fix v1.zip and updated safety net fix v2.zip which I did, but the SafetyNet check still fails. On his video, both items passed.
Not sure what went wrong for me.
He advised users (in the comments) to flash a different kernel, then flash the two safety net zip files again. Good advice or not? Can someone elaborate?
Click to expand...
Click to collapse
Hi, I came from the same video and I did all the steps he put in there. I did the root process with Magisk 13 then I updated to 14 version (a days ago) and everything is working ok.
Was trying to install SuperSU on MIUI 9.6.4 and 10.0.1, both gave me during "patching sepolicy".
Log:
- Creating backup
rm: can't remove '/data/stock_boot_*.img': No such file or directory
rm: can't remove '/cache/stock_boot_*.img': No such file or directory
rm: can't remove '/cache/stock_boot_*.img.gz': No such file or directory
libc: Access denied finding property "persist.vendor.dpm.feature"
libc: Access denied finding property "persist.vendor.dpm.feature"
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
[/dev/block/mmcblk0p58](67108864) --> [/data/stock_boot_a2de9e416bf12f0440dd6b4639bb495b276a438f.img.gz](16430168)
rm: can't remove '/sutmp/ramdisk.original': No such file or directory
- Patching sepolicy
libc: Access denied finding property "persist.vendor.dpm.feature"
libc: Access denied finding property "persist.vendor.dpm.feature"
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
Could not locate entry
--- Failure, aborting
Is anyone knows what's problem and how to get SuperSU installed ?
Thanks in advance.
Just use Magisk. SuperSU isn't in development anymore.
Sent from my Redmi Note 5 using Tapatalk
1) is anyone SuperSU works on 9.6.4 or 10.0.1 ?
2) I tried Magisk and it worked but when I installed Xposed (sdk26 and sdk27) from TWRP or Magisk , both got me into bootloop untill I uninstalled Magisk from TWRP. Anyone have the same experience ? Or how to get Xposed installed ?
Thanks
Did you use Xposed from Magisk repo?
easy_hk said:
1) is anyone SuperSU works on 9.6.4 or 10.0.1 ?
2) I tried Magisk and it worked but when I installed Xposed (sdk26 and sdk27) from TWRP or Magisk , both got me into bootloop untill I uninstalled Magisk from TWRP. Anyone have the same experience ? Or how to get Xposed installed ?
Thanks
Click to expand...
Click to collapse
xposed dont work on miui. only works on AOSP LAOS ect.
Antyhaker said:
Did you use Xposed from Magisk repo?
Click to expand...
Click to collapse
I used from repo and downloaded .zip, both not working. keep bootloop.
raptorddd said:
xposed dont work on miui. only works on AOSP LAOS ect.
Click to expand...
Click to collapse
is this started from MIUI 9/10 ? I used to use xposed on redmi 4 and max.
easy_hk said:
I used from repo and downloaded .zip, both not working. keep bootloop.
is this started from MIUI 9/10 ? I used to use xposed on redmi 4 and max.
Click to expand...
Click to collapse
since oreo.. no fix for xposed. and rovo89 is aware ever since the beginning of the year. but he hasnt fix it.
like i said but AOSP oreo xposed works. but not on miui oreo.
raptorddd said:
since oreo.. no fix for xposed. and rovo89 is aware ever since the beginning of the year. but he hasnt fix it.
like i said but AOSP oreo xposed works. but not on miui oreo.
Click to expand...
Click to collapse
sounds a sad news for MIUI user :crying::crying:
easy_hk said:
sounds a sad news for MIUI user :crying::crying:
Click to expand...
Click to collapse
yes it does. but ive never got to install superSU. mine was different error error 7. so i moved to magisk.
raptorddd said:
yes it does. but ive never got to install superSU. mine was different error error 7. so i moved to magisk.
Click to expand...
Click to collapse
error 7 for install SuperSU ?
easy_hk said:
error 7 for install SuperSU ?
Click to expand...
Click to collapse
yes. never installed so i gave up switched to magisk
never saw err 7 before on SuperSU. Lucky magisk still works.
V4A Fx installation (Rooted with magisk required)
Download following modules:
https://drive.google.com/folderview?id=10Q_4QsFAe8cW63GH3VrM0jtuIOAPP8t1
1.Install magisk_selinux_manager_v1.0.zip magisk module in magisk manager and set selinux to permissive.
2.install ViPER4Android_FX-v2.7.1.0(2710).zip magisk module in magisk manager.(requires internet)
3.Reboot and open V4A it will ask for driver installation .Allow it
4.After installation of driver it will automatically reboot .
5.Enjoy V4A
Credits to @santoshhh000
If you like this post press thanks
No
Did you install from magisk? Not twrp. Follow the instructions as mentioned above
ariber14 said:
Did you install from magisk? Not twrp. Follow the instructions as mentioned above
Click to expand...
Click to collapse
Yes, from magisk.
I will try again when reinstall miui eu.
omerhodzic1 said:
Yes, from magisk.
I will try again when reinstall miui eu.
Click to expand...
Click to collapse
Hey, miui eu is working?
---------- Post added at 11:10 PM ---------- Previous post was at 11:08 PM ----------
[/COLOR]
Linkonlk said:
Hey, miui eu is working?
Click to expand...
Click to collapse
Found it on the telegram group.
Redmi Note 8 Pro | OFFICIAL
Redmi Note 8 Pro - Official Telegram Group
t.me/RedmiNote8ProOfficial
ariber14 said:
V4A Fx installation (Rooted with magisk required)
Download following modules:
https://drive.google.com/folderview?id=10Q_4QsFAe8cW63GH3VrM0jtuIOAPP8t1
1.Install magisk_selinux_manager_v1.0.zip magisk module in magisk manager and set selinux to permissive.
2.install ViPER4Android_FX-v2.7.1.0(2710).zip magisk module in magisk manager.(requires internet)
3.Reboot and open V4A it will ask for driver installation .Allow it
4.After installation of driver it will automatically reboot .
5.Enjoy V4A
Credits to @santoshhh000
If you like this post press thanks
Click to expand...
Click to collapse
Which miui you install?
omerhodzic1 said:
Which miui you install?
Click to expand...
Click to collapse
On miui 11.0.2.0 eu
ariber14 said:
On miui 11.0.2.0 eu
Click to expand...
Click to collapse
I tried multiple times, miui eu 11.0.2.0, with a clean install at the end, without an account and any backup, different versions of magisk, ect. 1 or 2 sim card.
With one, one sim card work, when I installed the Viper with 2 sim, stop working both.
Maybe I'll be lucky with some new version. The Viper is my favorite.
Search for a zip called clean+soundmod.zip.it will remove any audio mod that might create conflict.flash it ftom twrp then repeat the procedure again as mentioned
ariber14 said:
Search for a zip called clean+soundmod.zip.it will remove any audio mod that might create conflict.flash it ftom twrp then repeat the procedure again as mentioned
Click to expand...
Click to collapse
Can you post it here. I could not find it.
Here it is. Flash it from twrp then restart
ariber14 said:
Here it is. Flash it from twrp then restart
Click to expand...
Click to collapse
Thank you!!
Your phone is using xiaomi.eu rom, but Is it China version or Global version?
I have China one with same xiaomi.eu rom, but cant seem to make viper work
MarkLev said:
Thank you!!
Your phone is using xiaomi.eu rom, but Is it China version or Global version?
I have China one with same xiaomi.eu rom, but cant seem to make viper work
Click to expand...
Click to collapse
M1906G7G - Global 64mb - not working for now.
omerhodzic1 said:
M1906G7G - Global 64mb - not working for now.
Click to expand...
Click to collapse
Problem with magisk_selinux_manager_v1.0.zip
If use 2 SIM they stop working.
Viper working with setenforce 0 in terminal.
Found this on telegram group:
t.me/RedmiNote8ProOfficial
I have noticed . Selinux manager module when flashed through latest magisk .It Doesn't work ,so if possible flash it through older version magisk 20.0 or earlier version .After that you can update your magisk to latest.
santoshhh000 said:
I have noticed . Selinux manager module when flashed through latest magisk .It Doesn't work ,so if possible flash it through older version magisk 20.0 or earlier version .After that you can update your magisk to latest.
Click to expand...
Click to collapse
I tried with magisk 19 and the problem is the same.
I also have a problem with SIM cards, when install magisk_selinux_manager_v1.0.zip with permissive, only when I take out one SIM card GSM works, when two are not working, no registered cards in mob, if install with enforceing is ok, that's weird. It is no problem for me to use the terminal, it is also safer for the system, it may be safer not to be in permissive mode all the time.
Thank you for your help.
And most importantly, I have ViPER4A!
All the best,
omerhodzic1 said:
I tried with magisk 19 and the problem is the same.
I also have a problem with SIM cards, when install magisk_selinux_manager_v1.0.zip with permissive, only when I take out one SIM card GSM works, when two are not working, no registered cards in mob, if install with enforceing is ok, that's weird. It is no problem for me to use the terminal, it is also safer for the system, it may be safer not to be in permissive mode all the time.
Thank you for your help.
And most importantly, I have ViPER4A!
All the best,
Click to expand...
Click to collapse
1. Install SELinux Mode Changer app from here
2. Install lates viper4android app
3. Start SELinux Mode Changer and set to "permissive" then start viper4android and Enjoy!
you can set autostart for SELinux Mode Changer
MarkLev said:
1. Install SELinux Mode Changer app from here
2. Install lates viper4android app
3. Start SELinux Mode Changer and set to "permissive" then start viper4android and Enjoy!
you can set autostart for SELinux Mode Changer
Click to expand...
Click to collapse
That's it.
Thnx
I totally forgot Tasker.
UNIVERSAL SafetyNet FIX
(A515x Edition)
ABOUT THIS:This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021. The only requirement is that you can pass basic attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.
Passing basic attestation is mostly out-of-scope for this module; this module is meant to defy hardware attestation, as well as reported "basic" attestation that actually uses hardware under-the-hood. Nonetheless, it features a few basic attempts at helping pass basic attestation on some devices, especially older devices and devices running stock ROMs.
HOW DO I USE IT?
Code:
1. Simply install the module by Magisk, reboot
2. Enable Magisk Hide and enjoy
**ITS ONLY for A51 OneUI 2.5 or 3.0
CREDITS TO:
@kdrag0n (Original developer of this mod)
@spit85 (For his important information and experience applying it to other devices )
SafetyNET Patch A51
Its based on the stock keystore so it doesnt affect anything
is it working One UI 2.1 refined v1.0 ?
Fatih27 said:
is it working One UI 2.1 refined v1.0 ?
Click to expand...
Click to collapse
It should be the same keystore. You can test it. If your phone doesn't boot, boot to recovery and delete the module there.
Hi, I do the steps but it keeps saying that the certification failed :/
EDIT: Solved
My sefty net passes but after that i can't access mobile setting
It says the settings has stopped
ameer419 said:
My sefty net passes but after that i can't access mobile setting
It says the settings has stopped
Click to expand...
Click to collapse
You are using a Samsung galaxy a51? Android 10 or 11?
spit85 said:
You are using a Samsung galaxy a51? Android 10 or 11?
Click to expand...
Click to collapse
Android 10
ameer419 said:
Android 10
Click to expand...
Click to collapse
That's strange. It should work on android 10. I hex patched that keystore by my self. Maybe you got another magisk module that conflicts with these one. Do you have magisk props hide module? If yes, delete that module. You don't need it with these safetynet patch. And these patch is only for stock rom or stock base roms
spit85 said:
That's strange. It should work on android 10. I hex patched that keystore by my self. Maybe you got another magisk module that conflicts with these one. Do you have magisk props hide module? If yes, delete that module. You don't need it with these safetynet patch. And these patch is only for stock rom or stock base roms
Click to expand...
Click to collapse
Yes at that time i have that module but after this problem...i unroot my device
ameer419 said:
Yes at that time i have that module but after this problem...i unroot my device
Click to expand...
Click to collapse
Then root your phone again and only instal this module. I should work. Or flash the boot image again with Odin and root it over twrp recovery
spit85 said:
Then root your phone again and only instal this module. I should work. Or flash the boot image again with Odin and root it over twrp recovery
Click to expand...
Click to collapse
Yeah i m going to root it tomorrow
Just after rooting....do i have to install thia module
Would u like to suggest me to install any other module to pass safety net
ameer419 said:
My sefty net passes but after that i can't access mobile setting
It says the settings has stopped
Click to expand...
Click to collapse
Hi, If u are in RefinedUI 2.0 its a bug but I have already fixed it, check the small updates section of the Refined thread
BlassGO said:
Hi, If u are in RefinedUI 2.0 its a bug but I have already fixed it, check the small updates section of the Refined thread
Click to expand...
Click to collapse
I m on ui2.5
ameer419 said:
I m on ui2.5
Click to expand...
Click to collapse
With RefinedUI?
BlassGO said:
With RefinedUI?
Click to expand...
Click to collapse
Bro I have not so much knowledge about thi....i don't know it's refined or not....how to check
ameer419 said:
Bro I have not so much knowledge about thi....i don't know it's refined or not....how to check
Click to expand...
Click to collapse
I guess you are on stock rom and only unlock the bootloader and rooted the phone. If you have the Samsung galaxy a51, this patch work. If you have another phone model, it's possible that's the reason your phone trips in settings
spit85 said:
I guess you are on stock rom and only unlock the bootloader and rooted the phone. If you have the Samsung galaxy a51, this patch work. If you have another phone model, it's possible that's the reason your phone trips in settings
Click to expand...
Click to collapse
Yes... i have stock rom unlocked bootloader
I will try thi today after rooting because i unroot my phone due to settings has stopped issue
Updater process ended with ERROR 1
Error installing zip file "/external_sd/SafetyNet_Patch_A515_a10-11.zip
or
Updater process ended with ERROR 123
Error installing zip file "/external_sd/SafetyNet_Patch_A515_a10-11.zip
mikola08 said:
It doesn't want to install on android 11
Click to expand...
Click to collapse
Magisk crashes when tapping from "install from storage"
Using
[ROM][A515x] RefinedUI v2.0 [OneUI3.0 - Android11]
[ROM][A515x] RefinedUI v2.0 [OneUI3.0 - Android11]
FEATURES [ 2.0 - REMAKE ] - NDataX replaced with BlueFly (An improved version) - Mixplorer removed (Problems with Google File Manager) - Added the option to remove the Magisk App from the /system (Abnormal State) - The OMC was updated with the...
forum.xda-developers.com
A short splash screen shows up with an blue folder icon.
Any idea how to fix that?
Hello everyone,
After a bit of research, I found out that many people with a OnePlus 9 Pro, myself included, struggled with installing viper4android.
Luckily and accidentally I discovered this GitHub repository!
It all works only with a magisk module installation.
After a reboot you're good to go.
I've tested it on Nameless AOSP 13 with SELinux enforcing.
Users have reported incompatibility with OxygenOS.
Nonetheless you can try and see if it works for you.
Cheers!
WOW
It actually worked, what a godsend. Thank you for this kind sir. I've tried so many methods and this is the solution.
I couldn't get it to work on oos13 ...
ffejy462 said:
I couldn't get it to work on oos13 ...
Click to expand...
Click to collapse
Thank you for the info!!
Just switched to nameless from extended. No worky on nameless
bbortel93 said:
Just switched to nameless from extended. No worky on nameless
Click to expand...
Click to collapse
Try with JamesDSP, it usually has fewer compatibility issues and works just as well as V4A.
bbortel93 said:
Just switched to nameless from extended. No worky on nameless
Click to expand...
Click to collapse
Naah... I'm still on Nameless latest version and it's still working. You must be doing something wrong.
Check the repository's instructions again, although I don't think they are difficult to follow, it's just one module to flash... Also make sure you don't have any other audio mods installed. It's okay if you have the built-in Dolby Atmos.
Installation fails with the following message:
----------------------------------------------------
- Copying zip to temp directory
- Installing ViPER4AndroidFX-repackagedhoch25-1b03ff9.zip
- Current boot slot: _b
- Device is system-as-root
unzip: can't open /data/user/0/vaet.gunkqwa/cache/flash/install.zip[.zip]
! Unable to extract zip file!
! Installation failed
----------------------------------------------------
Anyone tell me what's going on?
tathagatab said:
Installation fails with the following message:
----------------------------------------------------
- Copying zip to temp directory
- Installing ViPER4AndroidFX-repackagedhoch25-1b03ff9.zip
- Current boot slot: _b
- Device is system-as-root
unzip: can't open /data/user/0/vaet.gunkqwa/cache/flash/install.zip[.zip]
! Unable to extract zip file!
! Installation failed
----------------------------------------------------
Anyone tell me what's going on?
Click to expand...
Click to collapse
Do you have SELinux enforcing?
Do you have the latest magisk installed?
Did you flash it through magisk manager?
If the answer is yes, then try again after a reboot,
Else if the error insists, then idk, try reading the repository's instructions carefully.
It also might be that your ROM or ro your Android version is incompatible.
I hope this helps!
David_#27 said:
Do you have SELinux enforcing?
Do you have the latest magisk installed?
Did you flash it through magisk manager?
If the answer is yes, then try again after a reboot,
Else if the error insists, then idk, try reading the repository's instructions carefully.
It also might be that your ROM or ro your Android version is incompatible.
I hope this helps!
Click to expand...
Click to collapse
Yes, turned out that setting selinux to 0 solved it. Thanks for the suggestion. I didn't try it before because the repo instructions said it didn't matter.
Running stock OOS 13 with Magisk 25.2. Let's see if V4A works after the reboot.
[Edit after reboot]
No go, it's the same old "Do you wish to install the driver now" loop
tathagatab said:
Yes, turned out that setting selinux to 0 solved it. Thanks for the suggestion. I didn't try it before because the repo instructions said it didn't matter.
Running stock OOS 13 with Magisk 25.2. Let's see if V4A works after the reboot.
[Edit after reboot]
No go, it's the same old "Do you wish to install the driver now" loop
Click to expand...
Click to collapse
Good to know that it works with SELinux enforcing.
As for OOS, I don't see it working as one user above said it doesn't.
David_#27 said:
Good to know that it works with SELinux enforcing.
As for OOS, I don't see it working as one user above said it doesn't.
Click to expand...
Click to collapse
As I learned, it doesn't work on OOS 13, irrespective of selinux setting. Or at least I couldn't make it work.
For me it works perfectly, using the Pixel Ex rom. Thank you very much!