Related
[Solved] Reinstalled Framework from recovery using the ARHD zip file I had. Works perfectly since then.
I'm using an HTC One (M7) unlocked and rooted. I have the Xposed Installer installed and have been using the Sense Toolbox and a couple of other modules fine until recently.
The sense toolbox (and other modules) worked fine (meaning I could see all the tweaks working), but I had the message saying something like 'The latest version of Xposed is curently not active. Did you install the framework and reboot?'.
When I went into the Xposed Installer and tried installing the framework, the screen would go blank and the phone would restart and I would have the same message in the Installer. All this while, the modules I have installed are working fine.
I tried to uninstall the framework and then reinstall it, but now my modules don't work too and I can't install the framework. It just reboots. No boot-loop or anything. Just a reboot. Same red error message in the Xposed Installer.
I'm not sure if my issue started after I dirty-flashed ARHD 53 (coming from 51) or after I recently updated my Xposed framework.
Any suggestions? I miss my Xposed modules
Thank you for your help.
Use the alternative install method to flash in recovery.
Thank you for the reply. After seeing your reply, I remembered that ARHD gives an option to install Xposed when you flash the ROM, so I went into recovery and flashed Xposed Framework again. It's working now again, although I'm on an older version of the framework.
I'll update the framework and see if it's a problem with the new version. if it is, I'll just go back to the old one.
Edit: Updated the Xposed Framework version to the latest 2.5 and everything is working perfectly now.
[Problem Solved] Thank you.
Thread specifically about finding and solving the issue that some are seeing where the apps and logs screen of SuperSU will load indefinitely, while su access does keep working.
r25txe said:
Hi @Chainfire
I just tried the 2.04BETA to see if my issue was resolved, to no avail.
I was wondering have you had any reports of certain settings not being configurable and the "apps" and "logs" tabs endlessly refreshing, i.e., you cannot see what apps you have approved or denied.
My root does work, I can approve or deny requests normally, it's just I cannot go back if I want to reconfigure an app's root access or review logs. Unchecking the refresh app and logs automatically has no effect.
In the settings, uninstall SuperSU will not work, causes an eventual crash of SuperSU (after quite some time) unless you do a reboot. SuperSU will still be there, too.
I'm a Pro user and unable to set a PIN either as SuperSU will just circle endlessly after trying to set one.
I've been reading about other users' issues mostly related to root access itself, but my issues seem to be interface only.
---------- Post added at 01:30 AM ---------- Previous post was at 01:19 AM ----------
Oh, my ..!
It's working now, I just did another reboot (because SuperSU had become stuck again) and on reboot all was working! :good:
:blush:
I'll redownload the licence and test Pro features tomorrow and report back.
Click to expand...
Click to collapse
r25txe said:
All the issues I described are back now.
With or without licence.
Will continue trying/testing see if I can get a pattern.
This is persisting across four phones, one on Gingerbread.
Click to expand...
Click to collapse
mathuaerknedam said:
I'm also seeing this, in 1.94 and 2.02, but I've not yet tried the 2.04 beta. Sometimes it works. I've tried all sorts of different things to identify a pattern, but I've had no luck.
I've also one instance, just last night, of SuperSU requesting root privileges for itself. I can post a screenshot and some log data if that would help.
Sent from my Nexus S 4G using XDA Free mobile app.
Click to expand...
Click to collapse
xlollomanx said:
Same issue I have, is presented from any version after 1.94. However it does not happen always: sometimes shows granted superuser app sometimes not, happens random.
Click to expand...
Click to collapse
It'd be great if we can get a recap of which SuperSU versions, which devices and kernels and firmwares, are affected. Any information you have is welcome. Let's get this issue sorted out.
@Chainfire So I'll start. I own a Galaxy W with unofficial Cyanogenmod 11 ( http://forum.xda-developers.com/showthread.php?t=2588495) and now I'm using this kernel http://forum.xda-developers.com/showthread.php?t=2593027 (I' ve tried also with stock kernel but the problem persist and is the same). I used SuperSU for years and worked perfectly until v1.94. When I installed v2.0 the problem starts. After that I updated to 2.01 and I tried some beta like 2.04 and 2.05 but the problem still persist.
I hope this can help you, thanks for support.
EDIT: Some kind of Log could help you?
xlollomanx said:
@Chainfire So I'll start. I own a Galaxy W with unofficial Cyanogenmod 11 ( http://forum.xda-developers.com/showthread.php?t=2588495) and now I'm using this kernel http://forum.xda-developers.com/showthread.php?t=2593027 (I' ve tried also with stock kernel but the problem persist and is the same). I used SuperSU for years and worked perfectly until v1.94. When I installed v2.0 the problem starts. After that I updated to 2.01 and I tried some beta like 2.04 and 2.05 but the problem still persist.
I hope this can help you, thanks for support.
EDIT: Some kind of Log could help you?
Click to expand...
Click to collapse
How did you update? Via in-app, Play store, or exclusively ZIP updates? Which recovery are you using? Have you tried making a backup, wiping, and install SuperSU cleanly - does the issue persist?
I've definitely seen this with SuperSU 2.02, and I believe I also saw it with 1.94 (but I can't recall for certain). I've not yet tried 2.04 beta.
I'm using the device, rom, and recovery in my sig. I've see this with several different kernels, including the one in my sig, Marmite 10.6/10.5/10.4/10.3, Matr1x 25 cfs and bfs, Devil Kernel 20131025_VC and Air Kernel Weekly r350.
When I flash a kernel, cwm asks if I want to "fix root". I've reboot both fixed and unfixed, and it doesn't seem to matter.
What else can I try or provide?
Chainfire said:
How did you update? Via in-app, Play store, or exclusively ZIP updates? Which recovery are you using? Have you tried making a backup, wiping, and install SuperSU cleanly - does the issue persist?
Click to expand...
Click to collapse
Now I'm using CWM recovery based (6.0.5.0)
I tested the v1.94 and update v2.0 on a " old rom". Few days later, thinking was my device problem's I performed a full wipe with pristine and installed v2.0 directly from play store, so I could try a cleanly installation of SuperSU (but the problem persist). Here I tried all new versions (I also tried the v1.94, which worked fine, but mainly to uninstall the newer version's as I will explain below) but without success.
I tried in different ways:
I downgraded to v1.94(replacing supersu with root explorer), uninstalled SuperSU, reistalled v1.94(via in-app) and then updated to 2.0 and then v2.01 when update came out from play store.
I downgraded again to v1.94(replacing supersu with root explorer), uninstalled SuperSU and then installed v2.0 from zip-updates. Also tried flashing directly over v1.94 ,without uninstall, from recovery with zip-updates.
I downgraded again to v1.94(replacing supersu with root explorer), uninstalled SuperSU and then installed v2.02 from zip-updates. Also tried flashing directly over v1.94 ,without uninstall, from recovery with zip-updates.
I tried v2.04 and v2.05 with zip-update from recovery by flashing directly over v2.02(this v2.02 is a result from previous test).
I uninstalled SuperSU by replacing supersu with root explorer, installed via in-app v1.94(that work perfectly) and then installed 2.04.
I hope I have answered in the right way in all your questions.
Regards
I have similar bug. I am on SE xperia GB ROM and all previous versions below 2.00 were working fine. After that I started to notice various problems.. For ex. on 2.00+ versions I was always getting "update su binary" notification. I tried to update it in both ways and both were sucessufull and root was working but i still was getting that notification. On last beta (2.05) root stopped to work and all root apps are loading continuously... when I enter to supersu app I get a notification that there is no su binary (but it exists). I install supersu on clean rom from recovery.. Here is the source code..for reference..
https://github.com/feravolt/feralab
Thank you.
Been playing around, haven't replicated so far. A common theme seems to be CM and CWM, though it works fine in my own testing still... sigh.
mathuaerknedam said:
I've definitely seen this with SuperSU 2.02, and I believe I also saw it with 1.94 (but I can't recall for certain). I've not yet tried 2.04 beta.
I'm using the device, rom, and recovery in my sig. I've see this with several different kernels, including the one in my sig, Marmite 10.6/10.5/10.4/10.3, Matr1x 25 cfs and bfs, Devil Kernel 20131025_VC and Air Kernel Weekly r350.
When I flash a kernel, cwm asks if I want to "fix root". I've reboot both fixed and unfixed, and it doesn't seem to matter.
What else can I try or provide?
Click to expand...
Click to collapse
Which installation method do you use for busybox? As I recall, the app you use provides several different methods.
Chainfire said:
Which installation method do you use for busybox? As I recall, the app you use provides several different methods.
Click to expand...
Click to collapse
I just clicked the big install button for a regular install.
Sent from my Nexus S 4G using XDA Free mobile app
Chainfire said:
Which installation method do you use for busybox?
Click to expand...
Click to collapse
That seems like a probable culprit. Maybe if someone installed your version of 'busybox' we might see a difference.
Frank
Installed BusyBox as well ... still working for me ...
Can you guys having this issue post your /data/data/eu.chainfire.supersu/files/supersu.cfg file ?
Very important 3d
Inviato dal mio SM-G900F X-Note 5.0 con Tapatalk
Nothing here
FeraVolt said:
I have similar bug. I am on SE xperia GB ROM and all previous versions below 2.00 were working fine. After that I started to notice various problems.. For ex. on 2.00+ versions I was always getting "update su binary" notification. I tried to update it in both ways and both were sucessufull and root was working but i still was getting that notification. On last beta (2.05) root stopped to work and all root apps are loading continuously... when I enter to supersu app I get a notification that there is no su binary (but it exists). I install supersu on clean rom from recovery.. Here is the source code..for reference..
https://github.com/feravolt/feralab
Click to expand...
Click to collapse
These issues are not related, as the problem we're discussing only applies to Android with SELinux, which Gingerbread doesn't have.
Let me know if v2.06 BETA solved the problem, please!
@r25txe @mathuaerknedam @xlollomanx
Chainfire said:
Let me know if v2.06 BETA solved the problem, please!
Click to expand...
Click to collapse
It works!!!
The problem was never entirely consistent, so I'll keep checking and report back. But so far, so good!
Sent from my Nexus S 4G using XDA Free mobile app
Chainfire said:
Let me know if v2.06 BETA solved the problem, please!
@r25txe @mathuaerknedam @xlollomanx
Click to expand...
Click to collapse
Hi @Chainfire
I just flashed 2.0.5 and the problem is persisting after two full reboots.
What kind of logs would be useful to you if you need them?
r25txe said:
Hi @Chainfire
I just flashed 2.05 and the problem is persisting after two full reboots.
What kind of logs would be useful to you if you need them?
Click to expand...
Click to collapse
Flash 2.06 ?
Did you mistype, or ? If you are actually on 2.06 then I'll have to think some more what the issue could be and how to trace it...
Oh, dear.
I am clearly much too tired to be on XDA! I only noticed that you posted 2.0.6. I will try it after work tomorrow, really need to crash now.
---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------
Oh, I see you´re online, I will flash it right now ...
---------- Post added at 01:02 AM ---------- Previous post was at 12:56 AM ----------
2.06 works!!
(Although, 2.0.4 did this to me, too)
We´ll see how we get on tomorrow
Thank you, @Chainfire
---------- Post added at 01:08 AM ---------- Previous post was at 01:02 AM ----------
Not sure its of use, but here is the cfg file after the flash of 2.06.
https://www.dropbox.com/s/2s3kircndbfjqmm/supersu.cfg?dl=0
Hi everyone!
If you are using a Custom ROM such as CyanogenMod, and are trying to login to Snapchat, you may encounter this error:
"Oh no! Your login temporarily failed, so please try again later. If your login continues to fail, please visit support.snapchat.com/a/failed-login".
The reason why Snapchat won't let you login is because your device has root access, or Xposed Framework installed! Yes! You heard right! Snapchat now blocks devices with root access and Xposed installed!
SOLUTION 1: (CyanogenMod Only)
1. Go into "Settings" and find "Developer Options".
2. Then find "Root Access" and change it to "Disabled".
3. Now attempt to login to Snapchat!
4. Now, if your login was successful, you can now re-enable "Root Access" in "Developer Options".
5. Done!
NOTE: There seems to be a problem with Snapchat force closing on Marshmallow/CM13 Based ROM's, so if this happens to you, I'm sorry I do not know how to fix this, as far as I know, there is no fix for this issue.
SOLUTION 2:
1. Download Xposed Uninstaller.zip from here:
http://forum.xda-developers.com/showthread.php?t=3034811
2. Boot your phone into recovery and flash the Xposed Uninstaller.zip
3. Reboot your phone
4. Done!
NOTE: Once you login to Snapchat, you can reinstall Xposed Framework and everything will work fine.
If you have any problems, please contact me and I will attempt to help you. Thanks everyone!
I can't find root access in my developer options
Hi Uzayr, Are you using CyanogenMod?
Yeah... It keeps force closing... I'm using a rom based on CM13... Is there any way to fix this. I log in, but it force closes itself after I open the app
This seems to be a known problem with Marshmallow/CM13, So as far as I know there is no fix available.
No, Lewdog
---------- Post added at 05:33 PM ---------- Previous post was at 05:33 PM ----------
I used kingroot to root my device
Uzayr_ said:
No, Lewdog
---------- Post added at 05:33 PM ---------- Previous post was at 05:33 PM ----------
I used kingroot to root my device
Click to expand...
Click to collapse
Try using RootCloak
Hey! I have one problem with Snapchat, but I think I've found something that could help to fix it. As many people have noticed in other posts, Snapchat in CM13 based ROMs has FCs, but last night when I powered off WiFi and network conection Snapchat worked and then, when I powered on WIFI and network again, the FCs reappeared. Could it be this relevant to finding a solution? Can it have something to do with the bug of the camera? It happens every time I power off WIFI and network on my phone. Thanks!
Problem still there
Hi I tried using your way to uninstall xposed but the problem for snapchat is still there what do I do
Salmanmalik said:
Hi I tried using your way to uninstall xposed but the problem for snapchat is still there what do I do
Click to expand...
Click to collapse
Yeah me too ! I have uninstalled the Xposed Framework and also the Root Access but nothing happens ! Still the same problem !
Make sure Xposed Framework is completely uninstalled, then uninstall Snapchat, make sure that you do not have SuperSU installed, reboot your device and reinstall Snapchat and see if that works, thanks.
Tried everything....
Ok so. I have an SM-G930FD (international GS7 exynos), with a custom ROM installed effectively making my phone a SM-N930F (or whatever the code is for Note 7 is) or in other words, it's a ROM that ports all the features of the Note 7 including the model number.
Ever since I installed this ROM I've been trying all sorts of things to bypass the Snapchat log in detection.
I first tried RootCloak.... It didn't work. So then I went on to research and found that Xposed may be the culprit. So, I uninstalled Xposed framework.... that too didn't work. Then I thought maybe it's the presence of the Xposed app on my phone..... Still "log in temporarily failed" .....
Finally, I uninstalled Root and the Super SU app..... and guess what.... it still doesn't work....
I even tried switching between the Standard Snapchat App and the Beta Snapchat App.... Still, doesn't work. :crying:
Is there any other way to make snapchat log in work without having to install the stock ROM for my phone? If there's nothing else, ill just assume its the ROM that triggers Snapchats log in protection.
A4ABATTERY said:
Ok so. I have an SM-G930FD (international GS7 exynos), with a custom ROM installed effectively making my phone a SM-N930F (or whatever the code is for Note 7 is) or in other words, it's a ROM that ports all the features of the Note 7 including the model number.
Ever since I installed this ROM I've been trying all sorts of things to bypass the Snapchat log in detection.
I first tried RootCloak.... It didn't work. So then I went on to research and found that Xposed may be the culprit. So, I uninstalled Xposed framework.... that too didn't work. Then I thought maybe it's the presence of the Xposed app on my phone..... Still "log in temporarily failed" .....
Finally, I uninstalled Root and the Super SU app..... and guess what.... it still doesn't work....
I even tried switching between the Standard Snapchat App and the Beta Snapchat App.... Still, doesn't work. :crying:
Is there any other way to make snapchat log in work without having to install the stock ROM for my phone? If there's nothing else, ill just assume its the ROM that triggers Snapchats log in protection.
Click to expand...
Click to collapse
Same question, tried everything...
Im using android 7.1
I use samsung galaxy note 5
MinotaurusRom V7 and Nemesis V2 Kernel
I uninstalled xposed framekwork and xposed application and the supersu and also uninstalled snapchat and still have this ***** login error ??
hadymaher said:
I use samsung galaxy note 5
MinotaurusRom V7 and Nemesis V2 Kernel
I uninstalled xposed framekwork and xposed application and the supersu and also uninstalled snapchat and still have this ***** login error ����
Click to expand...
Click to collapse
Have you made sure that XposedBridge.jar under /system/framework/ has been deleted? And make sure all files are also deleted from /sdcard/Android/data/de.robv.android.xposed.installer/files.
Lewdog45 said:
Have you made sure that XposedBridge.jar under /system/framework/ has been deleted? And make sure all files are also deleted from /sdcard/Android/data/de.robv.android.xposed.installer/files.
Click to expand...
Click to collapse
Thanks for your reply
I checked for these files but they don't exist
hadymaher said:
Thanks for your reply
I checked for these files but they don't exist
Click to expand...
Click to collapse
Hmm... Do you have a Skype account? It's easier to communicate on and I will try to assist you further, thanks.
Lewdog45 said:
Hmm... Do you have a Skype account? It's easier to communicate on and I will try to assist you further, thanks.
Click to expand...
Click to collapse
Sure my skype name is hadymaher1
Thanks for your efforts :good:
Okay my problem is solved thanks to @Lewdog45
he said:
I have a solution, it may be a big process but if you are the only person who use's Snapchat on your device then what you can do is:
1. Uninstall root access on your device
2. Log into Snapchat with your normal account (You should be able to log in once you have removed root access)
3. Once you have logged in on Snapchat, you can Re-root your device, and reinstall Xposed Framework if you wanted
VERY IMPORTANT!
If you log out of Snapchat at anytime while you have root access and Xposed installed, you will have to repeat this process.
And he said about unrooting:
Steps:
1. Open SuperSu
2. Navigate to the "Settings" tab
3. Find the "Cleanup" tab
4. Then click on "Full unroot"
5. Done!
VERY IMPORTANT!
If your device says that it's uninstalling root access for more than 10 minutes, try rebooting your device.
After signing in to snapchat you can re root your phone agian and install xposed without any problem
If this helped please thank him and you can contact him on skype "lewdog45" if the problem still presist.
Hi everyone. I'm trying to run snapchat @CM13. If i disable camera permissions it logs in without problems, but every time i enable the camera Snapchat get force closed. Any idea? This happends with or without root anable
Soo i logged out of my snapchat account to login to a diffrent one but kept saying login temporally failed.
Soo i googled it and it said to unstall XPOSED Framework but i can't becuase i followed a youtube video on how to install the framework without recovery because i can't get one on my phone which is a Bush spira B2 Please help me thank i also uninstalled the xposed app
You can install/remove xposed framework up to Kitcat without having to do it through recovery. Above Kitcat, from lollipop on you can only install and remove xposed through a custom recovery. If you don't have a custom recovery? How did you get it installed?
If you have it on Kitcat or jellybean you can just uninstall it directly without having to bother with recovery
Sent from my iPhone using Tapatalk Pro
---------- Post added at 09:26 PM ---------- Previous post was at 09:26 PM ----------
hateeb123456 said:
Soo i logged out of my snapchat account to login to a diffrent one but kept saying login temporally failed.
Soo i googled it and it said to unstall XPOSED Framework but i can't becuase i followed a youtube video on how to install the framework without recovery because i can't get one on my phone which is a Bush spira B2 Please help me thank i also uninstalled the xposed app
Click to expand...
Click to collapse
Also if you are using some kind of Snapchat add on well they are blocking add-ons and third-party apps so most likely you are locked out of your Snapchat account.
Sent from my iPhone using Tapatalk Pro
I installed xposed thru this video on youtube i simply typed how to install xposed framework on lollipop no custom recovery he makes us install busybox and terninal emulator to install framework and yes i was running snapprefs xposed module and I logged out to login in to another acc now I get this error
Help
hateeb123456 said:
I installed xposed thru this video on youtube i simply typed how to install xposed framework on lollipop no custom recovery he makes us install busybox and terninal emulator to install framework and yes i was running snapprefs xposed module and I logged out to login in to another acc now I get this error
Help
Click to expand...
Click to collapse
Do the same thing you did to install Xposed, but use the uninstall zip found in the Lollipop/Marshmallow Xposed thread. I would assume, based on the fact that uninstalling and installing with recovery is the same, except you flash the uninstall zip when uninstalling.
But if dude above is correct, uninstalling Xposed may not fix your problem.
Hi.
I have a Samsung Galaxy Note 4 N910F, and in which I have installed the Xposed Framework "xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip" well, since I installed it, you can not Start PUBG Mobile. When the "Tencent Games" sign comes out the game closes without showing any error and returns me to the launcher.
When I uninstall Xposed the game goes well again.
What is the problem? Any solution?
More data:
Samsung Galaxy Note 4 N910F Marshmallow 6.0.1.
Custom rom "Note4_ApocalypseX_M_Tron_Pro_v8.1.0 - FINAL".
Xposed Framework "xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125".
Recovery "TWRP 3.2.1-0.
Try rootcloack, it hides xposed in selected apps.
If this doesn't work, maybe it's safetynet related and you can't do anything in that case.
D-Mak said:
Hi.
I have a Samsung Galaxy Note 4 N910F, and in which I have installed the Xposed Framework "xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip" well, since I installed it, you can not Start PUBG Mobile. When the "Tencent Games" sign comes out the game closes without showing any error and returns me to the launcher.
When I uninstall Xposed the game goes well again.
What is the problem? Any solution?
More data:
Samsung Galaxy Note 4 N910F Marshmallow 6.0.1.
Custom rom "Note4_ApocalypseX_M_Tron_Pro_v8.1.0 - FINAL".
Xposed Framework "xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125".
Recovery "TWRP 3.2.1-0.
Click to expand...
Click to collapse
Hii I have the same problem (stock rom) did you find any solution (910 T) note 4
This game has safetynet check like PM GO, you need to uninstall Xposed to play the game. If you're in marshmallow, you can also use rootcloak or something else to hide it.
DARK LIONlol said:
Hii I have the same problem (stock rom) did you find any solution (910 T) note 4
Click to expand...
Click to collapse
No, the only solution is not to use Xposed and put the data in the internal memory.
edison0354 said:
This game has safetynet check like PM GO, you need to uninstall Xposed to play the game. If you're in marshmallow, you can also use rootcloak or something else to hide it.
Click to expand...
Click to collapse
At the time I tried it, but it did not work.
Just curious have you tried from the exposed repo ' no device check ' module. On my S8 with this module it passes CTS profile match (fails basic integrity).
You could try this with root hiding method and clearing the games data and cache and try again and see if it works.
same issue... MM TW ROM not working on PUBG Mobile, Timi and LS Chinese. In Oreo ROM when xpose installed it opens but when you in game 10-20 minutes it will automatically close without saying error or force close. I try many but no one work. So simply don't install/flash xposed framework.
D-Mak said:
No, the only solution is not to use Xposed and put the data in the internal memory.
Click to expand...
Click to collapse
What I can do to disable the stupid dvfs and I didn't find it with es flie can you help (snap dragon) device
spawnlives said:
Just curious have you tried from the exposed repo ' no device check ' module. On my S8 with this module it passes CTS profile match (fails basic integrity).
You could try this with root hiding method and clearing the games data and cache and try again and see if it works.
Click to expand...
Click to collapse
I just tried it and it does not work. It has started the game all right, I got an update of 20Mb, the game asked me to restart, I start it again and when the black letters come out it closes.
spawnlives said:
Just curious have you tried from the exposed repo ' no device check ' module. On my S8 with this module it passes CTS profile match (fails basic integrity).
You could try this with root hiding method and clearing the games data and cache and try again and see if it works.
Click to expand...
Click to collapse
I just tried it and it does not work. It has started the game all right, I got an update of 20Mb, the game asked me to restart, I start it again and when the black letters come out it closes.
spawnlives said:
Just curious have you tried from the exposed repo ' no device check ' module. On my S8 with this module it passes CTS profile match (fails basic integrity).
You could try this with root hiding method and clearing the games data and cache and try again and see if it works.
Click to expand...
Click to collapse
I just tried it and it does not work. It has started the game all right, I got an update of 20Mb, the game asked me to restart, I start it again and when the black letters come out it closes.
I downloaded PUBG Moobil from playstore today all 1.7gb + 20mb update. All installed ok and works for me. Went through setup signed on as guest and started playing (learning to play the game is another story).
I am using a s8 stock nougat 7.0. With latest magisk and rovo's ver 89 exposed.
I have no issues with it running with exposed active.
I don't think the problem is related to safety net or even play store certification as I fail safety net with exposed active (passes when I turn it off). It does not check/detect that my phone is rooted either.
According to the description it is recommended to have 2 GB of memory to run properly as I understand your note4 has 3gb. Running out of memory will cause the game to crash. So I would check your memory . Try and turn off background running apps/services to free up memory.
There are other issues as well like internet connection,overheating to PUBG mobile servers that can cause issues but I would start with your memory first.
Echoing the same problem. Systemless Xposed v87.3 stops the game from running until i uninstalled Xposed. My phone is an Samsung A8, model SM-A800I, has 2GB RAM.
---------- Post added at 11:56 PM ---------- Previous post was at 11:55 PM ----------
spawnlives said:
I downloaded PUBG Moobil from playstore today all 1.7gb + 20mb update. All installed ok and works for me. Went through setup signed on as guest and started playing (learning to play the game is another story).
I am using a s8 stock nougat 7.0. With latest magisk and rovo's ver 89 exposed.
I have no issues with it running with exposed active.
I don't think the problem is related to safety net or even play store certification as I fail safety net with exposed active (passes when I turn it off). It does not check/detect that my phone is rooted either.
According to the description it is recommended to have 2 GB of memory to run properly as I understand your note4 has 3gb. Running out of memory will cause the game to crash. So I would check your memory . Try and turn off background running apps/services to free up memory.
There are other issues as well like internet connection,overheating to PUBG mobile servers that can cause issues but I would start with your memory first.
Click to expand...
Click to collapse
For some reason i cannot quote your reply with the former answer, but as i said above, my 2GB device runs fine, but stops when Xposed is installed, specifically v87.3
Found a way to fix, i think?
I upgraded Xposed from v87.3 to v89.3 via Magisk ( even though when i first tried v89.3, it caused bootloop, so i had to use v87.3, but for some reason when i upgraded from v87.3, it works fine. ) and the game now is playable again while having all xposed modules working properly
theheartbenvn said:
Found a way to fix, i think?
I upgraded Xposed from v87.3 to v89.3 via Magisk ( even though when i first tried v89.3, it caused bootloop, so i had to use v87.3, but for some reason when i upgraded from v87.3, it works fine. ) and the game now is playable again while having all xposed modules working properly
Click to expand...
Click to collapse
As I've said it works for me as well. The exposed version you updated to is the same as mine. Rovo"s ver 89 is the same as magisk ver 89.3.
It seems then to be an issue with exposed for marsmellow and possibly lower as ver 89 (magisk 89.3) is for nougat.
If this is the case then it won't matter which exposed version for marsmellow you install ( ie: rovo's, wanam's or systemless ) it probably won't work unless exposed is uninstalled. The only way to find out what is going on is to provide a logcat of the game when it crashes with exposed.
theheartbenvn said:
Found a way to fix, i think?
I upgraded Xposed from v87.3 to v89.3 via Magisk ( even though when i first tried v89.3, it caused bootloop, so i had to use v87.3, but for some reason when i upgraded from v87.3, it works fine. ) and the game now is playable again while having all xposed modules working properly
Click to expand...
Click to collapse
This sounds great. Could you please share full guide and on this.
theheartbenvn said:
Found a way to fix, i think?
I upgraded Xposed from v87.3 to v89.3 via Magisk ( even though when i first tried v89.3, it caused bootloop, so i had to use v87.3, but for some reason when i upgraded from v87.3, it works fine. ) and the game now is playable again while having all xposed modules working properly
Click to expand...
Click to collapse
What phone and ROM do you have?
spawnlives said:
As I've said it works for me as well. The exposed version you updated to is the same as mine. Rovo"s ver 89 is the same as magisk ver 89.3.
It seems then to be an issue with exposed for marsmellow and possibly lower as ver 89 (magisk 89.3) is for nougat.
If this is the case then it won't matter which exposed version for marsmellow you install ( ie: rovo's, wanam's or systemless ) it probably won't work unless exposed is uninstalled. The only way to find out what is going on is to provide a logcat of the game when it crashes with exposed.
Click to expand...
Click to collapse
I'm using Marshmallow 6.0.1 and switching versions helped me.
---------- Post added at 07:35 PM ---------- Previous post was at 07:27 PM ----------
Cybercrat said:
This sounds great. Could you please share full guide and on this.
Click to expand...
Click to collapse
If you rooted your phone using Magisk, and you have an Samsung phone, you need to install Systemless Xposed v87.3 via Magisk ( you can find this version in Systemless Xposed XDA thread ), then after the installation, upgrade the version to 89.3 via Download section in Magisk, and it should be working. Remember though, do not clear Dalvik-cache after you do this, because it'd make your phone stuck into bootloop if you're using Samsung and are on version 7.0 and older, since v89.3 for some reason doesn't work with the device having specified conditions when first installed, but works when upgraded to. I suggest you should install Magisk Manager for Recovery Module in case you run into that problem, so you can safely uninstall xposed if you have to clear dalvik. And by the way, can anyone test if older versions of xposed work?
---------- Post added at 07:37 PM ---------- Previous post was at 07:35 PM ----------
Kaper_20 said:
What phone and ROM do you have?
Click to expand...
Click to collapse
I have a Samsung Galaxy A8 ( 2015 version ), model SM-A800I, and currently operating on the lastest version, 6.0.1
theheartbenvn said:
I'm using Marshmallow 6.0.1 and switching versions helped me.
---------- Post added at 07:35 PM ---------- Previous post was at 07:27 PM ----------
If you rooted your phone using Magisk, and you have an Samsung phone, you need to install Systemless Xposed v87.3 via Magisk ( you can find this version in Systemless Xposed XDA thread ), then after the installation, upgrade the version to 89.3 via Download section in Magisk, and it should be working. Remember though, do not clear Dalvik-cache after you do this, because it'd make your phone stuck into bootloop if you're using Samsung and are on version 7.0 and older, since v89.3 for some reason doesn't work with the device having specified conditions when first installed, but works when upgraded to. I suggest you should install Magisk Manager for Recovery Module in case you run into that problem, so you can safely uninstall xposed if you have to clear dalvik. And by the way, can anyone test if older versions of xposed work?
---------- Post added at 07:37 PM ---------- Previous post was at 07:35 PM ----------
I have a Samsung Galaxy A8 ( 2015 version ), model SM-A800I, and currently operating on the lastest version, 6.0.1
Click to expand...
Click to collapse
THANK YOU VERY MUCH SIR!!!
It worked with the instruction you gave.
I tested with Galaxy Note 4 N910U 6.0.1 with latest security update (1/08/17)
Magisk 16.0 - Magisk Manager 5.8.3 - Xposed 89.3
And yes, DON'T clear Dalvik-Cache or a thermo nuclear disaster will happen.
edit:
Now when I check SafetyNet trough Magisk, it says "The answer is not valid".
Before updating xposed, at least it showed that safetynet did not pass the tests.
meh... i dont care safetynet.