Related
I'm just wondering if anybody has managed to get the Sky Go app working with a rooted Nexus 7?
I've read somewhere that a rooted Android device can work with Sky Go if it is running a stock kernel and used in conjunction with Temp Root Remover.
If anybody has, please share your set up. :good:
Many Thanks,
Andy
I don't have an active Sky account anymore, but on Modaco JR13 with Stock kernel and unsecure boot.
I managed to load the app and sign into my old account without any problems.
Obviously I didn't get as far as watching TV as my account is closed.
Hope this helps.
+1 would like top know if it is possible
Sent from my Nexus 7 using XDA Premium HD app
This thread ( http://forum.xda-developers.com/showthread.php?t=2042095 ) describes a possible workaround (removal of supersu) but grants all subsequently installed apps root access after this, hence not ideal.
Fingers crossed a more secure method or patched apk arises in the future!
aaronje said:
This thread ( http://forum.xda-developers.com/showthread.php?t=2042095 ) describes a possible workaround (removal of supersu) but grants all subsequently installed apps root access after this, hence not ideal.
Fingers crossed a more secure method or patched apk arises in the future!
Click to expand...
Click to collapse
OK so I have a nexus 7 (2012) on standard Android 4.4.4.
Rooted with CWM and superSU 2.01
I just used the root hider app from the play store and selected ..
Hide Su binary and then
Uninstall super user (selected chain fire SuperSU option)
I then had to go into my root of my nexus 7 and remove the sky go files stored there.
After I deleted them I then restarted the tablet.
I can still reinstalled superSU as I'm still rooted but its a bit of a Hassel ATM as every time I want to watch SkyGO I have to follow the same routine, hideSu > uninstall superSU > delete SkyGO files from root dir > restart tablet.
I think there should be an Xposed module to hide root to certain apps, not 100% sure though..
A simple google search would answer your question: http://lmgtfy.com/?q=hide+root+access+android+xposed+module
But any ways here is the right module: http://repo.xposed.info/module/com.devadvance.rootcloak
It's called rootcloak. Remember: you need the Xposed Framework!
flopower1996 said:
A simple google search would answer your question: http://lmgtfy.com/?q=hide+root+access+android+xposed+module
But any ways here is the right module: http://repo.xposed.info/module/com.devadvance.rootcloak
It's called rootcloak. Remember: you need the Xposed Framework!
Click to expand...
Click to collapse
Still not working with the above, shame I just don't want to lose root.
jb.traveller said:
Still not working with the above, shame I just don't want to lose root.
Click to expand...
Click to collapse
hide su from google play works
1eyedmonster said:
hide su from google play works
Click to expand...
Click to collapse
Hi mate, could you give me a run down to what you did as I still can't get it to work.
Thanks.
1eyedmonster said:
hide su from google play works
Click to expand...
Click to collapse
I couldn't even find the app?
Hello. I currently have a OP2 (or is it OPT? ) with Official RR + Boeffla for CM (alpha 10). I know, I need to update my signature.
Today I decided to try Viper (making a nand backup first, of course) and it installed without problems, but it only works on Play Music. Same for AudioFX, the default EQ that came with the system that I have now disabled (to avoid Viper issues).
No effects on YouTube or BSPlayer for example (with eighter A-FX or Viper), in short, the EQs don't affect the system, but only some apps, or one in my case.
Is this normal behaviour? Back on KK 4.4.4 I could use Viper or whatever EQ app and it would apply to all the system and apps!
Thanks in advance.
Do you have force enable v4a on?
I tried but nothing. Do I have to reboot when I enable that?
Tried rebooting, nothing. It's just not applying to the whole system, only to the apps tha use equalizers.
Is this normal?
For me, it didn't even work on Spotify using the latest 2.4.0.1 of V4A in permissive mode and using the correct busybox. So I uninstalled it, maybe in a couple of months it will work again.
It's like not all system uses the default EQ. And I don't know if that's normal behaviour on MM or is it just me.
Fixed thanks to this post:
http://forum.xda-developers.com/showpost.php?p=66617379&postcount=22262
Hope it helps others.
eXtremeDevil said:
Fixed thanks to this post:
http://forum.xda-developers.com/showpost.php?p=66617379&postcount=22262
Hope it helps others.
Click to expand...
Click to collapse
Does the zip still work. Am on RR 5.7.1 and facing the same issue. Viper works for Music Player and Googel Music but nothing else. Need it for MX desperatley. Would really appreciate your help
Yes, actually, it was easier than flashing all those. Just install Viper the normal way, the apk and then the driver. You need to have Selinux set to permissive all the time, AFAIK. After the driver installation and reboot, follow these instructions:
http://forum.xda-developers.com/showpost.php?p=66717263&postcount=22331
For me, I had to set that file to read only because after reboots it would roll back to normal. But as long as those line are commented, Viper will work system-wide.
Hope that helps. Please tell me how it goes.
Cheers.
eXtremeDevil said:
Yes, actually, it was easier than flashing all those. Just install Viper the normal way, the apk and then the driver. You need to have Selinux set to permissive all the time, AFAIK. After the driver installation and reboot, follow these instructions:
http://forum.xda-developers.com/showpost.php?p=66717263&postcount=22331
For me, I had to set that file to read only because after reboots it would roll back to normal. But as long as those line are commented, Viper will work system-wide.
Hope that helps. Please tell me how it goes.
Cheers.
Click to expand...
Click to collapse
Yup that did it :victory::victory: thanks so much man.
Cheers!!
Glad I could help
eXtremeDevil said:
Yes, actually, it was easier than flashing all those. Just install Viper the normal way, the apk and then the driver. You need to have Selinux set to permissive all the time, AFAIK. After the driver installation and reboot, follow these instructions:
http://forum.xda-developers.com/showpost.php?p=66717263&postcount=22331
For me, I had to set that file to read only because after reboots it would roll back to normal. But as long as those line are commented, Viper will work system-wide.
Hope that helps. Please tell me how it goes.
Cheers.
Click to expand...
Click to collapse
What do you mean by commenting? Do I have to really delete those lines or just put quote marks before and after the lines?
And I'm on stock 3.02, rooted and xposed installed. Van this work form me?
If Viper is not working for you, you can try that solution. You can delete the lines or add "#" before them, eighter would work. I recommend commenting them because that way you can uncomment them anytime you want.
All credit goes to @brianelv and @FaserF
https://goo.gl/seMFLJ
I only used the manual edits to the build prop on my Nexus 9 16GB Wifi and I have not checked the flashable zips (try at your own risk)
Requirements:
-must be running 7.0+
-must be rooted
-Google app version should be at least 6.5.35.21 or newer
How-to:
-Back up your build.prop
-Add the following line to your build prop
Code:
ro.opa.eligible_device=true
Replace the following in your build.prop
Code:
ro.product.model=Nexus 9
by
Code:
ro.product.model=Pixel
-Save your edited build.prop
-Go to Settings>Apps>Google App>Storage click on "Manage Space", click on "Clear All Data"
Reboot in Recovery (TWRP) Choose Wipe>Advanced Wipe select Wipe "Cache" and "Dalvik/ART Cache"
Reboot System
Profit!
You should now have a fully working Google Assistant! Set it up by pressing and holding the "home" button
Thanks for the heads up that it works on the N9!
A word for anyone else trying it: after following the instructions, it seemed to not work. I waited 15 minutes or so, tried again, and it launched the Assistant.
borxnx said:
Thanks for the heads up that it works on the N9!
A word for anyone else trying it: after following the instructions, it seemed to not work. I waited 15 minutes or so, tried again, and it launched the Assistant.
Click to expand...
Click to collapse
What launcher are you using?
Google Now/Experience or whatever. Not Pixel
Sent from my XT1575 using Tapatalk
Got things working on Marshmallow PureNexus
How do you edit build.prop? I tried manually editing the text of the file within Amaze file manager, but it always reverts back to the original. I even tried saving an alternate and deleting the original and it won't work...
fredsbassett said:
How do you edit build.prop? I tried manually editing the text of the file within Amaze file manager, but it always reverts back to the original. I even tried saving an alternate and deleting the original and it won't work...
Click to expand...
Click to collapse
Be sure you are using a file manager that has root access enabled. It sounds like when you try to edit the file it's just not editing, which could be because it doesn't have root permission. Also be sure you click "Save". I used Solid Explorer and it worked no problem.
borxnx said:
Be sure you are using a file manager that has root access enabled. It sounds like when you try to edit the file it's just not editing, which could be because it doesn't have root permission. Also be sure you click "Save". I used Solid Explorer and it worked no problem.
Click to expand...
Click to collapse
I used two other file explorers (both with root access) and even tried pushing the file with adb and it didn't work, but Solid Explorer worked. Thanks!
Just got it working without changing the Model name. Stock 7.1.1
corkiejp said:
Just got it working without changing the Model name. Stock 7.1.1
Click to expand...
Click to collapse
Nice!
Did you know that the Google Assistant is now officially available on any Android device running Marshmallow and up, and it has been for like a week now?
I'm glad you got it working!
borxnx said:
Nice!
Did you know that the Google Assistant is now officially available on any Android device running Marshmallow and up, and it has been for like a week now?
I'm glad you got it working!
Click to expand...
Click to collapse
Yes I'm aware, but it is only been activated in limited countries. I'm in Ireland. I got it working on my Redmi Note 3 (Kenzo) by using a US VPN. The same trick didn't work for the Nexus 9, but using "ro.opa.eligible_device=true" activated it on that.
borxnx said:
Did you know that the Google Assistant is now officially available on any Android device running Marshmallow and up, and it has been for like a week now?
Click to expand...
Click to collapse
Phones only, not tablets.
Google confirms to us that the wider Assistant rollout will not reach tablets.
So the only way to activate it on the Nexus 9, is to use "ro.opa.eligible_device=true"!
I decided to start this thread for a couple of reasons 1 so I can remember what order I did things in to get back after a wipe and 2 so maybe it can help others to setup certain apps how they want and not have to spend the time I did searching and googling.
To start we are going to assume you already have an unlocked bootloader and TWRP installed.
After a fresh wipe I flashed OOS 4.0.2 Full from this thread in TWRP
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oos4-0-nougat-op3t-leaked-t3523482
I recommend a fresh wipe because every time I did a dirty flash or restored a backup my Android System started draining battery like crazy and phone would get warm while charging
Without rebooting I then flashed Magisk V10.2 in TWRP
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Still without rebooting I flashed Franco Kernel in TWRP
https://forum.xda-developers.com/on...ernel-franco-kernel-r1-28th-november-t3508904
I then wiped dalvik and cache and rebooted phone.
edit - THIS STEP WILL NOT WORK ON 4.0.3. It has been patched out.
Somewhere in the process my DM-Verity was tripped and although annoying it does not seem to matter and it can be fixed later by following this
https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339
After phone booted and I setup account and wifi and I go the play store and install PHH superuser
https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en
Once installed I open it and click the 3 dots and go to settings
Where it says Superuser access I toggle between Apps only and Apps and ADB till I get the message Superuser granted to Superuser
I then go back into play store and install Magisk manager
https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en
I go into Magisk Settings and click the checkbox to Enable Magisk Hide.
I then reboot phone
Once phone reboots I open Magisk manager again and check safetynet. It now passes.
I hate ads, I had been using Adaway from F-Droid with MM but I couldn't get it to work on N
I found this https://github.com/AdAway/AdAway/issues/770 after many searches. About halfway down a user named KreAch3R has comiled Sanjay900's changes into an apk so I figured I would give it a try.
At first I could not get it to activate and block ads
I installed this busybox and then it activates no problems and now most ads (not youtube) are blocked
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Now what I really wanted was Viper4arise. I tried flashing some in TWRP and I couldn't get them to work and this led to a couple more wipes. But I really wanted this so I kept searching.
I found this https://forum.xda-developers.com/apps/magisk/viperfx-mkm-magisk-t3535401
I downloaded it and enabled it in Magisk manager
Still no luck and I couldn't get it to work.
After more googling and reading through the other threads for viper I figured it was deep buffering
I used ES file explorer as I was not at home and went into system/etc and found audio_policy.conf
I commented out the first line I saw that said deep_buffer.
After saving I rebooted and now Viper-fx works
To get it to work with Poweramp I had to set FX compatibility mode in Viper to compatible and in Poweramp audio/advanced tweaks I had to disable Direct Volume Control and Enable MusicFX.
Thanks for sharing
Did you have any special trick to get viper to work ? Tried commenting out the line deep_buffer and still unable to get viper to work.
ghofer said:
Did you have any special trick to get viper to work ? Tried commenting out the line deep_buffer and still unable to get viper to work.
Click to expand...
Click to collapse
The only steps I did are what was listed.
I was able to replicate it twice after wipes with same steps.
This is the line I commented out in attached
Sykojoe said:
The only steps I did are what was listed.
I was able to replicate it twice after wipes with same steps.
This is the line I commented out in attached
Click to expand...
Click to collapse
Edited: Didn't see the attachment earlier. Answered my question. Thank you btw for sharing this the rest of the steps worked great for me. I am passing safety net.
Ya I realized a SS might help more so I edited it in.
Sykojoe said:
The only steps I did are what was listed.
I was able to replicate it twice after wipes with same steps.
This is the line I commented out in attached
Click to expand...
Click to collapse
Sykojoe said:
Ya I realized a SS might help more so I edited it in.
Click to expand...
Click to collapse
Would you be able to send me that file ? I am just curious what is wrong with my setup.
Just want to say thank you again. Didn't see the PM until now. I was able to use another guide on XDA to get Viper working.
Viper will not work on all apps at any time on OOS 4.0.2. Enable Compatibility mode in settings to get it to work. IMO this produces lower quality audio, but it works.
Still cant get viper working. Nothing of deep_buffer is commanded. Please can you share your audio_policy.conf?
NielsvdS said:
Still cant get viper working. Nothing of deep_buffer is commanded. Please can you share your audio_policy.conf?
Click to expand...
Click to collapse
You need to edit in a # on the deep_buffer line.
I sent you a pm with my file
NielsvdS said:
Still cant get viper working. Nothing of deep_buffer is commanded. Please can you share your audio_policy.conf?
Click to expand...
Click to collapse
1) With what app?
2) Did you enable Viper's Compatibility mode?
3) I've also modified audio_policy_configuration.xml to remove deep buffer. Messing with this file too much will break your audio though.
damiensturdy said:
1) With what app?
2) Did you enable Viper's Compatibility mode?
3) I've also modified audio_policy_configuration.xml to remove deep buffer. Messing with this file too much will break your audio though.
Click to expand...
Click to collapse
With what app?: I've editted with ES File Explorer.
Did you enable Viper's Compatibility mode? Not tried yet
I don't have changed anything inside audio_policy_configuration.xml
NielsvdS said:
With what app?: I've editted with ES File Explorer.
Did you enable Viper's Compatibility mode? Not tried yet
I don't have changed anything inside audio_policy_configuration.xml
Click to expand...
Click to collapse
WHat app isn't Viper working with? Viper processes audio on a per-app basis, based on the audio buffer the app uses. Google Play Music, on Nougat, does not pipe through Viper even with modifications to the audio config.
Enable compatibility mode. At the moment this is the only way to get the highest compatibility with apps- like Google Play Music.
damiensturdy said:
WHat app isn't Viper working with? Viper processes audio on a per-app basis, based on the audio buffer the app uses. Google Play Music, on Nougat, does not pipe through Viper even with modifications to the audio config.
Enable compatibility mode. At the moment this is the only way to get the highest compatibility with apps- like Google Play Music.
Click to expand...
Click to collapse
It's now working after disabling audio buffer. I use most of the times Spotify to listen to music
I followed same steps earlier. But my selinux is enforcing. I have to set it to permissive everytime on reboot. Permissive fix that comes with arise didnt work for me. Any idea..?
Do you think the Elemental X Kernel would be ok instead of franco kernel? Not sure if I'd get compatibility issues with any of this stuff. Btw not going to try to get adblock or viper fx. Also, do you wipe the system or just what TWRP has already checked?
x12prem said:
I followed same steps earlier. But my selinux is enforcing. I have to set it to permissive everytime on reboot. Permissive fix that comes with arise didnt work for me. Any idea..?
Click to expand...
Click to collapse
Mine is set to enforcing with all this working fine
Ra3zor0 said:
Do you think the Elemental X Kernel would be ok instead of franco kernel? Not sure if I'd get compatibility issues with any of this stuff. Btw not going to try to get adblock or viper fx. Also, do you wipe the system or just what TWRP has already checked?
Click to expand...
Click to collapse
Not sure. I know it all worked the same with stock kernel.
Normally when I need to wipe my phone it is because I have really messed it up so I wipe system and data.
Sykojoe said:
Mine is set to enforcing with all this working fine
Click to expand...
Click to collapse
But viper4rarise needs selinux as permissive. Isnt it....?
Hey,
did somebody try to install Xposed Framework on the book?
Its normal Android 6.0.1, so it should be work. It must be the x86 version right?
I personally have not tried doing this, but I've had a quick look around, and it seems entirely possible. It doesn't seem like Xposed depends on the actual hardware, but more on the software side - and since Lenovo's ROM is fairly close to stock Android M, I don't see any reason why it wouldn't work.
I don't have the Android version of the Yoga Book, so I can't test this for you, but so long as you make a backup, all the hard work has already been done for you if this is something you want.
nan0s7 said:
I personally have not tried doing this, but I've had a quick look around, and it seems entirely possible. It doesn't seem like Xposed depends on the actual hardware, but more on the software side - and since Lenovo's ROM is fairly close to stock Android M, I don't see any reason why it wouldn't work.
I don't have the Android version of the Yoga Book, so I can't test this for you, but so long as you make a backup, all the hard work has already been done for you if this is something you want.
Click to expand...
Click to collapse
I tried it today but its not working. With the x86 file I got the message, that I need a correct x64 file. And with the arm64 file I got the error 255.
Any idea?
ox_eye said:
I tried it today but its not working. With the x86 file I got the message, that I need a correct x64 file. And with the arm64 file I got the error 255.
Any idea?
Click to expand...
Click to collapse
Hmm... Technically the Yoga Book is using the x86_64. However, the error your getting refers to something missing. So perhaps it's as simple as when you downloaded the file, something got left behind. Double check the checksum, or if you don't know how just re-download the file (the arm64 one)... If that doesn't work then maybe it does in fact need its own x86_64 build.
I'll have a look, but try once more.
nan0s7 said:
Hmm... Technically the Yoga Book is using the x86_64. However, the error your getting refers to something missing. So perhaps it's as simple as when you downloaded the file, something got left behind. Double check the checksum, or if you don't know how just re-download the file (the arm64 one)... If that doesn't work then maybe it does in fact need its own x86_64 build.
I'll have a look, but try once more.
Click to expand...
Click to collapse
I downloaded the arm64 file again, but got the same error "error: 255".
ox_eye said:
I downloaded the arm64 file again, but got the same error "error: 255".
Click to expand...
Click to collapse
I've had a quick look around and I've found that you do need to have a specially built version for x86_64, so you're not doing anything wrong. It doesn't look like many people have done it, but it has been achieved before. So if you have the time it may be something to do (or look further into the forums for a version of Xposed).
Hope I've helped at all, I'll try dig a little deeper later on.
nan0s7 said:
I've had a quick look around and I've found that you do need to have a specially built version for x86_64, so you're not doing anything wrong. It doesn't look like many people have done it, but it has been achieved before. So if you have the time it may be something to do (or look further into the forums for a version of Xposed).
Hope I've helped at all, I'll try dig a little deeper later on.
Click to expand...
Click to collapse
Okay, I have the time. But I dont know what I have to do.
ox_eye said:
Okay, I have the time. But I dont know what I have to do.
Click to expand...
Click to collapse
I'm still having a look around, but before I shove more test builds down your throat for you to see if they work I need to ask; do you know how to fix a boot-loop? Because that may happen and I can't be liable for your device.
But if you're cool with that, I'll give you more things to test out ;D
On my Note 10.1 and Oneplus 3 I had some Bootloops during installing ROMs. The different was that TWRP was installed directly on the device. So I did a full wipe with it and bootloop are gone.
Is it the same here? Only that I habe to load TWRP manually with ADB? If so, then we can try.
ox_eye said:
On my Note 10.1 and Oneplus 3 I had some Bootloops during installing ROMs. The different was that TWRP was installed directly on the device. So I did a full wipe with it and bootloop are gone.
Is it the same here? Only that I habe to load TWRP manually with ADB? If so, then we can try.
Click to expand...
Click to collapse
Yeah, I mean you can install TWRP on your device, it's just not recommended at the moment as it can be unstable. But yeah, it's basically the same here.
Have you got your device Rooted? Because I'd like to test out Magisk's Xposed version on x86_64. It doesn't say that it supports it or not... and I'm not sure if it's just implied from the original compatibility. But I guess now is a good time to find out, and I'll be able to update my Megathread with the information.
To install it (assuming you're Rooted via Magisk - if not, my Megathread has the information) just download the Magisk Manager app from the Play Store, go to the "Downloads" section, and download the latest SDK version (I think it's 24 or 23...) and install that (if the option is there). Once that's done downloading, just go to this page and download the Material Design Xposed Installer, and follow the instructions there.
Hopefully that should work... but if not, that just means we're going to have to do more experimenting!
Installer link: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
No success. If I try to install the Framework with Material Design Xposed I get the error message "Error 1 occured" either with x86 and arm64 file.
ox_eye said:
No success. If I try to install the Framework with Material Design Xposed I get the error message "Error 1 occured" either with x86 and arm64 file.
Click to expand...
Click to collapse
You need to download the Xposed SDK via the Magisk Manager with Magisk installed. There is no x86 or arm64 version of either. Also make sure you don't have the original Xposed Installer on your device, these two installers are incompatible.
Follow these steps:
1. Uninstall any version of Xposed you have of the original/official version
2. Install Magisk (check my Megathread for more information on that)
3. Download and install the Magisk Manager from the Play Store
4. Download the Xposed SDK (latest version) from inside the Magisk Manager
5. Download and install the unofficial Material Design Xposed Installer from the link before
6. Install Xposed from the Magisk Manager
nan0s7 said:
You need to download the Xposed SDK via the Magisk Manager with Magisk installed. There is no x86 or arm64 version of either. Also make sure you don't have the original Xposed Installer on your device, these two installers are incompatible.
Follow these steps:
1. Uninstall any version of Xposed you have of the original/official version
2. Install Magisk (check my Megathread for more information on that)
3. Download and install the Magisk Manager from the Play Store
4. Download the Xposed SDK (latest version) from inside the Magisk Manager
5. Download and install the unofficial Material Design Xposed Installer from the link before
6. Install Xposed from the Magisk Manager
Click to expand...
Click to collapse
Now, I get the error "error during Installation". Magisk is up to date with version 14.2 There is no log file to check.
ox_eye said:
Now, I get the error "error during Installation". Magisk is up to date with version 14.2 There is no log file to check.
Click to expand...
Click to collapse
Hmph. Well that is disappointing. I'm not sure if you've looked into the actual files of Xposed, but the other day I found that someone made a "patch" for one of the files. If you want to have a look inside the files you download and see if you can find this one, then that may be another experiment we could try.
The file is gistfile1.txt, there's also this extra information "gist:86ac06a6be14a6d9331b" - I don't know if that's anything useful.
My bad, gist is something to do with GitHub. But the contents of the file is still useful, but I don't know which file would need the patching.
The patched file is here, so I'd assume all you have to do is locate that file and replace the contents of it with this patched version, and then try to install Xposed (either via the Magisk method or the official method, up to you).
Hopefully I can either find more information about this patch or find something else you can try. Good luck!
Patched file: https://gist.github.com/shakalaca/86ac06a6be14a6d9331b
nan0s7 said:
Hmph. Well that is disappointing. I'm not sure if you've looked into the actual files of Xposed, but the other day I found that someone made a "patch" for one of the files. If you want to have a look inside the files you download and see if you can find this one, then that may be another experiment we could try.
The file is gistfile1.txt, there's also this extra information "gist:86ac06a6be14a6d9331b" - I don't know if that's anything useful.
My bad, gist is something to do with GitHub. But the contents of the file is still useful, but I don't know which file would need the patching.
The patched file is here, so I'd assume all you have to do is locate that file and replace the contents of it with this patched version, and then try to install Xposed (either via the Magisk method or the official method, up to you).
Hopefully I can either find more information about this patch or find something else you can try. Good luck!
Patched file: https://gist.github.com/shakalaca/86ac06a6be14a6d9331b
Click to expand...
Click to collapse
I am having the same problems getting Xposed on this tablet. I tried the methods in this post but still can not get it. I cant find the file the you are referring to change. Anything else to try or maybe there is another way to accomplish what I am trying to do. I am trying to use "Hide Mock Location" to use "Fake GPS" so I can watch baseball on the "MLB at Bat" app. The app blacks out the game if you are in the viewing area. Last year I just used Private Internet VPN and Fake GPS and it worked this year that doesn't. I found this post https://www.comparitech.com/blog/vpn-privacy/mlb-tv-workaround-with-dns-vpn/ when searching that is what I am trying to get Xposed installed. Any ideas would be welcome
frankjerkyass said:
I am having the same problems getting Xposed on this tablet. I tried the methods in this post but still can not get it. I cant find the file the you are referring to change. Anything else to try or maybe there is another way to accomplish what I am trying to do. I am trying to use "Hide Mock Location" to use "Fake GPS" so I can watch baseball on the "MLB at Bat" app. The app blacks out the game if you are in the viewing area. Last year I just used Private Internet VPN and Fake GPS and it worked this year that doesn't. I found this post https://www.comparitech.com/blog/vpn-privacy/mlb-tv-workaround-with-dns-vpn/ when searching that is what I am trying to get Xposed installed. Any ideas would be welcome
Click to expand...
Click to collapse
Hmm well to my knowledge no one got Xposed to work on the Yoga... but if you managed to follow my tutorial to install Magisk (I don't think SuperSU works) there are a few apps in the Play Store that allow you to set up a "mock location", but they require Root access.
nan0s7 said:
Hmm well to my knowledge no one got Xposed to work on the Yoga... but if you managed to follow my tutorial to install Magisk (I don't think SuperSU works) there are a few apps in the Play Store that allow you to set up a "mock location", but they require Root access.
Click to expand...
Click to collapse
Thanks I do have Magisk installed and have working root.
There is still no way to install xposed?
matata86 said:
There is still no way to install xposed?
Click to expand...
Click to collapse
In the moment not
Hi, friends! Did anyone try to install xposed*.zip via TWRP ?