As the title says, has anyone managed to get it to work?
I've tried various methods suggested elsewhere and on the Pixel 4XL forum which involved using the Audio Compatibility and Audio Modification Libs, but none of them has worked. Always ends up booting to the Fastboot screen and that is it.
Have to use ADB to remove the modules to get the phone to boot again.
People seem to have managed to get it to work on the Pixel 4 which also comes with android 10 out of the box, so I would have though it should work on the 7T and 7T Pro.
Has anyone got a method to make it work?
If not, has anyone managed to get JamesDSP to work?
Thanks
I'm in the same boat. Phone stuck at bootloader unlocked warning when I install the driver. I've tried the normal, legacy, xhifi and rootless and nothing works.
Starting to think something it's something with oxygenOS...
Sent from my OnePlus7TPro using XDA Labs
Thanks for your reply.
I thought the same, but there are people on the OP7 Pro on OOS 10 that have got it to work.
So i thought maybe its just devices that ship with Android 10 out of the box with the new partitioning etc, but Pixel 4 XL users seem to have to got it to work (using some workarounds).
So to me it looks like it is only Oneplus devices that ship with OOS 10 out of the box. OP7T seems to be in the same boat.
If I'd known this was going to be a problem I would have ordered the OP7 Pro instead. Too late now though.
Hopefully someone will figure this out. Viper is the only reason I root.
Thanks
I've replied to main Viper thread to see if anyone has any ideas
chiiiiiiippppppp said:
I've replied to main Viper thread to see if anyone has any ideas
Click to expand...
Click to collapse
I think we have to wait until developers to properly update the app. Until then, not much to do until then.
Sent from my OnePlus7TPro using XDA Labs
Removed duplicate
chiiiiiiippppppp said:
By following the below advice on the main Viper thread:-
============================
Remove service.sh (v4a 2.3.x) or post-fs-data.sh (newer ver.) from /data/adb/modules/(v4a folder) if it's stuck at Bootlogo
============================
I have now got past the stuck at fastboot screen after installing the driver. The driver says it is installed but will not process.
Perhaps I need to make it a system app, or maybe install the rootless version of the driver.
Click to expand...
Click to collapse
chiiiiiiippppppp said:
chiiiiiiippppppp said:
By following the below advice on the main Viper thread:-
============================
Remove service.sh (v4a 2.3.x) or post-fs-data.sh (newer ver.) from /data/adb/modules/(v4a folder) if it's stuck at Bootlogo
============================
I have now got past the stuck at fastboot screen after installing the driver. The driver says it is installed but will not process.
Perhaps I need to make it a system app, or maybe install the rootless version of the driver.
Click to expand...
Click to collapse
Yep, I followed to this.
My viper says abnormal status and is not processing, installing the rootless version did nothing for me unfortunately.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Got it working
After days of trying numerous different ways I've finally managed to get Viper to work my Oneplus 7T Pro
First I removed the any previous Viper module in Magisk and rebooted.
I then uninstalled the Viper App and rebooted again.
So I then had a clean starting point.
I installed The SELinux Switch app from XDA to set SELinux mode to Permissive:-
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
I turned off Google Play Protect.
I then installed the version 2.7.1.0 module in Magisk.
Installed driver and it rebooted.
Stuck at Fastboot screen.
Reboot to Recovery
I then did the following in adb to delete the post-fs-data.sh file which is the file that stops the phone booting.
1) adb shell
2)cd to /data/adb/modules/ViPER4AndroidFX
3)rm post-fs-data.sh
4)exit
reboot to Fastboot and then Start
Then it just worked.
After a subsequent reboot I has to try a few things to get it to work again. e.g. close Viper and music app and then open SELinux Switch and then start Viper again.
After a 2nd reboot it just seemed to work.
I think it might be a timing thing where you have to wait for SELinux Switch to get granted Root before trying Viper.
Anyway I'm a very happy chappy.
Hopefully this will help others get it working.
Finally, got it working with your method!
Will be listening to lots of music tonight, thanks!
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Finally, got it working with your method!
Will be listening to lots of music tonight, thanks!
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Thanks, now you confirmed that it works as well, then I will create a Guide post and link it in the 7T forum and the main Viper thread.
chiiiiiiippppppp said:
Thanks, now you confirmed that it works as well, then I will create a Guide post and link it in the 7T forum and the main Viper thread.
Click to expand...
Click to collapse
I don't think this works for the 7T because you need a modded stock recovery with adb in order to remove post-fs-data file. Which I think you should also mention in the guide,
Lossyx said:
I don't think this works for the 7T because you need a modded stock recovery with adb in order to remove post-fs-data file. Which I think you should also mention in the guide,
Click to expand...
Click to collapse
Good point.
I'll update the guide post and the 7T post.
Thanks
I wanna do this on the 7t . I have magisk and elementalx kernel running. I hope I won't have to wipe my stuff
chiiiiiiippppppp said:
Good point.
I'll update the guide post and the 7T post.
Thanks
Click to expand...
Click to collapse
THREAD CLOSED! If interested in this subject, please follow this thread: https://forum.xda-developers.com/7t-pro/themes/installing-viper4android-t4001045
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse
Related
Systemless Root
Read this first: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
To summarize:
This is an experimental root process
[*]It needs an unlocked bootloader
[*]It needs the system to have no trace of any other superuser solutions
[*]This will patch the kernel RAMDisk to include the su binary
[*]Following that, all calls to execute commands as root will be handled from here
[*]This means no system partition modification
[*]This also means Android Pay works
[*]Since this is experimental, expect apps with hardcoded su calls to not work (blame the app developer)
[*]Also, there are bugs as Chainfire stated but it's been stable up until now
[*]I have not tried this on the XT1572 but it should work
Click to expand...
Click to collapse
IMPORTANT!
You need to revert to completely stock/clean marshmallow without any SuperSU installed.
Installation Instructions:
Install the kernel patch - systemless_root.zip
Install SuperSU (systemless) - SuperSU v2.56
DO NOT INSTALL ANY OTHER SUPERSU MODULES
IGNORE ANY TWRP MESSAGES ABOUT SUPERSU or SU in general
XDA:DevDB Information
[Beta][Marshmallow/6.0][XT1575/1572] Systemless Root, Tool/Utility for the Moto X Style (Pure)
Contributors
alnikki25k
Version Information
Status: Testing
Current Beta Version: 1
Beta Release Date: 2015-12-04
Created 2015-12-04
Last Updated 2015-12-23
Reserved
Reserved
Aaaand....ignore this post.
XDA discourages place holder threads. Without a download link, this will probably be shut down pretty soon.
Sent from my XT1575 using Tapatalk
Yeah...really should tidy up your instructions. Tons of stuff to wade through in that link thread. No "clark" for our phone. Also, a layman's, two-sentence overview of what this is and does may be helpful to many. Thanks!
joshw0000 said:
XDA discourages place holder threads. Without a download link, this will probably be shut down pretty soon.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
And I definitely jumped to a conclusion I shouldn't have.
brholt6 said:
Will there be a download in this thread (curious because I don't see a .zip for our phone in the linked thread) or just a link to @Chainfire's thread?
Click to expand...
Click to collapse
joshw0000 said:
XDA discourages place holder threads. Without a download link, this will probably be shut down pretty soon.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
hijax2001 said:
Yeah...really should tidy up your instructions. Tons of stuff to wade through in that link thread. No "clark" for our phone. Also, a layman's, two-sentence overview of what this is and does may be helpful to many. Thanks!
Click to expand...
Click to collapse
brholt6 said:
I'd say especially when you list yourself as the only contributor and just link to someone else's work. Who knows, maybe he created the .zip we need for the 1575/1572 and he's uploading it now? I suppose I shouldn't jump to conclusions.
Click to expand...
Click to collapse
Wow. Aren't you guys all respectful? This is a DevDB thread. The link was up in the Downloads section. For some reason my post edits/links didn't go through. Maybe check once before you fire all guns?
alnikki25k said:
Wow. Aren't you guys all respectful? This is a DevDB thread. The link is up in the Downloads section. For some reason my post edits didn't go through. Maybe check once before you fire all guns?
Click to expand...
Click to collapse
Apologies...as you know, many people try to get credit for work they didn't do (I'm obviously not a fan of that and let it get the best of me). It just looked odd since there was only a link to the original thread until just now. Again, apologies for jumping to conclusions and thanks for the work.
I couldn't find any info anywhere how does systemless root benefit vs regular root by using the modified boot image? thanks!
brholt6 said:
Apologies...as you know, many people try to get credit for work they didn't do (I'm obviously not a fan of that and let it get the best of me). It just looked odd since there was only a link to the original thread until just now. Again, apologies for jumping to conclusions and thanks for the work.
Click to expand...
Click to collapse
Yeah. I get that. Don't worry about it.
alnikki25k said:
Wow. Aren't you guys all respectful? This is a DevDB thread. The link was up in the Downloads section. For some reason my post edits/links didn't go through. Maybe check once before you fire all guns?
Click to expand...
Click to collapse
Sorry about that. I saw [WIP] as the thread title and no download links in the OP and assumed this was another "I'm first to start working on it but have nothing to share" thread that pop up all over XDA and immediately get closed.
patt2k said:
I couldn't find any info anywhere how does systemless root benefit vs regular root by using the modified boot image? thanks!
Click to expand...
Click to collapse
From what I understand it allows you to root your phone without making any modifications to /system. So when a OTA is released you flash the stock kernel and accept the OTA. This assumes you've made no changes to /system once you gained root.
Sent from my XT1575 using Tapatalk
It's working great, I had to reinstall superSU from the play store as it was not showing up in the app drawer. Everything is working.
@alnikki25k BTW. Congratulation on the brilliant idea and implementation of a script that make the systemless root changes to the kernel, could this be used with another device?
Can I use this with the stock odexed (unrooted) from here:
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
Thanks, great work!
Note 3 Chicago said:
Can I use this with the stock odexed (unrooted) from here:
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
Click to expand...
Click to collapse
That's my question too.. Downloading the stock no root version.. Hoping for the best
---------- Post added at 02:45 PM ---------- Previous post was at 01:46 PM ----------
Note 3 Chicago said:
Can I use this with the stock odexed (unrooted) from here:
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
Click to expand...
Click to collapse
worked so far.. flashed the stock odexed no root. rebooted and did quick gmail setup. Went back to TWRP and flashed the files for the kernel and SuperSU. When prompted by TWRP to install SuperSU after flashing the files I said do not install per instructions. Booted up and restoring with titanium as I type.
Next question would be if anyone was able to get xposed working with systemless root? Probably not going to take that plunge since I got root mainly for titanium and ad blocker.
Edit. All apps back. Running good. Not trying xposed yet. Android pay loaded no problem. Added cards no problem. Doing good so far
Tested on XT1572 , everything works flawlessly except es file explorer unable to request for su permission for some reason.
Thanks again for this
bgos10 said:
Tested on XT1572 , everything works flawlessly except es file explorer unable to request for su permission for some reason.
Thanks again for this
Click to expand...
Click to collapse
Yep, ES Explorer does not work with systemless root, change to Solid Explorer that works well.
Thanks for this, now I have android Pay working properly.
BTW: good ole root explorer still works.
wctaylor79 said:
Next question would be if anyone was able to get xposed working with systemless root? Probably not going to take that plunge since I got root mainly for titanium and ad blocker.
Edit. All apps back. Running good. Not trying xposed yet. Android pay loaded no problem. Added cards no problem. Doing good so far
Click to expand...
Click to collapse
Xposed working fine on Moto X XT1572 Indian Version
MORFUZ KERNEL FOR P10 LITE OREO
:good: Hi guys, this kernel perfectly works also on our device. Works at HONOR 7X
https://forum.xda-developers.com/p10-lite/development/kernel-p10-lite-catuva21-t3798915
Feodorus 4PDA said:
MORFUZ KERNEL FOR P10 LITE OREO
:good: Hi guys, this kernel perfectly works also on our device. Works at HONOR 7X
https://forum.xda-developers.com/p10-lite/development/kernel-p10-lite-catuva21-t3798915
Click to expand...
Click to collapse
can you overclock?
zooyork8998 said:
can you overclock?
Click to expand...
Click to collapse
I can't tell I didn't try
Trying to figure out best settings, I agree kernel works great.
in the OP says he has Selinux permissive, then it is possible that viperaudioFX work?
rafi1123 said:
in the OP says he has Selinux permissive, then it is possible that viperaudioFX work?
Click to expand...
Click to collapse
Isn't that line edited , to say "missing"
Because permissive it not working
Will this work on treble GSI?
works for me on Stock Emui 8
Work on my custom ROM !
But there are problems with deepsleep with some governor
Can someone send me the stock kernel of bnd l21 ?
Well Ok it works, but how to get back to stock kernel.
lalitkhokhar said:
Well Ok it works, but how to get back to stock kernel.
Click to expand...
Click to collapse
Supposed to have made backup of kernel before flashing. Did you do?, Then just restore that backup.
I just tried flashing this with magisk and it said it installed, but is there an easy way to actually tell if it worked? I'm just trying to get viper4android to work to hopefully get around the dreadfully quiet headphone volume.
TiklMiPickles said:
I just tried flashing this with magisk and it said it installed, but is there an easy way to actually tell if it worked? I'm just trying to get viper4android to work to hopefully get around the dreadfully quiet headphone volume.
Click to expand...
Click to collapse
Go to settings, about phone - half way down it has kernal info
There's been some concerns on viper4 on customs roms causing bootloops -
Theres a dolby and a sony audio improvement zip to flash as well - i don't have links but try the telegram groups
nickzeptepi said:
Go to settings, about phone - half way down it has kernal info
There's been some concerns on viper4 on customs roms causing bootloops -
Theres a dolby and a sony audio improvement zip to flash as well - i don't have links but try the telegram groups
Click to expand...
Click to collapse
Thanks! Looks like it did install, but for some reason, the viper4android driver just won't install. Every time I open the app it keeps having me reinstall it, then when I reboot it just says I need to install it again. I'm wondering if it's specific to honor or the 7x since I can't seem to find anyone who's having similar issues.
TiklMiPickles said:
Thanks! Looks like it did install, but for some reason, the viper4android driver just won't install. Every time I open the app it keeps having me reinstall it, then when I reboot it just says I need to install it again. I'm wondering if it's specific to honor or the 7x since I can't seem to find anyone who's having similar issues.
Click to expand...
Click to collapse
they might not have similar problems cos they are not installing it.
Try find the dolby and sony sound things. - look also on mate 10 forums as its the same hardware
nickzeptepi said:
they might not have similar problems cos they are not installing it.
Try find the dolby and sony sound things. - look also on mate 10 forums as its the same hardware
Click to expand...
Click to collapse
It looks like the mate 10 is having the same issues, but after trying my headphones with the new kernel, it looks like the gain isn't limited to a super low volume like it was before! I'm not sure if this is just a placebo effect or if it actually solved the headphone volume issue, but I am hoping that was the fix I needed.
Has anyone tried this on Mate SE?
---------- Post added at 01:04 PM ---------- Previous post was at 12:47 PM ----------
TiklMiPickles said:
Thanks! Looks like it did install, but for some reason, the viper4android driver just won't install. Every time I open the app it keeps having me reinstall it, then when I reboot it just says I need to install it again. I'm wondering if it's specific to honor or the 7x since I can't seem to find anyone who's having similar issues.
Click to expand...
Click to collapse
Did you ever get V4A to work? Did you go into settings in the app and in Developer Mode select the Disable SELinux mode?
MikeyLee said:
Has anyone tried this on Mate SE?
---------- Post added at 01:04 PM ---------- Previous post was at 12:47 PM ----------
Did you ever get V4A to work? Did you go into settings in the app and in Developer Mode select the Disable SELinux mode?
Click to expand...
Click to collapse
Tried that, but it didn't work. I tell it to turn off Selinux, let it install the driver, then reboot the phone, and as soon as I reboot it and open the app again, it says the driver isn't installed
TiklMiPickles said:
Tried that, but it didn't work. I tell it to turn off Selinux, let it install the driver, then reboot the phone, and as soon as I reboot it and open the app again, it says the driver isn't installed
Click to expand...
Click to collapse
Have you tried any of the suggestions on the v4a xda thread. Like removing the stock audio overlay (xml) file first.
I keep seeing people say it will not work because selinux, or because of 64 bit drivers, then you go look at the xda thread, and see many (some) people saying it works for them.
If you are having the permissive setting working correct, then tell me if the guide on this link is working?
https://www.the***********.com/install-viper4android-on-android-oreo/
First of all READ THE WHOLE OP, PLEASE. Also pay attention to the "PS" at the bottom of this post.
(This post is still a work in progress)
WE NEED MORE TESTERS. Anybody with an A2017G and stock oreo(and the cam2 api patch below). Also more A2017U users on stock oreo need to help and test this.
Please report back if it works or not.
Requirements:
Selinux set to permissive (idk why but with enforced, ARcore doesn't work)
Camera 2 api is required. A2017G users need to flash this patch by @raystef66 https://androidfilehost.com/?fid=11410932744536993784
This won't be any simplified how to guide from me (more on that later).
Instead im gonna link 2 github issue posts which anyone with a little know-how about adb, sideloading/restore, root etc can follow to get ARcore working (reminder that it's also possible for non-rooted users).
First the main post
https://github.com/tomthecarrot/arcore-for-all/issues/139
IMPORTANT QUOTE and reason for not making a personal simple tutorial by myself (PAY ATTENTION TO THE LAST 2 SENTENCES PLEASE):
"Finally, we really only intended this mechanism for internal development use. We're mentioning it here because we see users super excited about running ARCore on additional devices, and agree that having to root your phone to do that is dumb. That said, we really only want to expose this to users already familiar with adb, side-loading, rooting, and the instability and wackyness that can arise from those things. Don't go out of your way to make it easy for novice users run ARCore on unsupported devices, and don't ask for support through official channels. If either of those start happening, we may have to cripple or remove this capability, and I think that's a loss for everyone involved."
What i think they are trying to prevent is "novice" users which don't know much about the matter in general, from flooding/spamming the official channels seeking for help. Also don't treat github as a forum. Don't ask the official devs for help. This is an UNSUPPORTED gift from the devs after all.
INSTEAD ask your questions here on this very xda thread and respect the official ARcore devs and the ARcore-for-all project. Thank you
I recommend reading through the whole github post as it's very informative on the matter and you might learn a thing or two.
Second post with instructions for rooted devices:
https://github.com/tomthecarrot/arcore-for-all/issues/139#issuecomment-466587565
For non-rooted users, please read through the github post. You need to know how to operate ADB restore properly.
Again, if you have any questions, ask here.
ARcore isn't working perfectly as of now since the calibration file we will be using isn't property tweaked yet (as the file itself was created for max compatibility for as many devices as possible). So let's work together, experiment with the values inside the calibration file (if you know how and what each value does, unlike me lol) and maybe, one day, we will have a proper, stable and smooth ARcore experience for our device.
Here is an example gif of me trying it out
https://thumbs.gfycat.com/GleefulShortBordercollie.webp (cant use IMG BB code to embed it into the post since its not in an actual gif format)
PS: i made this post on the phone and it's still a work in progress (especially now since xda labs messed up and only posted half of the OP for some reason). I plan to edit it later on pc for more clarity to make it visually easier and more appealing to read (currently sick, but i was so excited that i got ARcore working and really wanted to share it with you guys).
Since xda labs messed up with the post, some sentences are written differently than i originally intended. So i tried to fix it by re-writing the missing parts from memory and copy-pasting the whole text and posting it through the browser version of xda. So sorry if it is a little messy. All the more reason to edit it on pc later on xD.
Did everything the second post says to do for rooted users. Still a no go for me. When I load arcore measure it just flashes "acore keeps stopping"
Then it says ArCore is not able to run on this device.
What did you edit in your custom device profile?
Thanks bud
kountry83 said:
Did everything the second post says to do for rooted users. Still a no go for me. When I load arcore measure it just flashes "acore keeps stopping"
Then it says ArCore is not able to run on this device.
What did you edit in your custom device profile?
Thanks bud
Click to expand...
Click to collapse
I didn't edit anything yet since i have no idea what these values accomplish.
Do you have installed the camera2 api patch by @raystef66 ? Its needed, otherwise ARcore can't work. I edited OP and put the link to it at the top. (Totally forgot to add that this is the requirement)
Have you followed the steps exactly as they say? Quote: "Install the "arcore-modified-preview.apk" from*the "service-mod" branch*(it's linked in the README)"
See attached screenshot.
Download latest Arcore (from apmirror for example) and install that.
It doesn't have to be 1.7. You can just download the latest up to date version.
Follow the steps until he asks you to open the ARcore apk. What he now means by that is use any zip file viewer (i used rar for example) and with it open the official ARcore apk you downloaded (not the modified preview) and extract the textproto file from there.
Other than that i don't see any confusion coming from the rest of the instructions (renaming the file, putting it in the right folder etc)
GodOfPsychos said:
I didn't edit anything yet since i have no idea what these values accomplish.
Do you have the camera2 api patch installed by raystef66? This is necessary since it won't work without camera 2 api.
Have you followed the steps exactly as they say? Quote: "Install the "arcore-modified-preview.apk" from
Click to expand...
Click to collapse
I haven't installed raysteff66's camera2api patch but I have level_3 camera2 API and I went by the instructions you linked for rooted devices. I installed and modified everything it tells me to do.
P.s. I am using a ZTE Axon 7 A2017U on Oreo stock.
kountry83 said:
I haven't installed raysteff66's camera2api patch but I have level_3 camera2 API and I went by the instructions you linked for rooted devices. I installed and modified everything it tells me to do.
P.s. I am using a ZTE Axon 7 A2017U on Oreo stock.
Click to expand...
Click to collapse
Im sorry read my reply again, xda labs doesn't post my full replies for some odd reason so i used the browser version.
Also don't worry about the camera2 patch since you have an A2017U device. Its already camera2 api enabled
Added link of a demonstration gif to the OP
I'm running stock B20 Oreo and followed the instructions accurately. Do I need to clear the cache? I don't understand why it's crashing. I posted the screenshots of what I have.
kountry83 said:
I'm running stock B20 Oreo and followed the instructions accurately. Do I need to clear the cache? I don't understand why it's crashing. I posted the screenshots of what I have.
Click to expand...
Click to collapse
Hmm. Did you also set the permissions from the "files" folder as same as the others?
I didn't need to clear the cache and it worked for me.
@kountry83 if the "files" folder have the right permission and it still doesnt work. Could you maybe try a different camera ID?
Open the textproto file inside the files folder and edit the line camera_id: and change the 0 to 1.
Maybe this will do it.
See screenshot below
Maybe 0 is the front and 1 could be the back on the A2017U
GodOfPsychos said:
Hmm. Did you also set the permissions from the "files" folder as same as the others?
I didn't need to clear the cache and it worked for me.
Click to expand...
Click to collapse
/data/data/com.google.ar.core/files
My files folder is set to 2771 and the custom_device_profile.textproto file in the files folder is set to 644 permission.
kountry83 said:
/data/data/com.google.ar.core/files
My files folder is set to 2771 and the custom_device_profile.textproto file in the files folder is set to 644 permission.
Click to expand...
Click to collapse
My textproto file is set to 0666
We need more A2017G and U users with stock oreo to test ARcore. Please if any of you have already tested it and it works or not, please just say so in a reply and mention which device you used (G or U).
Edited OP as well to mention this
GodOfPsychos said:
We need more A2017G and U users with stock oreo to test this. Please if yoh have already tested it and it works or not, please just say so in a reply and mention which device you used (G or U)
Click to expand...
Click to collapse
Set the file to 0666. Still crashes with arcore measurement app. Even restarted and still crashes. What is your files folder permission?
Do you think you could make a flashible please with set permissions?
kountry83 said:
Set the file to 0666. Still crashes with arcore measurement app. Even restarted and still crashes. What is your files folder permission?
Do you think you could make a flashible please with set permissions?
Click to expand...
Click to collapse
My folder permission is the same as yours, 2771
Did you try changing camera ID as i mentioned in a previous post?
I tested the root method and it doesn't work as well. Probably need to tweak the custom_device_profile.textproto file
mickey36736 said:
I tested the root method and it doesn't work as well. Probably need to tweak the custom_device_profile.textproto file
Click to expand...
Click to collapse
Which device are you using? And which rom?
Also by "doesn't work as well" do you mean it doesn't work (crash) or its twitchy?
GodOfPsychos said:
Which device are you using? And which rom?
Also by "doesn't work as well" do you mean it doesn't work (crash) or its twitchy?
Click to expand...
Click to collapse
A2017G stock B01 with patch. I get with device not supportin mesure app.
Pokemon go also freeze the app when turn on ar+.
@GodOfPsychos changed camera ID to 1.
Same error, ArCore keeps stopping.
mickey36736 said:
A2017G stock B01 with patch. I get with device not supportin mesure app.
Pokemon go also freeze the app when turn on ar+.
Click to expand...
Click to collapse
Maybe its because you are still on the oreo beta. Im on b02
(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.
Hi all,
One of the things that was missing for me was the center clock.
The void in the middle needed to be filled so here you have a module to place the clock smack in the middle, it's not off center like previous mods, this one is as it should be.
Flashing always at your own risk, please read all instructions before flashing, module has been tested and is working on the latest android 11 BA running OOS, untested on non OOS ROM's
NOTES
-----------------
This will cause issues with android auto!
Does not work on Android 10
Confirmed working on Android 11 open beta 2
Confirmed working on Android 11 open beta 3
Confirmed working on OB4
Confirmed working on stable 11.0.2.2
Installation
-------------------
Pre-requisites
Rooted Oneplus 8 Pro
Android 11 Stable
Magisk Manager
Installation instructions
1. Download the module from here:
11.0.0 https://mega.nz/folder/OB8hXYqK#4hVILxDw-K7EKemL3FDNwQ
11.0.1.1
https://mega.nz/folder/SJ1G1RCD#izqB8T5SrK-uPiV4GVrTdQ
11.0.2.2
2.51 MB folder on MEGA
mega.nz
11.0.4.4
0 byte folder on MEGA
mega.nz
11.0.5.5
the module for 4.4 seems to be working fine for 5.5
If you have issues then disable it, reboot, re-enable then reboot and test.
11.0.6.6
2.51 MB folder on MEGA
mega.nz
11.0.7.7
Use the 0.6.6 version, it reloaded first time for me, i don't believe they changed OPSystemUI.apk so it's probably the exact same apk.
11.0.8.8
2.51 MB folder on MEGA
mega.nz
11.0.9.9
As this is only Octobers security update you can continue to use 11.0.8.8 thanks @mac796 for clarifying functionality.
11.0.10.10
Again no changes to OPSystemUI.apk so the previous release will continue to work on this version
2. Copy to your phones storage
3. Open Magisk and select the modules icon
4. Click "Install from storage"
5. Navigate to the downloaded folder and choose the zip inside.
6. Allow it to complete and then reboot.
Enjoy your center clock leave a thanks, let me know if it doesn't work and will do what we can to help.
Right side clock mod
---------------------------
Android 11.0.2.2
2.51 MB folder on MEGA
mega.nz
Thanks @Lycidias for testing
Troubleshooting
------------------------------
Magisk module failure.
This works for any magisk module failure.
1. Power off your phone by holding the power button, then turn it back on.
2. As your phone gets to the bootloader warning screen, press and hold volume up and down and continue to hold until the phone shows the boot animation.
3. You'll boot to safe mode, simply reboot once more.
4. On next boot all your magisk modules will be disabled, remove the problematic module and re-enable the functional ones.
Original mod made by
11-11.0.2.2
@Tulsadiver & @dianoandr tested by myself, absolutely massive thanks to them for this.
11.0.4.4 and onwards made by myself, original pixel version by Tulsadiver
REQUESTS
----------------
I can maybe do requests, but they won't be a priority and if i don't have the device, you will have to provide me the files required and give me the android version you're on, OS and you'll be testing too.
Oneplus 8T
------------
OOS 11.0.10.10 KB05BA
2.51 MB folder on MEGA
mega.nz
Thanks to @zarcom for testing
Enjoy
Did not work for A10
Works perfect on 11. Thank you.
[MOD EDIT: REMOVED OP QUOTE]
Any chance for porting to A10?
crazynapkinman said:
Any chance for porting to A10?
Click to expand...
Click to collapse
Can ask pal..will be tomorrow tho.
Why don't you just update to 11. It's way better than 10 anyway.
scott45333 said:
Works perfect on 11. Thank you.
Click to expand...
Click to collapse
Welcome.
crazynapkinman said:
Did not work for A10
Click to expand...
Click to collapse
Thanks for testing btw
dladz said:
Can ask pal..will be tomorrow tho.
Why don't you just update to 11. It's way better than 10 anyway.
Click to expand...
Click to collapse
I don't have an easy route to 11.
I'm on a Sprint\Tmo OP8.
I don't have Local Upgrade.
OTA disabled due to root and Tmo hasn't finished A11 anyway.
I'm hoping someone will make a A11 full rom to flash via TWRP to get me there
crazynapkinman said:
I don't have an easy route to 11.
I'm on a Sprint\Tmo OP8.
I don't have Local Upgrade.
OTA disabled due to root and Tmo hasn't finished A11 anyway.
I'm hoping someone will make a A11 full rom to flash via TWRP to get me there
Click to expand...
Click to collapse
Oh wow. What about converting to global?
dladz said:
Oh wow. What about converting to global?
Click to expand...
Click to collapse
I've been reading that thread for days and only get more confused the more I read...
I have to MSM back to stock? Then convert via fastboot? Idk... Very confusing reading it all.
Or I'm just too dense.
crazynapkinman said:
I've been reading that thread for days and only get more confused the more I read...
I have to MSM back to stock? Then convert via fastboot? Idk... Very confusing reading it all.
Or I'm just too dense.
Click to expand...
Click to collapse
Lol nah it's worrying doing these things but it's not usually as hard as you think.
Get it planned out before hand, I've rebranded before, on the p20 pro and I think a few HTC devices.
You'd be hard pushed to brick a OnePlus phone tbh.
But you're right to be careful. Just make a back up first.
dladz said:
Lol nah it's worrying doing these things but it's not usually as hard as you think.
Get it planned out before hand, I've rebranded before, on the p20 pro and I think a few HTC devices.
You'd be hard pushed to brick a OnePlus phone tbh.
But you're right to be careful. Just make a back up first.
Click to expand...
Click to collapse
Yeah. I got a backup of persist.img and boot partition.
I need to backup everything via TWRP?
Thanks much appreciated
Sent from my OnePlus IN2020 using XDA Labs
Thanks for this!! Really like centre clock One thing....now left side is disturbingly empty
hard case-never satisfied
But thank you!!
janitor9 said:
Thanks for this!! Really like centre clock One thing....now left side is disturbingly empty
hard case-never satisfied
But thank you!!
Click to expand...
Click to collapse
Haha it is check mine out though.
That's called energy ring.
crazynapkinman said:
Yeah. I got a backup of persist.img and boot partition.
I need to backup everything via TWRP?
Click to expand...
Click to collapse
So persist and boot is fine. But you probably won't be needing any of them.
As for the rest of it, backing up via twrp is one thing but at the point there ain't a functional copy of twrp for 11.
So backing up to twrp might not be the best idea.
I got out all my pics, vids, music, synced contacts with an account (Google) or sync everything to Google (I don't mean a back up as a single image, that's your choice)
Apps I would make a titanium back up of.
Then theres pretty much nothing left.
Copy all the titanium files out, that'll serve you well when you're ready to restore.
Then head down the rebranding route..
I'm not great with changing variant but I would back up also maybe your EFS partition if that's still a thing (IMEI's) just because of the networks hold on things, I can't think of anything else you could lose out on..
I'll check out the rebranding guides and see if I can make easier sense of it for you.
dladz said:
Haha it is check mine out though.
That's called energy ring.
Click to expand...
Click to collapse
Can you help me with a notchkiller mod that works on oxygenos 11 stable?
So far every mod i have used results in a bootloop
Blackdranzer said:
Can you help me with a notchkiller mod that works on oxygenos 11 stable?
So far every mod i have used results in a bootloop
Click to expand...
Click to collapse
We have no notch on the 8 pro?
dladz said:
We have no notch on the 8 pro?
Click to expand...
Click to collapse
Sadly some games and streaming apps like amazon prime display below the front canera....the result is a black bar just till the front camera
The notchkiller mods solved that issue but none of them working on android 11 so i was just asking if there any compatible version of the mod
Earlier netflix had this problem too but now they have solved it.
Blackdranzer said:
Sadly some games and streaming apps like amazon prime display below the front canera....the result is a black bar just till the front camera
The notchkiller mods solved that issue but none of them working on android 11 so i was just asking if there any compatible version of the mod
Earlier netflix had this problem too but now they have solved it.
Click to expand...
Click to collapse
There's a feature to change screen in android 11.
Plus you have the cut out option in display.