Database Develop

Viper4android

I tried lolipop version, Im on 5.0.1
Is there any way to make it working?
I only use it on spotify.
Or is there any other good app/equalizer?
Thks

Fustigador said:
I tried lolipop version, Im on 5.0.1
Is there any way to make it working?
I only use it on spotify.
Or is there any other good app/equalizer?
Thks
Click to expand...
Click to collapse
I think this belongs in here: http://forum.xda-developers.com/shield-tablet/help
Well, is there a problem with flashing the .zip or does the app dont work properly?
I used this (first two .zips) and this.
If that is still not working you should try that too.

The app works ok, but the sound is the same, its like doesn't have any effect.
I'll try lá ter.
Its not only Q&A but a thread with the app funcional to ower device.

Fustigador said:
The app works ok, but the sound is the same, its like doesn't have any effect.
I'll try lá ter.
Its not only Q&A but a thread with the app functional to our device.
Click to expand...
Click to collapse
I got V4A working by using the zip/apk standard download, then installing the apk as usual (making it a User app).
Install the V4A driver.
Make sure your Compatibility Mode is set to Normal.
Reboot.
Install SE Linux Mode Changer app from the Play Store (or edit your build.prop) to switch your SE mode to Permissive. (L's default is Enforcing.)
Open V4A up and tick the Enable box to use V4A on the ”phone speaker” tab.
Play some music! Check to see if it is working by unticking the phone speaker Enable box.
*If* it still doesn't work... Try the following one at a time:
Set Compatibility Mode to Compatible.
Tick the Force Enforce V4A under the phone speaker tab.
Install as a System app instead of a User app.
Try a different music player app. I'm using Shuttle+ and it works perfectly. I've heard some player apps don't work as well as others though.
Hoping this helps you a bit. It seems to be one of those trial & error things to get Viper set up on Lollipop. I even have to do things a tad differently to get it working on my Nexus 4 & 5.
?

Ty worked Great. I didn't Changed to permissive.
Maybe some moderator could move this thread to Q&A?
?

MiePx3 said:
I think this belongs in here: http://forum.xda-developers.com/shield-tablet/help
Well, is there a problem with flashing the .zip or does the app dont work properly?
I used this (first two .zips) and this.
If that is still not working you should try that too.
Click to expand...
Click to collapse
Hello, I flashed all three zip files from the first link but upon rebooting, v4a continually force closes. Don't have any other sound mods.
I'm on 5.0.1. Any help would be greatly appreciated.
Thanks.
Sent from my 1+1

Mojar7070 said:
Hello, I flashed all three zip files from the first link but upon rebooting, v4a continually force closes. Don't have any other sound mods.
I'm on 5.0.1. Any help would be greatly appreciated.
Thanks.
Sent from my 1+1
Click to expand...
Click to collapse
The last .zip from the first link is outdated. Try to delete it and use this one.
Make sure you use the right .apk for 5.0 (should be A4.x).

MiePx3 said:
The last .zip from the first link is outdated. Try to delete it and use this one.
Make sure you use the right .apk for 5.0 (should be A4.x).
Click to expand...
Click to collapse
Hello, thanks for the response. However, v4a kept force closing constantly and continually so I'm not able to navigate within the device. My biggest idiotic move was I didn't make a nandroid....assuming all will be good.
Anyways, I'm now on a hunt to flash stock rooted rom. If you have any info on that would greatly appreciate it.
Thanks.
Sent from my 1+1

OK all the file flashing is not useful at all if ur running stock. The only reason they exist is for DIFFERENT DEVICES, meaning ur flashing crap that is meant for something else and can have bad consequences. The flushable zips all have scripts that add lib files or script to build.prop. The flushable zips also seem to mess with any app that handles kernel configuration. ie if u like to change clock speeds, nothing would stick on this tablet after I flashed those v4a zips. Would always revert to stock.
For v4a to work. FIRSTLY run selinux mode changer. The person that said they got this to work without it is wrong. Dead wrong. The driver will NOT I STILL OR INITIALIZE UNLESS SELINUX IS PERMISSIVE. This must be done to allow android to install the driver to the kernel. Period. Run selinux mode changer, set to permissive, reboot. Check selinux, sometimes u will have to do it 3-4 times for it to stick. Then install the newest v4a from their site I think it's @ 2.3.4.0 the older versions needed the flashable zips for some files the Nexus lollipop update didn't have. They fixed this. Now just install the app normally, then open it and install the driver. Reboot. If u r on cyanogen unlock the developer options and turn off or unchecked "use nuplayer" finally, if u use gone mad music player go to options, audio, tell it to use external dsp.
Profit!
I've never needed to use compatibility mode or anything else. Works like a champ.

[IMG][XT1096] TotalX | root-tether-busybox-sqlite-xposed-hosts-bootanimation-dialer

***** TotalX *****​
I've built a mofo-flashable system image for the Verizon Moto X 2014 containing root, WiFi tethering, Busybox, SQLite3, Xposed, a symlinked hosts file for adblocking, a custom bootanimation, and the stock Google Dialer that has caller ID and allows you to search for business phone numbers. I also added the stock Google Messenger app. I'm currently working on getting CF.lumen to work, and AirAudio is fully functional with this image. I really didn't do much, most of the hard work was thanks to @JulesJam, @Slack3r, @slogar25, @btdownloads7, and @mikeoswego. Shout out to all of them for their hard work.
Download here:
TotalX-1.3.rar
TotalX-1.2.rar
TotalX-1.1.rar (do not recommend flashing, very buggy and drains battery)
TotalX.rar
Instructions:
Download the Xposed installer if you don't already have it, and install it to your phone but don't do anything with it. Also install AdAway 3.0.
If this is your first time flashing an image with Xposed, go into your file manager and delete /data/dalvik-cache/arm and /data/dalvik-cache/profiles. If you don't already have root, just do this step after flashing and reboot.
Wipe cache prior to flashing:
Code:
adb reboot bootloader
fastboot erase cache
Next, extract TotalX.rar to your mofo directory, flash the image with mofo, and wipe cache when its done:
Code:
mofo flash TotalX-1.1.img
fastboot erase cache
It might take a while to boot up, but at least you can enjoy the crazy new bootanimation. When it finally boots, open up AdAway and go to preferences, scroll down to "Target hosts file" and select /data/data/hosts. This sets it so that AdAway modifies the hosts file in /data/data, which is where the /system/etc/hosts file is pointing to.
If you'd like extra heavy-hitting adblocking, add XXXXXXXXXX to your hosts sources (EDIT: Don't do this, it screws up MMS). Then hit download and apply on the main screen and reboot once its done.
Install any Xposed modules you want and reboot. And here's a great module you can't get through the Xposed app: Pandora Patcher
That's it! You should be all set after that with no ads and the power of Xposed. If you have any trouble flashing, don't be afraid to post here and I'll try to help out. And if you'd like to buy me a beer, feel free to shoot [email protected] some cash on Google Wallet
Changelog:
Version 1.3:
- AirAudio is now fully functional!
Version 1.2:
- Removed build.prop edits due to HDR bug and battery drain
Version 1.1:
- Switched to @mikeoswego's base to fix busybox due to Xposed installation removing busybox for some reason
- Google Messenger app added
- build.prop edits by @trimax84
- New bootanimation taken from @motomotomotoG's collection (Geometry Dark), if you'd like any of the others from that page let me know and I'll make you an image!
- Fixed bootanimation memory leak using fix by @arter97
Version 1.0:
- Original, based on @btdownloads7's image, added Xposed, hosts symlink, 5.1 bootanimation, and Google Dialer.
Click to expand...
Click to collapse
Known Bugs:
- Upon flashing, you may experience Google Play Services constantly crashing. Still not sure what causes this. To fix it, uninstall updates for the Google Play Store and Google Play Services, reboot, and then reinstall the update. No more crashing after that.
- If you followed my instructions earlier to add http://adblock.mahakala.is/ to your hosts sources in AdAway, you will most likely be unable to send MMS. To fix this, revert your hosts file and remove this source, then reboot, reapply, and reboot again.
- Version 1.1 was very buggy due to the build.prop edits. The edits create a bug where the camera app crashes when taking pictures in HDR mode. It also seemed to drain battery at a ridiculous pace and created huge slowdowns. I fixed this in later versions and will not be editing the build.prop in future versions.
Click to expand...
Click to collapse

You are the man. I'm downloading now and will flash as soon as I can. [emoji106]

Install went as expected. I was coming from another version of this img with adaway and xposed and bb, sqlite. I cleared cache before and after install, on boot everything went good, not too long. At first everything was smooth, I was letting it settle before playing with the new dialer, then I started getting mass unresponsive apps, mostly google. I did a reboot and haven't had a repeat of the issue yet. Adaway updates fine, xposed modules load fine, and busybox is good. Google dialer is operational if a little slow feeling to me, oh and the boot animation is gorgeous as well. Great work putting this one together, to all who input.

contesauce said:
Install went as expected. I was coming from another version of this img with adaway and xposed and bb, sqlite. I cleared cache before and after install, on boot everything went good, not too long. At first everything was smooth, I was letting it settle before playing with the new dialer, then I started getting mass unresponsive apps, mostly google. I did a reboot and haven't had a repeat of the issue yet. Adaway updates fine, xposed modules load fine, and busybox is good. Google dialer is operational if a little slow feeling to me, oh and the boot animation is gorgeous as well. Great work putting this one together, to all who input.
Click to expand...
Click to collapse
hmmm.. that sound a little scary might hold off until its confirmed that this was a one off issue. But thanks for the upload!

To be fair it happened to someone else on one of the other threads with a dif image. Seems to be a one off after a reboot. Understand your trepidation though.

It actually just happened to me too. Rebooted and hasn't happened again. But yeah, it also happened to me with one of the previous builds as well, so I think it might just be a one-off problem. Will report if it happens again.

It does that with every new flash. Not sure why, but a reboot fixes that sucker.

Thanks for this! Any chance of getting this image without Xposed?

TokedUp said:
Thanks for this! Any chance of getting this image without Xposed?
Click to expand...
Click to collapse
I can do that, do you want everything except Xposed?

ClydeDroid said:
I can do that, do you want everything except Xposed?
Click to expand...
Click to collapse
YES! I had a very bad experience with Xposed once and i'll never use it again. Thanks. There's no rush though. Im on vacation so I wont be able to flash anything or donate to you until I get back home. I really appreciate it man and I promise I'll buy u some beer as soon as i get back.

Is this based off the image that has the HDR fix?

TokedUp said:
YES! I had a very bad experience with Xposed once and i'll never use it again. Thanks. There's no rush though. Im on vacation so I wont be able to flash anything or donate to you until I get back home. I really appreciate it man and I promise I'll buy u some beer as soon as i get back.
Click to expand...
Click to collapse
Alternatively you could flash this image and not use Xposed i.e. don't install the APK. Libs are't doing anything important.

Mayze23 said:
Is this based off the image that has the HDR fix?
Click to expand...
Click to collapse
Yep!

ClydeDroid said:
Yep!
Click to expand...
Click to collapse
Installed! Thanks for the Birthday Present -
As a suggestion you could modify the Build.prop to add a custom Rom Name under settings and custom details etc. That way you can really feel ownership of your changes.
Also if you really wanted you could delete Verizon Apps under the /system/app partition to remove bloatware but I understand that may be a bit tedious and undesirable. Otherwise really good build, worked well - no issues.

Haxxa said:
Also if you really wanted you could delete Verizon Apps under the /system/app partition
Click to expand...
Click to collapse
Or you could just freeze them with TiBU. If you are not going to be able to use the space for anything else, no sense in deleting them. Also some Verizon customers actually use NFL Mobile, Verizon Navigator, MyVerizon, etc.

I've had the gapps issue as well, basically neutered the phone until I forced a restart. A reboot had fixed it temporarily but it came back again a couple of times. I eventually uninstalled updates for both Play Store (gapps) and Google Play Services and re-downloaded the updates. Have been fine for a while now.
My bluetooth has also been wonky. Used to connect to my car without issue but now I seemingly have to manually connect, or even reboot the phone to get it to connect. Wasn't having these issues on previous images...
Now that I've bltched, I really appreciate the work...and the changes are worth the few headaches! Thanks!

ClydeDroid said:
Yep!
Click to expand...
Click to collapse
Do you have any interest in adding CF Lumen to your image? When I download it, it has to install a driver and that must be something that is installed on /system b/c it never gets installed. However, I don't know if drivers are something that is too complicated to bake into an image.
http://forum.xda-developers.com/showthread.php?t=2711912
There is an unrooted mode but it doesn't work near as well as the rooted mode. With the rooted mode you can get the whites to be a very nice cool-toned white w/o any yellow/pink tinge.

JulesJam said:
Do you have any interest in adding CF Lumen to your image? When I download it, it has to install a driver and that must be something that is installed on /system b/c it never gets installed. However, I don't know if drivers are something that is too complicated to bake into an image.
http://forum.xda-developers.com/showthread.php?t=2711912
There is an unrooted mode but it doesn't work near as well as the rooted mode. With the rooted mode you can get the whites to be a very nice cool-toned white w/o any yellow/pink tinge.
Click to expand...
Click to collapse
Sure, I'll give it a shot!

tjohnstone3 said:
I've had the gapps issue as well, basically neutered the phone until I forced a restart. A reboot had fixed it temporarily but it came back again a couple of times. I eventually uninstalled updates for both Play Store (gapps) and Google Play Services and re-downloaded the updates. Have been fine for a while now.
My bluetooth has also been wonky. Used to connect to my car without issue but now I seemingly have to manually connect, or even reboot the phone to get it to connect. Wasn't having these issues on previous images...
Now that I've bltched, I really appreciate the work...and the changes are worth the few headaches! Thanks!
Click to expand...
Click to collapse
That's really strange. I've only experience the gapps freaking out once, but this is worrying. I might do some research to try to figure out what the problem could be.

ClydeDroid said:
That's really strange. I've only experience the gapps freaking out once, but this is worrying. I might do some research to try to figure out what the problem could be.
Click to expand...
Click to collapse
It's been 5 hours since I did the uninstall updates and reinstall them and I haven't had any issues since. So hopefully it's a thing of the past.
Though I haven't retested the bluetooth since this morning.

[Discussion] Fate Go Magisk Discussion Thread

Just wanted to create a thread similar to the Pokémon Go one because i've seen the only one having problems with this app and magisk despite the John announncement made in September...
Anyway, back to the main topic, in this thread i would like to gather all users with some requirements:
- Fate GO istantly closes, opens the default mail app and prompts the "Error 61" in the mail, other errors have nothing to do with magisk.
- Latest version of Magisk Dev
- Magisk Hide enabled and Fate GO ticked in the list
- Magisk Manager hidden
- Check if other apps (Like GPay for example) find Magisk/Root or not
- Safetynet "full" passes
- No Xposed
- Running the uninstaller of magisk makes Fate GO working normally
- Always write: ROM, Kernel, Magisk Version, Fate GO version and region (NA, CN, JP ecc...)
Thanks in advance to everyone that will help with this problem or share their experiences or thoughts, and if someone else would like to test itself you can find the apk on APKPure if it's no present on play store.

Make sure USB debugging is disabled, then if that doesn't work, clear the data for the app
Sent from my Pixel using Tapatalk

Hello, I'm sorry for you, but I'm the same, and the worst is that I recently installed magisk, just yesterday, because I thought it would work with Fate G / O but apparently I happen the same as you, it was supposed to be fixed, right?
By the way, just to complete other apps I can't find magisk.
-StockRom Android 6.
-Kernel 3.18.19+
-Last Magisk Dev
-Last ver JP and NA

Chocobubba said:
Make sure USB debugging is disabled, then if that doesn't work, clear the data for the app
Click to expand...
Click to collapse
Debug usb has nothing to do with error 61, which is magisk, that's why I specified it in the list xD
Niiya said:
Hello, I'm sorry for you, but I'm the same, and the worst is that I recently installed magisk, just yesterday, because I thought it would work with Fate G / O but apparently I happen the same as you, it was supposed to be fixed, right?
By the way, just to complete other apps I can't find magisk.
-StockRom Android 6.
-Kernel 3.18.19+
-Last Magisk Dev
-Last ver JP and NA
Click to expand...
Click to collapse
Yep, it was supposed to bi fixed since September, but the majority of the players here and on reddit reported the opposite, I've tried anything suggested and to ask it many times in many threads and for now I'm stuck with a not-rooted OP6...
Btw I got it "barely working" with the app "Island" but I say "barely" because sometimes it didn't work.

Killua96 said:
Debug usb has nothing to do with error 61, which is magisk, that's why I specified it in the list xD
Yep, it was supposed to bi fixed since September, but the majority of the players here and on reddit reported the opposite, I've tried anything suggested and to ask it many times in many threads and for now I'm stuck with a not-rooted OP6...
Btw I got it "barely working" with the app "Island" but I say "barely" because sometimes it didn't work.
Click to expand...
Click to collapse
I tried flashing the reddit hide zip and several more until I surrendered, after all I gave him delete without remembering to save the save code.
It's weird, because I installed magisk believing that go would work, if a bank app works because it wouldn't work fate GO?
It seems that I was wrong.

Niiya said:
I tried flashing the reddit hide zip and several more until I surrendered, after all I gave him delete without remembering to save the save code.
It's weird, because I installed magisk believing that go would work, if a bank app works because it wouldn't work fate GO?
It seems that I was wrong.
Click to expand...
Click to collapse
Btw my bank app doesn't work with and without magisk, anyway the problem is that FGO was advised as playable since September and it's not...

Hello, i get some problems like this. My device - Asus me302kl with Nitrogen os 8. I install magisk (canary), hide fate app, and rebuilt magisk with new package name. After killing process in app settings i can play, but after some time (i think when magisk has autolaunch) fate found magisk and i recieve error 61. After this I need restore and rebuild package again, for normal fgo launch.
Now i try something for stable result.

This could be interesting: https://twitter.com/topjohnwu/status/1064941972375392257?s=19
Let's see if he can do something about it...

Killua96 said:
This could be interesting: https://twitter.com/topjohnwu/status/1064941972375392257?s=19
Let's see if he can do something about it...
Click to expand...
Click to collapse
And in fact now magisk is not detected at all by FGO, finally...!

For a moment I got error 43 so I deactivated the USB debug, but then I went back to error 61, is it still possible that it is an error of my device?
The developer options are activated permanently because oem unlock is activated.

Niiya said:
For a moment I got error 43 so I deactivated the USB debug, but then I went back to error 61, is it still possible that it is an error of my device?
The developer options are activated permanently because oem unlock is activated.
Click to expand...
Click to collapse
If you have added fgo to the magisk hidelist, and have hidden MagiskManager trough the option in the settings then you could try to use the ProcGate apk and see if the proc bug is the issue.

FGO works well now, no errors or anything. This is great because I use root regularly, but wasn't willing to let go of it.
:victory:

I have android 6, well I can always use an emulator.

Just tried this game and can't open just white screen and there some gmail option
-AEX N 7.1
-latest mgisk cannary
-3.10.108
-latest NA
I can play dragalia lost just fine with magisk hide,this game sure annoyingxD
Edit: Oookay its weird,I just reboot my device and it work like a charmxD

Niiya said:
I have android 6, well I can always use an emulator.
Click to expand...
Click to collapse
Check with procgate app if you have leaks, if there are unfortunately there aren't solutions atm on Android versions bellow nougat...

Well looks like this topic is a bit dead. Is Fate GO still working with Magisk?

I can't seem to get it working. Keep getting error 61 & 60
Running on 7.1 LineageOS with latest canary build
Both Fate GO & MM are hidden
All safetynet checks passed
Freshly flashed ROM, no Xposed or anything
No leaks detected in Procgate
Running magisk uninstaller makes Fate GO working normally

AsakuraVN said:
I can't seem to get it working. Keep getting error 61 & 60
Running on 7.1 LineageOS with latest canary build
Both Fate GO & MM are hidden
All safetynet checks passed
Freshly flashed ROM, no Xposed or anything
No leaks detected in Procgate
Running magisk uninstaller makes Fate GO working normally
Click to expand...
Click to collapse
What error code you have last? 61?
Try hide MM from framework+google apps

Lordische said:
What error code you have last? 61?
Try hide MM from framework+google apps
Click to expand...
Click to collapse
Already tried. Right now it's 60.

Guilhermex12 said:
Well looks like this topic is a bit dead. Is Fate GO still working with Magisk?
Click to expand...
Click to collapse
Yes. Poke GO and FGO work with Magisk - at least with 17.4 and 18.1. i played Fate a few days ago, no problem on Pie.

Magisk Modules not working

Hi everyone,
I am pretty new to rooting, flashing, modding etc.
My problem is as follows:
I am on Pie 10.0.1.0PDIMIFJ, upgraded to it thanks to a guide in this forum.
After upgrading (bootloader has been unlocked beforehand of course) I got root through patched boot.img and Magisk Manager.
I did this in order to be able to gain some everyday treats such as Youtube background playing and especially V4A.
I could install these modules via Magisk, but they do not seem to work.
V4A is asking for driver installation everytime I reboot my phone, and I have to reboot after every driver installation.
This happens independently from the version of Viper I am trying to install.
After installing Youtube Vanced nothing changes. Playing stops when closing the app while a video is turned on.
I also tried a couple of other modules but none seems to be working.
I read somewhere that this could be connected to "SELinux permissive" something . I am sorry, I do not really know what that's about but maybe someone out there could give me a hint as to where I have to look.
I do not need a guide or anything, don't mind learning something on the way
Help would be greatly appreciated.
Thank you guys in advance

Anyone?

Same/similar issue
I am also experiencing the same issue, was able to install Viper and pixel Camera mod, then after no matter what module I install it does not show up in the app drawer atleast, I tried App systemizer , Cloudfare DNS and SF font.. nothing seems to work than the first installed two modules. Tried to install and remove them multiple times.
Cleared magisk cache
installed M<agisk from TWRP multiple times.
tried to install modules from TWRP as well.
I am so new to all these, please dont mind any mistakes.
Thanks.

The same problem I got.How to do to enable camera 2api.

magisk fortnite thread

Hello everyone. I have created this thread (hopefully in the right place) to start a discussion on methods/developing methods to get fortnite to work on a rooted device, with magisk installed. Im currently running Dr. Ketan's rom (android pie) on a samsung galaxy note 9 and for obvious reasons (the fortnite galaxy skin) would like to play a few games and have it work without any hiccups. Im not looking to hack the game or any nonsense like that, so if anyone has a currently functioning method that doesnt require me to reflash stock firmware (as i dont have a pc and had to use a friends to unlock bootloader and such) and play on the unrooted device then re-root and install custom rom

evan5935 said:
Hello everyone. I have created this thread (hopefully in the right place) to start a discussion on methods/developing methods to get fortnite to work on a rooted device, with magisk installed. Im currently running Dr. Ketan's rom (android pie) on a samsung galaxy note 9 and for obvious reasons (the fortnite galaxy skin) would like to play a few games and have it work without any hiccups. Im not looking to hack the game or any nonsense like that, so if anyone has a currently functioning method that doesnt require me to reflash stock firmware (as i dont have a pc and had to use a friends to unlock bootloader and such) and play on the unrooted device then re-root and install custom rom
Click to expand...
Click to collapse
Uhh. Its already working. Atleast for me. You just need to hide magisk manager , hide Fortnite app and installer on magisk hide tab, disable usb debugging, and make sure there isn't magisk named folder or files inside your internal storage. That should do it. I'm on the note 8 and it works just fine

white7561 said:
Uhh. Its already working. Atleast for me. You just need to hide magisk manager , hide Fortnite app and installer on magisk hide tab, disable usb debugging, and make sure there isn't magisk named folder or files inside your internal storage. That should do it. I'm on the note 8 and it works just fine
Click to expand...
Click to collapse
Dang, really? Thanks man!

evan5935 said:
Dang, really? Thanks man!
Click to expand...
Click to collapse
Yep!! Its working on mine ....

white7561 said:
Yep!! Its working on mine ....
Click to expand...
Click to collapse
Its not workin for me bro, i hide magisk manage, have no folders or files named makgisk, or even have magisk in the name, hide the root apps with magisk as well as the fortnite installer and app before i launch each of them. It just deosnt work for me :'(

Are you running in magisk core mode, with adb/root disabled as well?

And what about USB/ADB Debugging? Have you turned that off as well?

white7561 said:
Yep!! Its working on mine ....
Click to expand...
Click to collapse
Didgeridoohan said:
And what about USB/ADB Debugging? Have you turned that off as well?
Click to expand...
Click to collapse
Yes but developer options is still on, does that make a difference? Also, I have not tried with magisk core mode off and root disabled, so if you are doing that then that may also be my issue
Edit: i turned on magisk core mode and disabled root and still does not work. Would having lucky patcher installed be an issue?

evan5935 said:
Yes but developer options is still on, does that make a difference? Also, I have not tried with magisk core mode off and root disabled, so if you are doing that then that may also be my issue
Edit: i turned on magisk core mode and disabled root and still does not work. Would having lucky patcher installed be an issue?
Click to expand...
Click to collapse
Prob yeah ...

white7561 said:
Prob yeah ...
Click to expand...
Click to collapse
Definitely was the issue. Deleted lucly patcher and also the Xposed installer (even though exposed isnt on Pie yet) and that combined with everything else did the trick

evan5935 said:
Definitely was the issue. Deleted lucly patcher and also the Xposed installer (even though exposed isnt on Pie yet) and that combined with everything else did the trick
Click to expand...
Click to collapse
Yep. Also . No xposed . Since it fails the safety net [emoji4]. Well. Happy gaming!! [emoji4][emoji4][emoji4]

Working still Season 9 Magisk 19.1? Not I
Anybody still using this method? I get all the way to the drop then get kicked out "can't sync user profile"
Magisk is hidden in a random folder, installer and game both hidden. Tried with Developer settings off and also with them on. Rooted.
Even Google Pay works so I'm head scratching here if there is a system processes that is now needing hidden or what to play the newest Beta. All help appreciated.

I have the same problem. Google pay is working but fortnite not

I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.

Chuck_C said:
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Click to expand...
Click to collapse
Curious what was your setup? To have it work?

Pvt WhoOkid said:
Curious what was your setup? To have it work?
Click to expand...
Click to collapse
Stock OnePlus 7 pro with magisk and TWRP. Epic launcher and Fortnite both hidden in magisk hide. USB debugging turned off. No modules installed. Just using it for root. Worked fine until last night. Gpay and all other safety net apps work fine. It's just Fortnite. Logged in on a friend's Xbox and a really laggy ipad and could play on both so it's not my account - it's definitely the rooted phone and magisk no longer hides itself from Fortnite.
I'm really irritated with the whole thing because I was so close to finishing the season pass and now I can't play at all.

Here's another fix. These last few updates they have added more things to the blacklist. So remember that they basically scans the internal sdcard etc for MagiskManager folder right? Well now they scan TWRP folder too!! So try renaming it to something else without TWRP in it. And see if it works!. Just tried mine and still working just fine!

white7561 said:
Here's another fix. These last few updates they have added more things to the blacklist. So remember that they basically scans the internal sdcard etc for MagiskManager folder right? Well now they scan TWRP folder too!! So try renaming it to something else without TWRP in it. And see if it works!. Just tried mine and still working just fine!
Click to expand...
Click to collapse
Thanks for posting that. I renamed the folder and now it works again.
Now I need to figure out if I can leave it that way or if I need to keep switching the folder name back and forth to be able to use TWRP correctly.

Chuck_C said:
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Click to expand...
Click to collapse
I have pretty much the same setup as you. Do you happen to get lag here and there? During game play? I was able to get mine working again by renaming the folder for trwp as suggested.

Chuck_C said:
Thanks for posting that. I renamed the folder and now it works again.
Now I need to figure out if I can leave it that way or if I need to keep switching the folder name back and forth to be able to use TWRP correctly.
Click to expand...
Click to collapse
With Tasker or Automate, you can set a trigger to automatically rename folder on start of Fortnite and rename back, after the game is closed.