I've finally figured this out!
This is a scientific breakthrough! Not really... lol
So, I've managed to make SafetyNet pass using a "custom" Magisk build.
I grabbed it from here and so far I've flashed this build and it coaxed SafetyNet into passing. On one treble ROM, ToxycOS, it completely made SafetyNet pass, both ctsProfile and basicIntegrity. On RR official though, it only made basicIntegrity pass. However, that's completely better than nothing at all!
This is how I got SafetyNet to pass completely, it only works if basicIntegrity is passing while ctsProfile if failing.
•Magisk builds: https://github.com/ianmacd/MagiskBuilds
•Magisk I flashed that got SafetyNet to pass: https://github.com/ianmacd/MagiskBuilds/blob/master/Magisk-v16.5-20180621-ianmacd.zip
•Guide to get SafetyNet to pass: https://github.com/phhusson/treble_experimentations/issues/116
Thanks to @topjohnwu for making Magisk possible
Big thanks to @ianmacd for making these Magisk builds
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
crayonicle said:
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
Click to expand...
Click to collapse
yo you can always change the device's fingerprint in order to make safetynet pass using a magisk module
crayonicle said:
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
Click to expand...
Click to collapse
Which version on 16.5 did you use i meant the build date
adb debug working?
huawei p8 lite 2017
phh treble rom gsi vanilla v22
Thanks to everyone but the guy who actually discovered and documented this? Hmph!
It works on BDN-L34
I passed the test successfully following this guide.
I used a Huawei Mate SE (BND-L34) running phusson's [AOSP 8.1 - Phh-Treble] v22. Then downloaded iammacd'smagisk build that the op provided and zip flashed it through TWRP. Then logged on android and uninstalled the magisk manager app (which was an older version) and then downloaded the newest one available and installed it as an apk. After that I opened the app and went to "downloads" and looked for MagiskHide Props, installed the module and rebooted phone. Then as the op did, I followed cawilliamson's instructions on how to set up MagiskHide Props the only difference being that I set up the fingerprint using Huawei mate 9 since Honor 7x were not listed.
I was running and failing at different points the SafetyNet test until I completed the process. Thats it, thanks to crayonicle for research and compiling such great information and to the other people that made it possible. :good:
IonDEfeso said:
I passed the test successfully following this guide.
I used a Huawei Mate SE (BND-L34) running phusson's [AOSP 8.1 - Phh-Treble] v22. Then downloaded iammacd'smagisk build that the op provided and zip flashed it through TWRP. Then logged on android and uninstalled the magisk manager app (which was an older version) and then downloaded the newest one available and installed it as an apk. After that I opened the app and went to "downloads" and looked for MagiskHide Props, installed the module and rebooted phone. Then as the op did, I followed cawilliamson's instructions on how to set up MagiskHide Props the only difference being that I set up the fingerprint using Huawei mate 9 since Honor 7x were not listed.
I was running and failing at different points the SafetyNet test until I completed the process. Thats it, thanks to crayonicle for research and compiling such great information and to the other people that made it possible. :good:
Click to expand...
Click to collapse
Have an Mate 9. What can I do for now? The Magisk-v16.5-20180621-ianmacd.zip dosen´t work for me. It´s bootloped!
chrisaw said:
Thanks to everyone but the guy who actually discovered and documented this? Hmph!
Click to expand...
Click to collapse
I got his permission to post this on Telegram.
Don't worry.
krlosoul said:
adb debug working?
huawei p8 lite 2017
phh treble rom gsi vanilla v22
Click to expand...
Click to collapse
It seems to be. You can always try and test it yourself.
Ashley david said:
Which version on 16.5 did you use i meant the build date
Click to expand...
Click to collapse
2018-6-21
BTW ive just updated to the "MagiskManager-v16.8-2018071902" which is ianmacd's lastest build posted and (first of all isnt bootlooping) and is also passing all of the SafetyNet tests. Also installed the lastest version of the Magisk Manager app 5.8.3 (129) successfully. Not sure if is helpful to report that but since it boot-looped me when I tried to update it last time, so now I consider it an achievement lol. I first uninstalled magisk manager through android uninstall (not the magisk uninstall, which unroots you and delete modules) then installed the new version manually.
-----------------------------------------------------------------------
mcc2005 said:
Have an Mate 9. What can I do for now? The Magisk-v16.5-20180621-ianmacd.zip dosen´t work for me. It´s bootloped!
Click to expand...
Click to collapse
I am no expert but what ROM are you running? I used to have RRO v6 and the boot loping happened to me when I updated magisk to lastest version through the app. Try flashing the older magisk you had before?
If not I think you will have to go back to stock which is what I had to do when that happened to me. I used a stock oreo zip rom for my device (BND-L34) and this guide now since you have the MATE 9 I dont know what the procedures and files needed for that one.
Using a BDN-L34 (Mate SE)
Back to report that I successfully flashed [8.1.0][TREBLE] Pixel Experience [AOSP][r36][2018/07/14] by jhenrique09 (8.1.0-20180714-0200-OFFICIAL) and sucessfully installed the last Magisk version (and app) and passed all the tests (even better it help me bypass the "google uncertified device" messages i was getting). To pass the SafetyNet I downloaded the MagiskHide on the Magisk app "Downloads" then ran a terminal emulator with the following commands.
Code:
su
props
Then only needed to set the fingerprint by doing:
1 > F > * > ** > Y > Y (This last option will make the device reboot, needed to pass SafetyNet, but you can reboot later by writing N)
*Note that you need to select your phones brand in the options given there.
**Select your phone model (or any other model with the same fingerprint reader or compatibility, guess you can try out different models and check if any works, at your own risk though, I dont know if there could be grave repercussions.)
IonDEfeso said:
*Note that you need to select your phones brand in the options given there.
**Select your phone model (or any other model with the same fingerprint reader or compatibility, guess you can try out different models and check if any works, at your own risk though, I dont know if there could be grave repercussions.)
Click to expand...
Click to collapse
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
crayonicle said:
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
Click to expand...
Click to collapse
Yeah I selected honor 9 for my Mate SE, I just mentioned that since I dont know how serious would it be the implications of selecting a totally different model for another phone but yeah just didn't wanted to tell people to select whatever and then suddenly their fingerprint isn't working or something like that haha. Btw i used the same guide you provided the first time i did everything he pointed but then realized that only the first step was enough so only did that.
steven360 said:
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
Click to expand...
Click to collapse
I did it on a Moto G5 with the latest Viper OS Oreo release, it doesn't work, can you help me please?
HourlongTuna5 said:
I did it on a Moto G5 with the latest Viper OS Oreo release, it doesn't work, can you help me please?
Click to expand...
Click to collapse
I'm afraid that this fix might be for Huawei only (no proof yet), maybe perhaps you can try with a similar moto phone?
Related
Does someone successed to install magisk on his mate 10 ?
(Magisk is a systemless root. Magisk root is not visible by safetynet. So you can install netflix, use google pay, etc. with a rooted phone)
I have tried with the magisk manager on rooted rom => failed
I have tried with the zip file (we can do that with a modified recovery but it's annoying) => failed
I have tried with adb and fastboot to generate a flashable boot.img => bootloop
Someone have an idea for Magisk ?
I'm guessing Huawei disabled Loop device support for all Oreo firmware (doesn't work on Mate 9 Oreo either), regardless of device. You could build your own kernel using mate 10 kernel source and enable loop devices.
Magisk need loop support to install. SuperSU can do system-install as well so it will install even if loop devices are disabled (need to edit so it finds RAMDISK instead of BOOT).
I sucessfully installed magisk on mine using this method:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
JediRemi said:
I sucessfully installed magisk on mine using this method:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
Wow, you haven't noticed that the last post in this thread is from December? Magisk can be easily installed now without crazy steps ?
Sent from my HUAWEI BLA-L29 using XDA Labs
DeeZZ_NuuZZ said:
Wow, you haven't noticed that the last post in this thread is from December? Magisk can be easily installed now without crazy steps
Click to expand...
Click to collapse
I had, the problem is that when googling it, this post comes first with a bunch of other non-relevant results (Magisk for mate 10 pro).
I wasted a lot of time trying to adapt the mate 10 pro method to the mate 10 (but couldn't find a stock ramdisk image for my mate 10).
So to save time for people coming after me, I thought it would be good to point them directly to the right thread.
JediRemi said:
I had, the problem is that when googling it, this post comes first with a bunch of other non-relevant results (Magisk for mate 10 pro).
I wasted a lot of time trying to adapt the mate 10 pro method to the mate 10 (but couldn't find a stock ramdisk image for my mate 10).
So to save time for people coming after me, I thought it would be good to point them directly to the right thread.
Click to expand...
Click to collapse
Oh yeah I remember the mate 10 (non-pro) having problems with such things. Then it is good yea
Sent from my HUAWEI BLA-L29 using XDA Labs
DeeZZ_NuuZZ said:
Wow, you haven't noticed that the last post in this thread is from December? Magisk can be easily installed now without crazy steps ?
Click to expand...
Click to collapse
Where do I look to install magisk without crazy steps? ?
tboy2000 said:
Where do I look to install magisk without crazy steps? ?
Click to expand...
Click to collapse
Get TWRP and flash latest magisk beta
For many people hwota method or so didn't work, don't ask me why. But flashing TWRP, even though hwota should work then too and then flashing magisk beta zip works fine.
But if someone wants to flash an OTA, be sure to flash back ramdisk_recovery
Sent from my HUAWEI BLA-L29 using XDA Labs
Lock this thread.
Is the magisk zip only for mido? Or is it generic as well?
I only have mido for testing , but it should be universal. I should build an image with su for treble devices without twrp, I guess.
An alpha build of twrp is available for the Honor 9 lite. I'll test in the next 24 hrs and report here.
Working on any Treble supported device right?
It should work on any device phh-treble works.
Would you be interested in adding fixes for the Huawei mate 10 pro ?
I could try to play the guinea pig.
Maybe a secondary flashable zip / kernel would do the job as not much has to be fixed...
Have you tried the current build? I would like to know the issues with huawei treble devices.
pchatzop said:
Have you tried the current build? I would like to know the issues with huawei treble devices.
Click to expand...
Click to collapse
Downloading mate. I will flash with my p10+. Btw, im using carbon rom atm.
Work on mido.
Bootloops on my Huawei P Smart. Phh's V12 ROM works Ok though.
Good to know. It may be a problem with dm-verity, will patch it on the next build.
pchatzop said:
Good to know. It may be a problem with dm-verity, will patch it on the next build.
Click to expand...
Click to collapse
Booted with my p10+ but every I reboot got this mate.
pchatzop said:
Good to know. It may be a problem with dm-verity, will patch it on the next build.
Click to expand...
Click to collapse
Likewise, the ROM cannot be charge when turnoff same with treble (boot you in recovery mode). However, you may check carbon rom of honor view 10 as it can be charge when turnoff (also, the supercharge is enable when off)
Anyone tested on Redmi 3s
Just installed it on my Mido with nano GApps and provided Magisk, running fine for now, will test on!
Thank you very much for your work, for some Reason I can't use Thanks Button the last days but feel thanked and hugged for that you, Sir, made my Day!
pchatzop said:
Have you tried the current build? I would like to know the issues with huawei treble devices.
Click to expand...
Click to collapse
Can I simply replace my actual LineageOS build with yours ?
I got many things running in a way I can keep it as a daily driver and I sadly can't make a TWRP backup as TWRP can't decrypt our device for the moment.
ChriKn said:
Can I simply replace my actual LineageOS build with yours ?
I got many things running in a way I can keep it as a daily driver and I sadly can't make a TWRP backup as TWRP can't decrypt our device for the moment.
Click to expand...
Click to collapse
May cause you bootloop. Better backup your data/files. I used titanium backup :good:
v0ne said:
May cause you bootloop. Better backup your data/files. I used titanium backup :good:
Click to expand...
Click to collapse
I just have gotten a working phone after 3 days of work, I prefer to keep it this way
But once TWRP backups are feasible, I will of course try this
ChriKn said:
I just have gotten a working phone after 3 days of work, I prefer to keep it this way
But once TWRP backups are feasible, I will of course try this
Click to expand...
Click to collapse
If you're using the Treble LOS right now, you will not find anything in this Rom that will not work for you, I think.
Been using it for a few hours and no Problems popped up!
Set up with
opengapps (Mini), Magisk from OP and Pixel2 Experience Module.
Battery seems to be good for now, all Basics like WhatsApp, GMail, Messenger, Maps (GPS), Spotify with Bluetooth Car Audio (excellent sound), Mi Band 1s do work. And it has March Security Patch.
Of course it's just a few hours but till now, it's just awesome!
Hi all,
I just modified the module from @snowwolf725 to have a newer template so it can run on oreo rom
If you need to use nfc-sim on oneplus 3/3t you could try this module.
[Install]
1. Get Magisk
2. In the download area search for "OnePlus 3/t NFC Sim Enabler"
3. Reboot
4. If your manage app require permission you can give it at settings-apps-app permissions-additional permissions, toggle smartcardservice for it
I only test it on OOS Oreo ROM, it may not work on custom rom due to different framework built in.
You can report here so I'll check what other MOD have to add to make other ROM work.
the smartcardservice is modified from SEEK for Android by Johnzweng
Repo link
crazymika said:
Hi all,
I just modified the module from @snowwolf725 to have a newer template so it can run on oreo rom
If you need to use nfc-sim on oneplus 3/3t you could try this module.
[Install]
1. Get Magisk
2. In the download area search for "OnePlus 3/t NFC Sim Enabler"
3. Reboot
4. If your manage app require permission you can give it at settings-apps-app permissions-additional permissions, toggle smartcardservice for it
I only test it on OOS Oreo ROM, it may not work on custom rom due to different framework built in.
You can report here so I'll check what other MOD have to add to make other ROM work.
the smartcardservice is modified from SEEK for Android by Johnzweng
Repo link
Click to expand...
Click to collapse
Any chance that this mod used on htc m9 with aicp 13.1, rooted with magisk?
tombbb said:
Any chance that this mod used on htc m9 with aicp 13.1, rooted with magisk?
Click to expand...
Click to collapse
I don't think so, it's NFC chip specified so if you have a different device it's xml config would be different.
For m9 you could look through it's stock rom to adjust configuration, I believe the M9 stock ROM support NFC-SIM card.
What does nfc sim means?
prasant737 said:
What does nfc sim means?
Click to expand...
Click to collapse
In some places we have our payment/transportation card integrated in SIM card.
so we can use our phone to pay/take public transportation.
hi sir able to update it for oneplus 6t android pie?
laocheebye said:
hi sir able to update it for oneplus 6t android pie?
Click to expand...
Click to collapse
according your ID I assume you are Taiwanese, there is modification for oneplus 6 on mobile01, i think that will also work for 6t
I didn't have 6t so I can't test on it.
crazymika said:
according your ID I assume you are Taiwanese, there is modification for oneplus 6 on mobile01, i think that will also work for 6t
I didn't have 6t so I can't test on it.
Click to expand...
Click to collapse
i am singaporean actually. can u link me the thread? i can read chinese so its fine. thank you deep deep.
---------- Post added at 02:27 PM ---------- Previous post was at 02:12 PM ----------
i found the thread and the download link if anyone is interested to try for oneplus 6 or 6t.
forum link in chinese
flashable zip
i havent tried cos there is no decrypt twrp for 6t yet so at your own risk people.
I had asked about it to the author directly on github since since my test are not successful. No update since then...
https://github.com/Magisk-Modules-Repo/oneplus3simnfc/issues/2
NoobZik said:
I had asked about it to the author directly on github since since my test are not successful. No update since then...
https://github.com/Magisk-Modules-Repo/oneplus3simnfc/issues/2
Click to expand...
Click to collapse
I'll update this to pie compatible when oos pie released
crazymika said:
I'll update this to pie compatible when oos pie released
Click to expand...
Click to collapse
Hello, any news ?
Hi, just tried the latest v1.2.1, but it seems HamiPay detects root even MagiskHide enabled for it. Would you please share how to prevent HamiPay from detecting root? Thank you.
jekyll530 said:
Hi, just tried the latest v1.2.1, but it seems HamiPay detects root even MagiskHide enabled for it. Would you please share how to prevent HamiPay from detecting root? Thank you.
Click to expand...
Click to collapse
I think they changed the root detection, now it's can only use with iPASS, EasyCard or icash.
Creditcard function have been lock with rooted devices.
crazymika said:
I think they changed the root detection, now it's can only use with iPASS, EasyCard or icash.
Creditcard function have been lock with rooted devices.
Click to expand...
Click to collapse
Thank you for replying. The above seems work fine. Can this module be ported for OP5/T, 6/T (OOS 9.0) or even 7/Pro?
Cuvillier said:
Hello, any news ?
Click to expand...
Click to collapse
I've update to Pie rom, and confirm that we still can use sim NFC at it, just need some path adjustments, use the attached zip file replace your system/vendor/etc/libnfc-nxp.conf, put the SmartcardService folder in system/priv-app folder
add this line "persist.nfc.smartcard.config=SIM1,eSE1" in system/build.prop file, and should work as before.
I forgot how to make it into proper Magisk Module~the module i made tonight can't not be installed.... so strange. I'll update once i get it to work.
P.S.
I tried custom ROMs, they have many differences about NFC config, I can not get it to work even replace the framework and permission file, tried everything I know but still failed, maybe they missed something at more lower level.
updated for OOS Pie
I just found what's wrong.
Here's the updated Module for OOS Pie.
Later i'll update to Modules-Repo
jekyll530 said:
Thank you for replying. The above seems work fine. Can this module be ported for OP5/T, 6/T (OOS 9.0) or even 7/Pro?
Click to expand...
Click to collapse
@snowwolf725 have created the OP5 module, 6/6t have other method to make it working,but I need check some of it's file to make sure, op7 should work in theory, but it still depend on some rom configuration. I only have a op3t, do don't know how other models work.
Currently OOS have proper components (driver, config, frameworks...) installed, so it easier to enable them, for custom rom or future builds(which OP3 won't have)
I believe that require more adjustments to have this feature working.
crazymika said:
@snowwolf725 have created the OP5 module, 6/6t have other method to make it working,but I need check some of it's file to make sure, op7 should work in theory, but it still depend on some rom configuration. I only have a op3t, do don't know how other models work.
Currently OOS have proper components (driver, config, frameworks...) installed, so it easier to enable them, for custom rom or future builds(which OP3 won't have)
I believe that require more adjustments to have this feature working.
Click to expand...
Click to collapse
The OP5/T module is not available via Magisk download now. I'm currently using OP5 and will buy a 7 Pro. If you need, I can help testing.
crazymika said:
@snowwolf725 have created the OP5 module, 6/6t have other method to make it working,but I need check some of it's file to make sure, op7 should work in theory, but it still depend on some rom configuration. I only have a op3t, do don't know how other models work.
Currently OOS have proper components (driver, config, frameworks...) installed, so it easier to enable them, for custom rom or future builds(which OP3 won't have)
I believe that require more adjustments to have this feature working.
Click to expand...
Click to collapse
thanks but it doesn't work on lineage os 16. in logcat i get keymaster operation failed and unsupported digest on km1 hal issue. i hope you can fix it
regards
Mod Edit:
Thread closed due to no link provided, as well as rude, disrespectful OP statement.
So apart from F/DS devices, would it work on a N?
How about vendor, is it included?
Thanks
bober10113 said:
So apart from F/DS devices, would it work on a N?
How about vendor, is it included?
Thanks
Click to expand...
Click to collapse
I don't believe it would work on an N because the firmware I used is specifically for an F/DS device. Has it even been released on the N yet?
The vendor needed for Android Pie *is* included, as is modem, kernel, etc.
chrisaw said:
I don't believe it would work on an N because the firmware I used is specifically for an F/DS device. Has it even been released on the N yet?
The vendor needed for Android Pie *is* included, as is modem, kernel, etc.
Click to expand...
Click to collapse
Usually Fs and Ns are identical hardwarewise except system partition size is a tad smaller I believe.
I'll give it a shot and report back.
edit:
i checked script and bootloader and mdem are being flashed wich is a big no no for N devices.
plus as i can see there have been a complaint so...
chrisaw said:
If anyone takes offence to this ROM for any reason - please let me know and I'll take it down immediately.
Click to expand...
Click to collapse
Yes I have objection.
You can not use my modified images. You want to make your own then there is one thread in geneneral section. Get pie beta on your device and then dump it yourself.
Its my request to remove my work and meanwhile you make your own, remove the link.
chrisaw said:
Description
I really love this new Android 9.0 beta from Samsung with the One UI. I also really love DevBase!
With that in mind - I've created PieBase which is simply a combination of:
- Latest DevBase release (from here - thanks _alexndr)
- Latest Magisk release (from here - thanks topjohnwu)
- Latest Samsung Pie firmware (from here - thanks drketan)
If anyone takes offence to this ROM for any reason - please let me know and I'll take it down immediately. As soon as official DevBase is released - I'll remove this post and direct any visitors to his thread. I'm not even remotely interested in stealing people away from DevBase - it's an awesome ROM - just looking to fill the void for now.
SafetyNet Pass
In order to get SafetyNet to pass with Magisk you will need to:
Download Busybox magisk module
Download MagiskHide Props Config magisk module
Reboot your device
Download and open a terminal app of your choice
Switch to root by entering the "su" command
Enter "props" then enter: 1, f, 13, 24, y, y
Once your device has done rebooting - you should now be passing SafetyNet. The reason this is needed is simply because beta versions of Samsung ROMs never pass SafetyNet so we're claiming to be an 8.0 running device to Google so they'll pass us as running a known Samsung ROM.
Warnings
App names and dependencies have changed around a lot in this release so your old configs likely wont work!
You are welcome to try to attempt to dirty flash this ROM but it's VERY likely you will need to clean flash (sorry!)
If you have a /sdcard/devbase directory - rename this before flashing.
If you have a /sdcard/options.prop file - rename this before flashing.
This ROM is for F/DS ONLY!!!
Download
Mod Edit: Link removed
Click to expand...
Click to collapse
Hi. Ur rom is almost copy of Dr. Ketan rom. Does not sounds legitimate. Suggest u to rethink & close the thread.
Sent from my SM-N960F using XDA-Developers Legacy app
(First time posting here please correct me if this is in the wrong place)
Hello
I have recently rooted my Pixel 2 XL with TWRP and Magisk and wanted to install Viper4Android. But when i try to install the drivers it stops and I get the message
"Installation failed at patching system"
I have the audio modification Library and also got it working on Android 10 before but 11 doesn't work right now.
My question is:
Has anybody already installed V4A on Android 11 successfully and knows a way to do it or will I have to wait for the official release and an updated V4A?
Unfortunately I have the same error with Pixel 2 XL and android 11 (also worked with 10).
I also tried "tricky" install procedures (like this: https://www.the***********.com/install-viper4android-android-10-guide/) but no success yet.
I think the issue is related to Magisk canary and only happens on Pixel 2 (and XL) devices with android 11.
viper4android & Android 11
I have the same issue as well..
Can't get anyone to answer, been to several site, asking the same question
R3vation said:
(First time posting here please correct me if this is in the wrong place)
Click to expand...
Click to collapse
The following thread will get the eyes of most people using Viper
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
R3vation said:
I have recently rooted my Pixel 2 XL with TWRP and Magisk and wanted to install Viper4Android. But when i try to install the drivers it stops and I get the message
"Installation failed at patching system"
I have the audio modification Library and also got it working on Android 10 before but 11 doesn't work right now.
My question is:
Has anybody already installed V4A on Android 11 successfully and knows a way to do it or will I have to wait for the official release and an updated V4A?
Click to expand...
Click to collapse
A logcat of the install process would be my starting point. You also do not specify which version of Magisk you are using? If you wish to respond to me, use the above thread, but there will be people with a lot more targeted understanding of your issues on that thread.
DiamondJohn said:
The following thread will get the eyes of most people using Viper
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
A logcat of the install process would be my starting point. You also do not specify which version of Magisk you are using? If you wish to respond to me, use the above thread, but there will be people with a lot more targeted understanding of your issues on that thread.
Click to expand...
Click to collapse
I'm also having same problem on pixel 4 XL and it's the new Android and magisk and also the way viper4android installation works i talked to dewitt and he say he will work on that as soon as he knows what changed in magisk
Scytherblack said:
I'm also having same problem on pixel 4 XL and it's the new Android and magisk and also the way viper4android installation works i talked to dewitt and he say he will work on that as soon as he knows what changed in magisk
Click to expand...
Click to collapse
Same for P4. Let me know that he says?
Xdevillived666 said:
Same for P4. Let me know that he says?
Click to expand...
Click to collapse
Yes sir that's only reason i switched back to Android 10 and Dewitt said he dont have no Android 11 running device to test so we'll just wait until android 11 is stable os and they release it for more device
I reckon we'll just need to be patient until the Devs look at compatibility upgrade for Android 11 - that has now been officially released. Everything works for me on my freshly rooted P4XL running R11, apart from V4A. But V4A is my most loved root app (next to Adblock, of course)
@R3vation
I have recently rooted my Pixel 2 XL with TWRP and Magisk and wanted to install Viper4Android. But when i try to install the drivers it stops and I get the message
"Installation failed at patching system"
Click to expand...
Click to collapse
In Magisk grant Viper4Android root permission, then all is good.
jwoegerbauer said:
@R3vation
In Magisk grant Viper4Android root permission, then all is good.
Click to expand...
Click to collapse
Tried that - few times now, no joy...
There might be hope...
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
SirAugustine said:
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
Click to expand...
Click to collapse
Works for me as well
SirAugustine said:
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
Click to expand...
Click to collapse
Thanks mate
Same issue on Android 11 on my Oneplus 8 Pro. Would love an answer, or an alternative to Viper for the time being. Its one thing I can't seem to live without.
SirAugustine said:
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
Click to expand...
Click to collapse
Can anyone confirm the safety of this file? Ichigo Kywrosaki is an anime character
State.of.mind said:
Can anyone confirm the safety of this file? Ichigo Kywrosaki is an anime character
Click to expand...
Click to collapse
The customize.sh is completely different, as well as the module.prop. They use completely different install methods.
This unofficial build seems to install the app as a system app, while the official module installs it as a user app. As a result, permissions are granted in a system-level config file, though none look suspicious.
I haven't compared APK files, so I don't know anything about the actual app code.
The only thing that I consider mildly suspicious is the fact that the app copies native audio library binaries into certain locations; these could potentially be malicious. I doubt that they are, though.
After installing this, my Pixel 3a has been randomly reporting 'missing codec' when attempting playback of FLAC files via MediaMonkey.
I also recently got the TRN BT20S bluetooth adapters for my IEMs, could be the intersection of the two, will keep testing.
Restart usually clears things up, but not the best solution.
I'm missing something, how do you download this form the link?
BracesForImpact said:
I'm missing something, how do you download this form the link?
Click to expand...
Click to collapse
Click the description of the video and there is a google drive link to dload it from
JackRandalt said:
This is why I never use Viper. I prefer Whatsapp. It never has such issues.
Click to expand...
Click to collapse
Wut? Whatsapp is a message app.