Related
Hi all
Relative newbie here with incredibly frustrating issue that has wasted many of my hours recently!
I saw this a thread about getting sky go (a UK video streaming service) working on a nexus 10 by spoofing build prop to think it's a nexus 7http://forum.xda-developers.com/showthread.php?t=2045403
I flashed stock rom from Leapinlar's great thread (http://forum.xda-developers.com/showthread.php?t=2062613) then rooted with very green's equally great zip (http://forum.xda-developers.com/showthread.php?t=2437575).
Used device spoofer to switch build prop to nexus 7 and hey presto, skygo appears in play store - whoopee!
The problems come when I look to remove root - I used supersu to perform full uproot, reboot, clear cache, factory reset etc but whatever I try, skygo still gives me an error message saying my device is rooted.
Does anyone have any idea what might be causing this despite full unroot? Could it be the fact that the above process leaves me with cyanogenboot / non stock recovery? If so is there any way of rooting and spoofing whilst maintaining stock boot/recovery?
Thanks in advance for your help!
Mike
Sky use a number of tricks to work out if an device has been tampered with. The GS3 and Sky Go (plus their other apps) have issues with other recoveries.
artesea said:
Sky use a number of tricks to work out if an device has been tampered with. The GS3 and Sky Go (plus their other apps) have issues with other recoveries.
Click to expand...
Click to collapse
Do you know whether there is any way of modifying the build prop without ending up with a non stock recovery?
If I can root and unroot without ending up with a custom recovery I think it would work?
Hello,
You could keep your device rooted. Just install this app on the Play Store, dubbed Hide my Root. It's a little bit of hassle, but every time you want to use Sky Go, within the app select "Hide su binary" then click on "Uninstall super user".
Once you're done watching Sky Go, and want your root privileges back, just restore SU Binary, and reinstall super user.
All the best.
HiddenG said:
Hello,
You could keep your device rooted. Just install this app on the Play Store, dubbed Hide My Root. It's a little bit of hassle, but every time you want to use Sky Go, within the app select "Hide su binary" then click on "Uninstall super user".
Once you're done watching Sky Go, and want your root privileges back, just restore SU Binary, and reinstall super user.
All the best.
Click to expand...
Click to collapse
Thanks for your reply, much appreciated.
Unfortunately this does not work - SkyGo still sees my HD+ as being rooted.
So Hide My Root doesn't work, could it potentially be due to Cyanoboot? Does anyone know how to create a "stock" root zip with build props spoofed to Nexus 7?
Thanks!
Has anybody had any luck getting SkyGo to work on a Nook HD+?
grimem said:
Thanks for your reply, much appreciated.
Unfortunately this does not work - SkyGo still sees my HD+ as being rooted.
So Hide My Root doesn't work, could it potentially be due to Cyanoboot? Does anyone know how to create a "stock" root zip with build props spoofed to Nexus 7?
Thanks!
Click to expand...
Click to collapse
It could infact be due to you have a custom recovery and YES of course you can have root and have stock recovery, just install stock nexus 7 rom and root through ODIN and choose not to install cwm/phils/ect also please uninstall busybox sky go also looks for this.
Another note is apps like hidemyroot dont work on android roms nwer than 4.2 for example if you have a 4.3 rom youre screwed
Sky Go now on Nook HD+
Hi all
Anyone with an unrooted stock HD+ able to confirm whether SkyGo is now working since they released the Tablet version with wider compatability yesterday? Now shows as available to download on Nook HD+ but I'm running a custom ROM at the moment so unable to test out as it won't work on rooted devices . . . . .
grimem said:
Hi all
Anyone with an unrooted stock HD+ able to confirm whether SkyGo is now working since they released the Tablet version with wider compatability yesterday? Now shows as available to download on Nook HD+ but I'm running a custom ROM at the moment so unable to test out as it won't work on rooted devices . . . . .
Click to expand...
Click to collapse
I reverted to stock to get it working - works really well! - occasional minor glitches starting a stream but from there in it's good - the quality especially on the on demand stuff is really good compared to bbc player, itv player etc...
edit:
fwiw I'm running at the moment with unknown sources enabled (ITV Player claims to be incompatible with my device running stock - so I side loaded it, works fine) and cwm installed on the recovery - it works fine with those. I expect you could root stock and use a root hiding app and it would still work based on peoples results with the mobile version.
now it's just a matter of getting stock into a usable state - I think CM was a tiny bit zippier, but most of my issues with the stock UI have been resolved by installing apex launcher. Just need to figure out a way to change the lock screen, and maybe remove the status bar and I'll be sorted
jazzy2fives said:
I reverted to stock to get it working - works really well! - occasional minor glitches starting a stream but from there in it's good - the quality especially on the on demand stuff is really good compared to bbc player, itv player etc...
edit:
fwiw I'm running at the moment with unknown sources enabled (ITV Player claims to be incompatible with my device running stock - so I side loaded it, works fine) and cwm installed on the recovery - it works fine with those. I expect you could root stock and use a root hiding app and it would still work based on peoples results with the mobile version.
now it's just a matter of getting stock into a usable state - I think CM was a tiny bit zippier, but most of my issues with the stock UI have been resolved by installing apex launcher. Just need to figure out a way to change the lock screen, and maybe remove the status bar and I'll be sorted
Click to expand...
Click to collapse
Great, thanks for your feedback. Good news!
I'll probably look to have stock on sd boot card for the occasions I want to use skygo then
unknown sources
jazzy2fives said:
I reverted to stock to get it working - works really well! - occasional minor glitches starting a stream but from there in it's good - the quality especially on the on demand stuff is really good compared to bbc player, itv player etc...
edit:
fwiw I'm running at the moment with unknown sources enabled (ITV Player claims to be incompatible with my device running stock - so I side loaded it, works fine) and cwm installed on the recovery - it works fine with those. I expect you could root stock and use a root hiding app and it would still work based on peoples results with the mobile version.
now it's just a matter of getting stock into a usable state - I think CM was a tiny bit zippier, but most of my issues with the stock UI have been resolved by installing apex launcher. Just need to figure out a way to change the lock screen, and maybe remove the status bar and I'll be sorted
Click to expand...
Click to collapse
Hi, can you tell me how you activated unknown sources on your unrooted stock nook, thanks in advance
peter8988 said:
Hi, can you tell me how you activated unknown sources on your unrooted stock nook, thanks in advance
Click to expand...
Click to collapse
If you go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD per item 1a, you can use that to flash my Enable Unknown Sources zip without being rooted.
Sent from my BN NookHD+ using XDA Premium HD app
dont work try'd it loads also rootcloak aswell all useless
Q&A for [ROM][Lollipop][Z3C] Cyanogenmod 12 - Nightly
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][Lollipop][Z3C] Cyanogenmod 12 - Nightly. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Ciao Guys,
actually I have rEctiFy ROM with clockworkmod recovery..do I have to flash anyway the cyanogen boot.img ?
mauroalpha said:
Ciao Guys,
actually I have rEctiFy ROM with clockworkmod recovery..do I have to flash anyway the cyanogen boot.img ?
Click to expand...
Click to collapse
I think you do. I tried it once in cwm and it failed, it could also have been a different issue but it works fine with the boot.img of the zip. Just keep in mind to store the zip on the internal storage before you flash the kernel and after wiping it.and that the recovery menu is very dim, you should avoid bright conditions.
Video or pictures
I would like to see how the cyanogenmod works on the Z3 Compact. Could you send me a video or some pictures?
Thanks!
Lukas
I have still some problems with my bluetooth headset. The connection and the controlls works, but often i dont get sound.
supermanlovers said:
I have still some problems with my bluetooth headset. The connection and the controlls works, but often i dont get sound.
Click to expand...
Click to collapse
My Bluetooth headset was acting up when i had the built in equalizer (AudioFx) turned on , try to turn it off and see if it helps.
I also installed viper4android instead which is way better.
Thanks, this worked for me
2mal16 said:
I think you do. I tried it once in cwm and it failed, it could also have been a different issue but it works fine with the boot.img of the zip. Just keep in mind to store the zip on the internal storage before you flash the kernel and after wiping it.and that the recovery menu is very dim, you should avoid bright conditions.
Click to expand...
Click to collapse
I've just installed with cyano recovery, everything was fine..
I want to report that somethimes the mic recorder loss some seconds while i'm using it..i've just updated now the nightly
need to test it again
anyway i'm really happy, the phone for me is now really faster than the stock rom.
Camera button
Anyone figure out how to remap the camera button yet?
So i'm kind of a noob here I guess but I thought to install this one would need to have their device rooted (like I had) and I have it on my device working perfectly, the only problem is the phone is telling me that it is not rooted and thus not letting me use titanium backup and greenify etc.
Is it just me, or is the Auto Updater not rebooting to recovery after downloading the cm-12-20150214-NIGHTLY-z3c -
I did extract and ABD'flashed the boot.img
And theres still an issue with the LED brightness and audio engine wakeup ( Sound seems dim at first, and sometimes notification audio is skipped, almost like it is in hibernation and cant always get out of it ) , cant seem to find it in the fixlog or changelog either
I just got cm12 setup on my galaxy tab 8.4, the only issue i notice thus far is that im finding it impossible to set a different wallpaper on my lockscreen from my gallery pics... If i want to use one of my personal backgrounds i have to use the same as my homescreen. The only way to change just the lockscreen background is to pick one from a theme i downloaded but that option sucks because i never use theme backgrounds... Anyone have a workaround or is that something well have to wait on in another nightly? I was able to do this easily in cm11, just had to go to lockscreen in settings and themes and i could pick it there
kiliimanjaro said:
So i'm kind of a noob here I guess but I thought to install this one would need to have their device rooted (like I had) and I have it on my device working perfectly, the only problem is the phone is telling me that it is not rooted and thus not letting me use titanium backup and greenify etc.
Click to expand...
Click to collapse
Go to Settings, Developer Options, then a few settings from the top you will see "Root access", click it and choose "Apps and ADB" or just "Apps only" (if you don't use ADB).
After root access is enabled you can install SuperSU from the Play Store (or just use the CM root access if you don't want SuperSU).....
Thanks that worked perfectly!
Another problem though (or else me just being silly and overlooking something simple) that when I boot to recovery it brings up the Cyanogenmod Recovery and there is no option to Backup my files. The only options I have are to wipe everything or reboot.
kiliimanjaro said:
Thanks that worked perfectly!
Another problem though (or else me just being silly and overlooking something simple) that when I boot to recovery it brings up the Cyanogenmod Recovery and there is no option to Backup my files. The only options I have are to wipe everything or reboot.
Click to expand...
Click to collapse
When you flash boot.img from the nightly .zip file you get the CM Recovery. You are correct in that there is no backup option. Use Titanium or some other app to back up your stuff. You can also use a different recovery but you may run into a different problem where the phone identifies itself as "aries" and won't flash the ROM. The CM Recovery takes care of that problem.
Anyone found a fix to the dim notification led issue? I think its related to the CM recovery. Anyone that can confirm this issue aswell?
I have a tab pro 8.4 running cm12 latest nightlies and i cant get adblock plus to work on it. Ive tried everything. It ran beautifully on cm 11 but on cm12 it FCs either right after u launch it or sometimes i can almost get done downloading the site block list. I have the wifi only version of the sm-t320 if that helps. Any ideas anyone? Either a way to fix it or an alternative app?
jflow36 said:
I have a tab pro 8.4 running cm12 latest nightlies and i cant get adblock plus to work on it. Ive tried everything. It ran beautifully on cm 11 but on cm12 it FCs either right after u launch it or sometimes i can almost get done downloading the site block list. I have the wifi only version of the sm-t320 if that helps. Any ideas anyone? Either a way to fix it or an alternative app?
Click to expand...
Click to collapse
try adaway (the newest dev build version) from this thread: http://forum.xda-developers.com/showthread.php?t=2190753
I think it worked for me when i was running cm 12.
firsty said:
Anyone found a fix to the dim notification led issue? I think its related to the CM recovery. Anyone that can confirm this issue aswell?
Click to expand...
Click to collapse
+1. Loving it but the notification LED is basically invisible compared to the stock ROM. Anyone know of a fix for this?
A couple of issues I've run into is sometimes bluetooth audio gets sped-up so my music sounds like it is playing a 2x speed (Google play music) and I'm unable to activate any accessibility services (I can get into the cancel or ok screen but can't click ok). Anybody else have these or know a workaround?
Hi all.
I installed cm13 on my mi5 pro yesterday. Looking good so far. I only have minor issues. The first and most important is I can't swap the back and recent button. I've already got used to miui method ( back on the right, recent button on the left).
How can I change them on cm13? Unfortunately closed+gravity can't help me, because after installing them my banking app (Barclay's) thinks that my phone is rooted and closes with an FC. I've also tried the buttons on the screen option, but in this way I lose screen size, though I can change the buttons I believe.
The other small issue is that I don't really like the menu in this alphabetical order system. Can I use something else instead? Like what is in Nova launcher, just a normalenu, nothing else.
Thanks for the help in advance.
Cheers!
the first issue is related to kernel... when cm will be based on the kernel released from xiaomi, the problem will be solved. don't worry, developers are working on it
I found the a method and it is working:
https://www.androidfilehost.com/?fid=457084094631642269
GrooveHero said:
Hi all.
I installed cm13 on my mi5 pro yesterday. Looking good so far. I only have minor issues. The first and most important is I can't swap the back and recent button. I've already got used to miui method ( back on the right, recent button on the left).
How can I change them on cm13? Unfortunately closed+gravity can't help me, because after installing them my banking app (Barclay's) thinks that my phone is rooted and closes with an FC. I've also tried the buttons on the screen option, but in this way I lose screen size, though I can change the buttons I believe.
The other small issue is that I don't really like the menu in this alphabetical order system. Can I use something else instead? Like what is in Nova launcher, just a normalenu, nothing else.
Thanks for the help in advance.
Cheers!
Click to expand...
Click to collapse
For the drawer style you can change that in the launcher's settings. Long press a free spot on your home screen, then press settings and change style to "compact".
This swaps the two capacitive buttons around to xiaomi setup instead of Google
you can also find it on this url: https://store.shade.sh/mi5/ from the unofficial cm13 weekly build thread if you do not wish to download it from myself
Thank you guys its working like a miracle.
Now I have another problem, but this time it looks massive.
So my problem is that cm13 is pre rooted when you install it. Well, I have no problem with it, but unfortunately my banking app ( Barclay's) has. I can't use it, because it says rooted device not supported. I've already checked developer options, and root access is disabled, but this doesn't help, I still have issues with the app. I tried flash SuperSU+binaries from twrp, opened app after flash and use full unroot, same problem, banking app thinks my phone is still rooted. I'm thinking about trying out the slim (aosp based) ROM if I can't find any working method.
Can you guys help me with this?
Thank you one again
GrooveHero said:
Thank you guys its working like a miracle.
Now I have another problem, but this time it looks massive.
So my problem is that cm13 is pre rooted when you install it. Well, I have no problem with it, but unfortunately my banking app ( Barclay's) has. I can't use it, because it says rooted device not supported. I've already checked developer options, and root access is disabled, but this doesn't help, I still have issues with the app. I tried flash SuperSU+binaries from twrp, opened app after flash and use full unroot, same problem, banking app thinks my phone is still rooted. I'm thinking about trying out the slim (aosp based) ROM if I can't find any working method.
Can you guys help me with this?
Thank you one again
Click to expand...
Click to collapse
Root cloak via xposed maybe? Not sure if still supported though!
Harrynowl said:
This swaps the two capacitive buttons around to xiaomi setup instead of Google
you can also find it on this from the unofficial cm13 weekly build thread if you do not wish to download it from myself
Click to expand...
Click to collapse
great! thank you very much!
Harrynowl said:
Root cloak via xposed maybe? Not sure if still supported though!
Click to expand...
Click to collapse
Tried out this method, but as soon as I tried to start banking app, it closed with an fc. Yes I remember now, that was the problem few days back.
Hm...I can't think anything else..
GrooveHero said:
Tried out this method, but as soon as I tried to start banking app, it closed with an fc. Yes I remember now, that was the problem few days back.
Hm...I can't think anything else..
Click to expand...
Click to collapse
I'm unsure, sorry!
GrooveHero said:
Tried out this method, but as soon as I tried to start banking app, it closed with an fc. Yes I remember now, that was the problem few days back.
Hm...I can't think anything else..
Click to expand...
Click to collapse
Try using shade.sh's userbuilds. They are built without built in root. They are under the category "userbuilds" on his website.
Success!
I had to install aosp to to realize what's the problem here. After I did that the same problem happened.: Banking app says my phone is rooted. So I tried doing the same methods on aosp what I did on cm13, except Xposed+gravity because I knew my apps gonna FC. So I tried safe unroot apk from play store, no luck. I also tried this app the night before.
Then i thought maybe I should enable root in developer options, because yesterday morning with this was a half success, Barclays mobile banking app( debit card) said, the device is rooted, I touched ok, then it started without any problems. It was only half success, because the other app Barclaycard (credit card) didn't work, same problem: the phone is rooted. So I tried out the following, and that was the complete success:
Enabled root access for apps only in dev options than i started safe unroot from play->everything's working like a charm.
Thank you guys for help!
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk
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.