Have you been notified to update your Remote Play app on your Android after the recent 4.50 firmware update? Are you having problems running it without being greeted by an error? I'd like you to give this a try. It worked for me. Today I'd like to share a module that should solve the problem.
This module allows PlayStation Remote Play to start on a rooted device running unsupported stock firmware or a custom ROM with Magisk installed and Sony Framework Module installed. Just make sure the Remote Play app is checked in the Magisk Hide section of Magisk Manager. This module might also allow PlayStation Vue to work on custom ROMs and rooted devices. This module might or might not work on your device. I should've specified that earlier. I only tested it on one device, my Nexus 5X. Users with different devices are reporting success.
I've only tested this on my Google Nexus 5X running Pure Nexus, a custom 7.1.1 Nougat ROM. There was no need to downgrade to Marshmallow and install Xposed Framework with RootCloak with my solution.
How did I find this solution?
I noticed at some point that even users with different ROMs on the same device got different results. I started looking at build.prop after a while and noticed one specific line that stood out.
Code:
[B]ro.build.tags=test-keys[/B]
I remember seeing somewhere that PlayStation Vue would work if this build.prop line was changed to release instead of test. I thought it would make perfect sense if changing this could also fix the problem with Remote Play. Since both were Sony apps I figured this was going to narrow down the problem.
Code:
[B]ro.build.tags=release-keys[/B]
After saving the changes I rebooted my device, started the Remote Play app, and it worked! It booted past the error screen. This mod does not require a modded .apk of Sony's Remote Play app. You can use the same one you would download from the Play Store after installing the Sony Framework module from Magisk Manager.
I made a Magisk module to make this more simple and clean. It changes the build.prop line for you, just flash it with Magisk Manager or with TWRP Recovery.
Instructions
1.) Install Sony Framework module from Magisk Manager. Reboot.
2.) Install RemotePlayEnabler module. Reboot.
3.) Open Play Store and install Remote Play like any normal app.
4.) In Magisk Manager, go to Magisk Hide and check the Remote Play app, PlayStation app, and PS Messenger app.
5.) Open Remote Play app and check if it works for you.
Click to expand...
Click to collapse
Info from another thread about using DS4 with the official Remote Play app- kind of. There are two methods. Thank @RoyJ for this info
RoyJ said:
Info from another thread about using DS4 with the official Remote Play app- kind of. AFAIK, this requires you be on the same WiFi network and within reasonable (Bluetooth) range of the PS4. If that's not correct let me know, I'll edit the post.
Second account method;
-Make a second PSN account for free. Log into the 2nd account on the PS4 itself.
-Open the Remote Play app & go to settings. Hit "Sign In" (if you have the PlayStation app logged in to your main account it should automatically log you into that account. Log out and once again "Sign In" this time using your second account. This time around it'll prompt your for a username and password.
-On the PS4 (while logged into 2nd account) go to "Settings > Remote Play Connection Settings > Add Device". It'll display a code you'll use for the next step
-Click Next / Skip while the Remote Play app is trying to connect to the PS4 and manually register it. It will ask for the code from earlier. Enter it and you should now be streaming the PS4 through the app.
-Press the PS button on the DS4 and it should switch back over to your main account, while keeping the remote play going.
It works, I just tested it. I only tested it one room away from my PS4. I believe this works since your controller is technically connected to the PS4 itself, but the 2nd user started remote play. 1st user takes back control with the DS4, but it doesn't kill the link to remote play. The controller still has to be close enough to the PS4 to be picked up with Bluetooth, it doesn't actually connect it to the phone.
To whom it may concern..
Click to expand...
Click to collapse
At this point I will offer no further support. My goal was to create this module in order to boot up the latest Remote Play on my Nexus 5X after Sony released PS4 Firmware 4.50 and updated the Remote Play app to 2.0.0 and I successfully got it working. I hope others can have the same results on their device otherwise I'm sorry but I can't help you any further.
If my module works for you and if you would like to show your appreciation, hit thanks and feel free to send me a donation. I also accept Bitcoin payments.
GitHub: https://github.com/AndroiDeputies
Reserved
@RoyJ and @Kropolis could you let me know if this works for you? You guys were patient and put up with a lot in the other thread. I'd like to give you guys access first.
Edit: Not to be picky about the viewers on this thread, but I'm sure we'd like to avoid some of the other interesting characters that popped up in the other forum.
I tried it but it doesn't work.
I did everything correctly. Installed Magisk, then Sony framework, then the remote play enabler, installed the remote play app from play store, then I checked the app in Magisk hide but I get error 88001003.
Sent from my Nexus 6 using Tapatalk
Works on my Nexus 6P. Debloated stock ROM based on latest stable images. Magisk v11.5. Allows the official 2.0 apk to run just fine.
---------- Post added at 06:14 AM ---------- Previous post was at 06:12 AM ----------
slekkas said:
I tried it but it doesn't work.
I did everything correctly. Installed Magisk, then Sony framework, then the remote play enabler, installed the remote play app from play store, then I checked the app in Magisk hide but I get error 88001003.
Click to expand...
Click to collapse
I don't know if you have any of them installed, but I also added PlayStation & PS Messages to Magisk Hide as well. Rebooted and it works.
RoyJ said:
Works on my Nexus 6P. Debloated stock ROM based on latest stable images. Magisk v11.5. Allows the official 2.0 apk to run just fine.
---------- Post added at 06:14 AM ---------- Previous post was at 06:12 AM ----------
I don't know if you have any of them installed, but I also added PlayStation & PS Messages to Magisk Hide as well. Rebooted and it works.
Click to expand...
Click to collapse
Damn it, that gave me hope but nothing. I also checked the playstation app and playstation messenger app but still get the error.
slekkas said:
I tried it but it doesn't work.
I did everything correctly. Installed Magisk, then Sony framework, then the remote play enabler, installed the remote play app from play store, then I checked the app in Magisk hide but I get error 88001003.
Click to expand...
Click to collapse
Earlier my friend @bgboii tried it with his Nexus 6P and it failed for him as well. But he was also running Dirty Unicorns when all of my modules failed to work for him. I'm not sure if that helps.
RoyJ said:
Works on my Nexus 6P. Debloated stock ROM based on latest stable images. Magisk v11.5. Allows the official 2.0 apk to run just fine.
---------- Post added at 06:14 AM ---------- Previous post was at 06:12 AM ----------
I don't know if you have any of them installed, but I also added PlayStation & PS Messages to Magisk Hide as well. Rebooted and it works.
Click to expand...
Click to collapse
I'm glad it works for you. Also on the Nexus 6P that's great. And I believe I also checked the same apps you checked in Magisk Hide as well, I'll update the OP accordingly. It's a good just-in-case measure for some.
Sent from my LG Nexus 5X using XDA Labs
leolawliet said:
Earlier my friend @bgboii tried it with his Nexus 6P and it failed for him as well. But he was also running Dirty Unicorns when all of my modules failed to work for him. I'm not sure if that helps.
I'm glad it works for you. Also on the Nexus 6P that's great. And I believe I also checked the same apps you checked in Magisk Hide as well, I'll update the OP accordingly. It's a good just-in-case measure for some.
Sent from my LG Nexus 5X using XDA Labs
Click to expand...
Click to collapse
What is dirty unicorns?
I guess it's a Rom,
I'm using chroma.
Here's my ROM: https://forum.xda-developers.com/showpost.php?p=71356972&postcount=1
The kernel included with it: https://forum.xda-developers.com/showpost.php?p=68138956&postcount=1
Magisk v11.5. I installed Magisk Manager from the Play Store and used it to download v11.1 a few days ago and then to v11.5 today.
No other root or anything like that (ROM doesn't come with root). Enabled Magisk Hide, BusyBox & Systemless Hosts from Magisk settings. Rebooted, confirmed SafetyNet passed, added back my apps. Logged into all PlayStation related apps and added them to Magisk Hide and rebooted. No issues using Remote Play. I'll see if the mic feature works too.
My understanding is the 88001003 error code is the root check but I could be mistaken. Currently my Nexus 5x is rooted using Xposed and working well. I use my older Nexus 5 must of the time so if I end up upgrading the 5x to Android 7 I'll definitely give this a try since it worked on your device.
Sent from my Nexus 5X using Tapatalk
slekkas said:
What is dirty unicorns?
I guess it's a Rom,
I'm using chroma.
Click to expand...
Click to collapse
Yes, it's another custom ROM available for our devices. I've never tried with Chroma before, what Root method do you use for Magisk?
RoyJ said:
Here's my ROM: https://forum.xda-developers.com/showpost.php?p=71356972&postcount=1
The kernel included with it: https://forum.xda-developers.com/showpost.php?p=68138956&postcount=1
Magisk v11.5. I installed Magisk Manager from the Play Store and used it to download v11.1 a few days ago and then to v11.5 today.
No other root or anything like that (ROM doesn't come with root). Enabled Magisk Hide, BusyBox & Systemless Hosts from Magisk settings. Rebooted, confirmed SafetyNet passed, added back my apps. Logged into all PlayStation related apps and added them to Magisk Hide and rebooted. No issues using Remote Play. I'll see if the mic feature works too.
Click to expand...
Click to collapse
I miss Flash Kernel. I haven't seen an update for my device since December. I'm just using Pure Nexus with Jolla Kernel and Arise audio mods. Very few Root tweaks so I still rely on MagiskSU for anything that might require system mods.
Sent from my LG Nexus 5X using XDA Labs
leolawliet said:
Yes, it's another custom ROM available for our devices. I've never tried with Chroma before, what Root method do you use for Magisk?
I miss Flash Kernel. I haven't seen an update for my device since December. I'm just using Pure Nexus with Jolla Kernel and Arise audio mods. Very few Root tweaks so I still rely on MagiskSU for anything that might require system mods.
Sent from my LG Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I use supersu
In the old version of Magisk there was a toggle to hide root. I can't seem to find it on the new one. I'm using a TV Go app to watch TV on my phone and it worked fine with the previous version. Now it's telling me that the app is not working on rooted devices which means something I'm not doing right in Magisk.
Kropolis said:
My understanding is the 88001003 error code is the root check but I could be mistaken. Currently my Nexus 5x is rooted using Xposed and working well. I use my older Nexus 5 must of the time so if I end up upgrading the 5x to Android 7 I'll definitely give this a try since it worked on your device.
Click to expand...
Click to collapse
The root check might not be the only thing being checked. That build.prop line I edited is usually set to test-keys for custom ROMs, so it was clever for Sony to use that in addition to the root check to determine if the device was running modified software. That's just my guess but this theory helped me figure out the problem on my end.
Sent from my LG Nexus 5X using XDA Labs
slekkas said:
I use supersu
In the old version of Magisk there was a toggle to hide root. I can't seem to find it on the new one. I'm using a TV Go app to watch TV on my phone and it worked fine with the previous version. Now it's telling me that the app is not working on rooted devices which means something I'm not doing right in Magisk.
Click to expand...
Click to collapse
SuperSU is the problem. You can't hide root from SuperSU even with the latest Magisk. You will need MagiskSU to get this working.
Sent from my LG Nexus 5X using XDA Labs
leolawliet said:
SuperSU is the problem. You can't hide root from SuperSU even with the latest Magisk. You will need MagiskSU to get this working.
Sent from my LG Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Cool, I will research that.
---------- Post added at 08:47 AM ---------- Previous post was at 07:48 AM ----------
leolawliet said:
SuperSU is the problem. You can't hide root from SuperSU even with the latest Magisk. You will need MagiskSU to get this working.
Sent from my LG Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I tried to find a way to remove supersu and install magisksu but I didn't find any instructions. I'm afraid to mess with my phone cause I really need it today.
If it's some easy steps please share or point me to the right guide.
Thanks.
Sent from my Nexus 6 using Tapatalk
slekkas said:
Cool, I will research that.
---------- Post added at 08:47 AM ---------- Previous post was at 07:48 AM ----------
I tried to find a way to remove supersu and install magisksu but I didn't find any instructions. I'm afraid to mess with my phone cause I really need it today.
If it's some easy steps please share or point me to the right guide.
Thanks.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Might be a good idea to start with uninstalling Magisk, just to be safe.
Remove SuperSU (there's an option in the SuperSU app, full unroot). It will ask you if you want to restore the backup boot image, do that (or you could do that yourself, just to be safe). You could also flash osm0si's unSU zip in TWRP and then restore your stock boot image.
Flash Magisk zip in TWRP.
Done.
If you really need your device today, don't tinker with it until tomorrow... And always have a backup.
Didgeridoohan said:
Might be a good idea to start with uninstalling Magisk, just to be safe.
Remove SuperSU (there's an option in the SuperSU app, full unroot). It will ask you if you want to restore the backup boot image, do that (or you could do that yourself, just to be safe). You could also flash osm0si's unSU zip in TWRP and then restore your stock boot image.
Flash Magisk zip in TWRP.
Done.
If you really need your device today, don't tinker with it until tomorrow... And always have a backup.
Click to expand...
Click to collapse
It worked mate, Thanks a million
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
The touch buttons don't work for me. Is anyone else having this problem?
Never mind, working fine now.
slekkas said:
It worked mate, Thanks a million
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
The touch buttons don't work for me. Is anyone else having this problem?
Never mind, working fine now.
Click to expand...
Click to collapse
For clarification for anyone who encounters your touchpad issue, were you having trouble with the onscreen buttons, mapping to Sixaxis, or both? And how did you resolve?
Sent from my Nexus 5X using Tapatalk
Info from another thread about using DS4 with the official Remote Play app- kind of. AFAIK, this requires you be on the same WiFi network and within reasonable (Bluetooth) range of the PS4. If that's not correct let me know, I'll edit the post.
Second account method;
-Make a second PSN account for free. Log into the 2nd account on the PS4 itself.
-Open the Remote Play app & go to settings. Hit "Sign In" (if you have the PlayStation app logged in to your main account it should automatically log you into that account. Log out and once again "Sign In" this time using your second account. This time around it'll prompt your for a username and password.
-On the PS4 (while logged into 2nd account) go to "Settings > Remote Play Connection Settings > Add Device". It'll display a code you'll use for the next step
-Click Next / Skip while the Remote Play app is trying to connect to the PS4 and manually register it. It will ask for the code from earlier. Enter it and you should now be streaming the PS4 through the app.
-Press the PS button on the DS4 and it should switch back over to your main account, while keeping the remote play going.
It works, I just tested it. I only tested it one room away from my PS4. I believe this works since your controller is technically connected to the PS4 itself, but the 2nd user started remote play. 1st user takes back control with the DS4, but it doesn't kill the link to remote play. The controller still has to be close enough to the PS4 to be picked up with Bluetooth, it doesn't actually connect it to the phone.
To whom it may concern..
RoyJ said:
Info from another thread about using DS4 with the official Remote Play app- kind of. AFAIK, this requires you be on the same WiFi network and within reasonable (Bluetooth) range of the PS4. If that's not correct let me know, I'll edit the post.
Second account method;
-Make a second PSN account for free. Log into the 2nd account on the PS4 itself.
-Open the Remote Play app & go to settings. Hit "Sign In" (if you have the PlayStation app logged in to your main account it should automatically log you into that account. Log out and once again "Sign In" this time using your second account. This time around it'll prompt your for a username and password.
-On the PS4 (while logged into 2nd account) go to "Settings > Remote Play Connection Settings > Add Device". It'll display a code you'll use for the next step
-Click Next / Skip while the Remote Play app is trying to connect to the PS4 and manually register it. It will ask for the code from earlier. Enter it and you should now be streaming the PS4 through the app.
-Press the PS button on the DS4 and it should switch back over to your main account, while keeping the remote play going.
It works, I just tested it. I only tested it one room away from my PS4. I believe this works since your controller is technically connected to the PS4 itself, but the 2nd user started remote play. 1st user takes back control with the DS4, but it doesn't kill the link to remote play. The controller still has to be close enough to the PS4 to be picked up with Bluetooth, it doesn't actually connect it to the phone.
To whom it may concern..
Click to expand...
Click to collapse
I'll update the OP with a link to this post. Thanks @RoyJ
Sent from my LG Nexus 5X using XDA Labs
Related
New N6 updated to 6.01 and I find an EQ in the stock Google Play Music, but I have not found an app that acts as a system-wide EQ for use on Amazon Music, TuneIn Radio, iHeatRadio, etc. I've had great luck with Equalizer from the Play Store on other devices, but not so much for the N6. It installs fine, but does nothing to the audio. Any assistance appreciated!
454 said:
New N6 updated to 6.01 and I find an EQ in the stock Google Play Music, but I have not found an app that acts as a system-wide EQ for use on Amazon Music, TuneIn Radio, iHeatRadio, etc. I've had great luck with Equalizer from the Play Store on other devices, but not so much for the N6. It installs fine, but does nothing to the audio. Any assistance appreciated!
Click to expand...
Click to collapse
try this(may work for you)
https://play.google.com/store/apps/details?id=music.bassbooster.equalizer&hl=en
Thanks for the suggestion, but installed and...nothing.
I'm using viper mod but music fx (Google eq) kicks in every time. I had to uninstall it to make viper work. Try disabling effects from music fx from settings or try to disable from app settings and try your favorite app for sound effects.
Besides music fx should effect every music app, which I tried on eleven and spotify.
I have a question. I have a refurbished nexus 6 on 6.0.1 that I recueved yesterday. Iv got to return it because the back is comming unglued. Device is unlocked.Question is I tried installing twrp via fastboot commands and it booted into twrp as long as I had it connected to the computer after it finished I tried booting into twrp and it failed but when I rebooted the device back up I got the update superSU notification I tried flashing it and through Google play and it fails. I flashed twrp-2.8.7.1 and superSU v2.60 or what ever the newest one is for android M. I done all this before I called asurion about the other problems I was having. So how do I get rid of the supersu app because it won't let me uninstall it in Google play it' says update or open.
Sent from my HTC6600LVW using Tapatalk
---------- Post added at 08:02 AM ---------- Previous post was at 07:58 AM ----------
If twrp is installed where would it be located in root explorer?
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I have a question. I have a refurbished nexus 6 on 6.0.1 that I recueved yesterday. Iv got to return it because the back is comming unglued. Device is unlocked.Question is I tried installing twrp via fastboot commands and it booted into twrp as long as I had it connected to the computer after it finished I tried booting into twrp and it failed but when I rebooted the device back up I got the update superSU notification I tried flashing it and through Google play and it fails. I flashed twrp-2.8.7.1 and superSU v2.60 or what ever the newest one is for android M. I done all this before I called asurion about the other problems I was having. So how do I get rid of the supersu app because it won't let me uninstall it in Google play it' says update or open.
Sent from my HTC6600LVW using Tapatalk
---------- Post added at 08:02 AM ---------- Previous post was at 07:58 AM ----------
If twrp is installed where would it be located in root explorer?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
Why are you trying to hijack this thread? Make your own. Very rude.
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
This module installs the leaked Pixel Launcher and Wallpaper Picker as system apps, to give full Google Now integration.
Got stuck on bootloop. Perhaps it was because I'm using a different system UI/theme (Xperia X) for my Z2.
DawoodSahi said:
Got stuck on bootloop. Perhaps it was because I'm using a different system UI/theme (Xperia X) for my Z2.
Click to expand...
Click to collapse
I don't think that should matter, though I do recall there being compatibility issues with Magisk and Sony devices in general.
jaimbo said:
I don't think that should matter, though I do recall there being compatibility issues with Magisk and Sony devices in general.
Click to expand...
Click to collapse
Not that I know of, everything that I'm using is working very well. That'll include, Phh supersu, systemless xposed, v4a for now.
took a couple of reflashes in the right order but finally got it all working thanks for this, it's pretty awesome.
Tried this module to check out the launcher, very nice. Works well on HTC m8, nice new flavor to try for a bit. Only thing I don't like is not being able to change the date at top of home screen. Wish they made it customised.
Sent from my HTC One M8 using XDA-Developers mobile app
How can I install this? I tried using the downloads section in Magisk Manager and it says "The zip is not a Magisk module!!" and does nothing. Is there a different way for me to install it within Magisk?
Installation worked for me, no error message saying it's not a magisk zip, though i got the same problem from above that i am stuck on my boot screen, device is a samsung galaxy note edge (completly fresh install, latest stock rom, only installed magisk with phh's superuser)
I can't remove it in Magisk Manager. How to remove it completely or is it only remove the 2 apps in /system/app en priv-app?
Sent from my lightning fast SM-G930F (S7)
Is there a way we can get weather instead of the date on the homescreen? TIA
I have weather... maybe you need to download the newer apk from apk mirror ?
Can anyone confirm if the launcher shortcuts work on MM devices?
I have installd pixel launcher module from magisk installer but its not working its showing as follows and there is no ui how to get that
I have rebooted my device many times. But no use
Just a small heads up @jaimbo. The support link in your module is broken (missing a colon).
Bootloop
I'm stuck in a bootloop as well. Any way to uninstall the pixel launcher from recovery?
stryker.x said:
I'm stuck in a bootloop as well. Any way to uninstall the pixel launcher from recovery?
Click to expand...
Click to collapse
yes - flash "Mount-Magisk.zip" file in recovery (from this thread: Collection-magisk-modules. It will mount magisk image to you under /magisk/ folder. Go there and delete whole issues generated module folder. Reboot. Should start now. But... for me (on my device) avery time I mount Magisk image from recovery, I got google account lost, fc few apps, even once whole system ui got fc, so I cant get into my device. Try, risk nothing.
S7E 935F, mahisk v9, Echoerom Nougat deodexed.
this put my s7edge sm g935f into a bootloop. I have no idea what to do. Please help
---------- Post added at 09:36 AM ---------- Previous post was at 08:50 AM ----------
DawoodSahi said:
Got stuck on bootloop. Perhaps it was because I'm using a different system UI/theme (Xperia X) for my Z2.
Click to expand...
Click to collapse
fixed using simplycity's method. i would delete this but i dont know how so for now its just an edit
trinadhchinna7 said:
I have installd pixel launcher module from magisk installer but its not working its showing as follows and there is no ui how to get that
I have rebooted my device many times. But no use
Click to expand...
Click to collapse
which font is that .could you give link pls
Note you can find the zip at https://github.com/Magisk-Modules-Repo/PixelLauncher/archive/master.zip (for "magisk approved" modules at least)
Sort of couldn't find this anywhere for some reason, had to look at where the magisk-manager gets pre-zipped stuff from just replace the repo name for other modules also.
useful when magisk doesnt want to flash+download on its own
pokepokepoke said:
which font is that .could you give link pls
Click to expand...
Click to collapse
Its fords folly if u have blackmart u can get it there
If u r using samsung device and willing to purchase the app then search it in samsung apps
I haven't been able to find a thread on this. So here goes… I'm not able to get the Blackberry Work app that my firm uses to load without detecting root on Magisk v14.0,
What i have tried so far:
- Hide the app using Magisk hide
- Hide Magisk Manager
- Restarting the phone after applying settings above
- Switching between Core/Non-core modes
I can't imagine i am the only one experiencing this issue. Would be real greatly if someone could advise if Magisk can be configured to circumvante BB Work's detection. I really need this app for work (non pun intended)
Which version of BlackBerry Work are you using? Is it newer than 2.7.1.822? Is it asking you for an unlock code?
There was a problem with Huawei devices in some versions. They already fixed it, but for unknown reason 2.7.1.822 is still the latest that works on my Zenfone 2.
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka
I'm using the latest version. I can get pass all the password/codes, the problem starts after that. The app detects the root after login and i'm bounched back to the logon screen again. If i try to login now, it'll block me and i'm asked to contact my system admin.
I'll try to use the version you mentioned below when i get to the office tomorrow and see how it goes.
Still looking for a way to run Blackberry work app on rooted android!
Has anyone found a way??
deepchakra said:
Still looking for a way to run Blackberry work app on rooted android!
Has anyone found a way??
Click to expand...
Click to collapse
I've just checked this and the current version of BB Work from Google Play doesn't work with Magisk.
The last version that works fine is 2.7.1.822
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka
If you run a ROM unrooted, will Blackberry Work still detect the unlocked bootloader and/or custom recovery?
Can i write a Magisk module to spoof the device name that blackberry work reads? My company has a policy that only allows iPhones on blackberry work.
Anyone have a solution? I'm am running stock Android pie rooted and can't get bb work to work.
stu5797 said:
Anyone have a solution? I'm am running stock Android pie rooted and can't get bb work to work.
Click to expand...
Click to collapse
Im also running Pie. I have BB Work and UEM Client working fine on my setup with Magisk 17 and manager 5.9.6 or whatever that recent one is. I think the key is you need to use Elemental x kernel as well. So assuming you already have TWRP installed then you would:
1. Boot to TWRP
2. Install Elemental X Kernal
3. Install Magisk 17
4. Install Verified Boot signer v8
5. reboot and if you havent already install Magisk Manager
6. Make sure magisk manager is "hidden" in the settings, also use Magisk Hide to hide all the BB apps as well as one called something like "android.auto_generated.rro_..." I also run it in Core Only mode.
7. Reboot, delete any BB apps you might have already installed and then redownload and resetup. Just make sure everything is Hidden in Magisk Hide before launching it the first time. I can assure you that BB apps can be gotten to work with Magisk and Anrdoid 9.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
napes22 said:
If you run a ROM unrooted, will Blackberry Work still detect the unlocked bootloader and/or custom recovery?
Click to expand...
Click to collapse
No it wont.
Thanks so much. I noticed if you install blackberry work and it detects anything, the code deactivates so you can not use the app. It must be a prefect install or it won't work
stu5797 said:
Thanks so much. I noticed if you install blackberry work and it detects anything the code deactivates so you can use the app. It must be a prefect install or it won't work
Click to expand...
Click to collapse
Make sure you hide Magisk Manager and that you use Magisk hide to hide Magisk from both Blackberry Work and Blackberry Work profile.
If you take those 2 steps it'll work.
napes22 said:
Make sure you hide Magisk Manager and that you use Magisk hide to hide Magisk from both Blackberry Work and Blackberry Work profile.
If you take those 2 steps it'll work.
Click to expand...
Click to collapse
This works perfectly. Excellent. :good:
What is "Blackberry Work profile"? I don't see that in the list of apps...
Is anyone still using latest app with magisk?
someuser08 said:
Is anyone still using latest app with magisk?
Click to expand...
Click to collapse
2.16.0.1156 BB Work (disabled auto update) on LineageOS 15.1 (Oreo 8.1.0). Magisk 18.1 with Manager 7.0.0. It's still working albeit the phone must be rebooted from time to time because Magisk disappears. This has been an issue for me on the past few versions of Magisk installed systemless.
I can't seem to get it to work for the last half of year (it was OK before). Its almost like work app detecting something else rather than root...
someuser08 said:
I can't seem to get it to work for the last half of year (it was OK before). Its almost like work app detecting something else rather than root...
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/blackberry-app-magisk-t3742178/page2
I removed magisk completely and it still doesn't work for me - I now think its detection of custom ROMs or unlocked bootloaders that kick in...
someuser08 said:
I removed magisk completely and it still doesn't work for me - I now think its detection of custom ROMs or unlocked bootloaders that kick in...
Click to expand...
Click to collapse
I have auto update turned off on my BB apps now. Currently running 2.16.0.1156 still. With Magisk 19.0 and Manager 7.1.1, all BB apps are working on LineageOS 15.1 (Oreo 8.1). If you use the "Basic" configuration guide for Magisk on these versions, you should be in business.
Settings like debugging and dev options could be some off the culprits preventing proper detection circumvention.
I found an old phone, formatted internal storage and got LOS 15.1 on it. BB is the only app installed(no magisk). After retrieving policies from the server it self wipes due incompatible security policy. I can only assume it detects custom ROM (tried the same with AEX). Is there a module in magisk that makes your phone look like official factory state?
I've seen a few threads on the Blackberry Work app, but they all seemed have become idle at the end of 2017. Has anyone been able to run new versions of Blacberry Work with the new versions of Magisk?
I'm running an unrooted custom ROM, but the way new versions of the ROM are compiled (using Android Clang) are triggering the checker. Was hoping I could flash Magisk to hide root and custom rom detection from the app.
It depends on what the app is detecting, of course, but take a look under "Hiding root from apps" in the troubleshooting guide. The rest of the post might have some useful tips as well.
I ended up installing Magisk and hiding from the app. It works really well, so we can go ahead and close this thread. Thanks for the follow up.
napes22 said:
I ended up installing Magisk and hiding from the app. It works really well, so we can go ahead and close this thread. Thanks for the follow up.
Click to expand...
Click to collapse
Is BB Work still working for you with Magisk? Our company moved to BB Good (now Work) years ago. I stopped rooting back then since it was too much of a hassle to figure out and I need to have my work email. If this works, the only thing holding me back would be getting official updates from OnePlus. I have the 5T.
jvnat said:
Is BB Work still working for you with Magisk? Our company moved to BB Good (now Work) years ago. I stopped rooting back then since it was too much of a hassle to figure out and I need to have my work email. If this works, the only thing holding me back would be getting official updates from OnePlus. I have the 5T.
Click to expand...
Click to collapse
Yes I can confirm that magisk root does work with BB Work. You have to use the "hide" function in the Magisk Manager and select BB work.
FYI
I am using a stock rom with root.
Tip: don't use xposed framework if you want a working BB work app.
I flashed Magisk in my redmi note 3 kate and installed the magisk manager apk app, everything is working fine, but my question is: Should I install phhSuperUse, rather than this variant has SU because it was built to be installed with magisk ?
Excuse me, I'm not very familiar with the subject and I've been reading about this and I'm a little confused
---------- Post added at 10:22 PM ---------- Previous post was at 10:20 PM ----------
What is the difference when using the magisk modules?
always use xposed framework plus S.U. But since I can no longer download some apps in play store I have resorted to install magisk on my device.
Hello,
Is it still working ?
It work with Good for Enterprise , but i am not able to install UEM Client and BB Work ?
UEM Client seems fine and show device as unrooted but then setting up Blackberrry Dynamics failed due to that , any idea ?
Regards,
Darkwa said:
Yes I can confirm that magisk root does work with BB Work. You have to use the "hide" function in the Magisk Manager and select BB work.
FYI
I am using a stock rom with root.
Tip: don't use xposed framework if you want a working BB work app.
Click to expand...
Click to collapse
I have a message bb work data wiped. And installation fails at the last point. How can I solve it?
Greetings
Wysłane z mojego MI 6 przy użyciu Tapatalka
As of yesterday, blackberry is detecting my root for some reason. Nothing has changed so my guess is that it has something to do with my company's policy changing? At this point I'm very confused
napes22 said:
As of yesterday, blackberry is detecting my root for some reason. Nothing has changed so my guess is that it has something to do with my company's policy changing? At this point I'm very confused
Click to expand...
Click to collapse
I am in the same boat. I can no longer get Magisk 18.0 and BB Work (or any of the BB enterprise apps) to function. I immediately get the "jailbroken" message. I have no idea what changed. :crying:
I am going to try 18.1 and will report if things change.
DaCHeF36 said:
I am in the same boat. I can no longer get Magisk 18.0 and BB Work (or any of the BB enterprise apps) to function. I immediately get the "jailbroken" message. I have no idea what changed. :crying:
I am going to try 18.1 and will report if things change.
Click to expand...
Click to collapse
Magisk 18.1, Manager 7.0, and following this guide is what works:
https://www.didgeridoohan.com/magisk/MagiskHide
Make sure the "Basics" are taken care of, manually.
Hide Magisk Manager package under settings, MagiskHide "Work" only now (no "Work Profile" choice present in the new version). I removed all root-requiring apps. The combo here worked. I may go one by one to see if any of those apps made a difference. Regardless, it works following those instructions. Good luck. :good:
DaCHeF36 said:
Magisk 18.1, Manager 7.0, and following this guide is what works:
https://www.didgeridoohan.com/magisk/MagiskHide
Make sure the "Basics" are taken care of, manually.
Hide Magisk Manager package under settings, MagiskHide "Work" only now (no "Work Profile" choice present in the new version). I removed all root-requiring apps. The combo here worked. I may go one by one to see if any of those apps made a difference. Regardless, it works following those instructions. Good luck. :good:
Click to expand...
Click to collapse
Perfection, thanks so much. Running DU on taimen with Magisk 18.1 substratum TitaniumBackup Franco app. All good!
Sent from my Pixel 2 XL using Tapatalk
Blackberry Appstore
bigknowz said:
Perfection, thanks so much. Running DU on taimen with Magisk 18.1 substratum TitaniumBackup Franco app. All good!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
@DaCHeF36 Spoke too soon, not able to load BB Access or Appstore, thoughts?
bigknowz said:
@DaCHeF36 Spoke too soon, not able to load BB Access or Appstore, thoughts?
Click to expand...
Click to collapse
I'm not sure about the Appstore, but I am stuck at an "Authenticating" screen for Access. If I make any progress I'll let you know.
Canary
DaCHeF36 said:
I'm not sure about the Appstore, but I am stuck at an "Authenticating" screen for Access. If I make any progress I'll let you know.
Click to expand...
Click to collapse
Everything works on Canary, running 18100.
bigknowz said:
Everything works on Canary, running 18100.
Click to expand...
Click to collapse
Magisk 19.0 and the new 7.1.1 Manager combination seem to work with all BB apps. Maybe it's just me, but the Work Profile option returned in Hide.
Are there any dependencies for BB apps we need to also hide from Magisk?
DaCHeF36 said:
Magisk 19.0 and the new 7.1.1 Manager combination seem to work with all BB apps. Maybe it's just me, but the Work Profile option returned in Hide.
Click to expand...
Click to collapse
I only need to use the BB work app, are you hiding any other app except BB Work ? Also,a) are you hiding the Magisk Manager, b)using Magisk Hide to hide BB Work or c)doing both?
TarunN5 said:
I only need to use the BB work app, are you hiding any other app except BB Work ? Also,a) are you hiding the Magisk Manager, b)using Magisk Hide to hide BB Work or c)doing both?
Click to expand...
Click to collapse
Work and Work profile setup are hidden. Work profile setup is definitely there again. I use Access, Tasks, and Connect too. I have them all hidden even though that may be overkill. I hide Magisk Manager using the built in package option too. I also followed the guide to ensure that all settings like debug, etc. were off. Gold. I excluded the BB apps from auto-updating. I don't plan to upgrade them unless the back-end requires it at some point.
DaCHeF36 said:
Work and Work profile setup are hidden. Work profile setup is definitely there again. I use Access, Tasks, and Connect too. I have them all hidden even though that may be overkill. I hide Magisk Manager using the built in package option too. I also followed the guide to ensure that all settings like debug, etc. were off. Gold. I excluded the BB apps from auto-updating. I don't plan to upgrade them unless the back-end requires it at some point.
Click to expand...
Click to collapse
Thanks, can you please tell me what exactly do you mean by "work profile" and "work profile setup". The app I see is i dont see a work profile app in the play store either. Can you also please send a screenshot of the BB apps that you have hidden in Magisk? This is the first time I'm using BB on my phone so pardon my noobness