Related
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!
I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.
This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk
Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app
Hello ! Is there a way to install xposed framework on A7 2017 nougat ?
Using the Magisk module with the Material Design XPSD worked perfectly on my A7(2017)
dudedude420 said:
Hello ! Is there a way to install xposed framework on A7 2017 nougat ?
Click to expand...
Click to collapse
Hello! I've never posted on XDA before but since I spent 6 hours yesterday trying to figure out a proper way to do just that so I might as well help.
This worked perfectly for my A720F/DS but it should also work with any A series nougat device. Notice that the MOST important part for this to work in other devices is choosing the correct xposed SDK according to your android system and CPU. Magisk is universal, no need to worry about download one specific for your device.
I'll start with a short summary in case you know a lot about the topic and then proceed to a step-by-step process.
Only the "systemless" AKA Magisk way works flawlessly, it's pretty simple when using the correct files. If you already have Magisk properly installed all you have to do is download the latest "Material Design Xposed Installer" and have active the 24 SDK module from the Magisk Manager app.
STEP 1
ROOT WITH MAGISK AND USE VERITY PATCH TO AVOID KNOX PROBLEMS
1. Put magisk v14.0 and dm-verity patch onto the sdcard in the phone.
Download the latest magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Verity Patch from here: https://forum.xda-developers.com/samsung-a-series-2017/help/how-to-install-magisk-v12-0-root-enable-t3611527 You might need this link later to use S Health...
2. Flash TWRP using Odin - You cand download both here https://forum.xda-developers.com/samsung-a-series-2017/development/xcc-t3591448
Important Note for Installing TWRP on A7 2017: Disable auto-reboot in Odin so that after flashing TWRP it says PASSED but instead of rebooting and Knox un-doing what you just did, you will now attempt to go to download mode again (Vol Down + Home + Power Button) but as soon as the screen goes black (meaning the phone is off) you will instead go to Recovery mode, simply pressing the Vol Up + Home + Power Button.
3. In recovery mode, allow modifications. and under wipe there should be a button to format data. You will need to do this to flash Magisk and dm verity, if not your cellphone will be stuck on a bootloop.
4. Flash Magisk, when the process is done simply go back and flash dm verity. (this order is important)
5. Boot the phone normally, it shouldn't take long but don't worry if it takes up to 5 minutes. (In my case, when only the SAMSUNG logo showed up it would always keep going to a normal boot, but when it said A7 and the other info it would be stuck on a boot loop).
6. Open Magisk Manager app and check if you can download and install modules (it needs storage permission first). It you manage to install modules properly then skip to the next step. If it says Process Error and you can't seem to install modules then make sure you give the app the proper permissions and then on the home page of the app select Install Directly (Recommended), I guess this installs Magisk again or somethins.. This seemed to finally make it work for me. A reboot is necessary.
STEP 2
INSTALL SYSTEMLESS XPOSED FRAMEWORK SDK24 MODULE FROM MAGISK ALONG WITH MATERIAL DESIGN XPOSED INSTALLER APK
1. Get the latest "Material Design Xposed Installer" from here, it shouldn't matter if you immediately install it or install it later (like I did)https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758 (I'm 90% sure thats the one I used, if it doesn't work, try the one by Sr.CyanDroid)
2. In the Magisk Manager app, download and install the module XPOSED FRAMEWORK SDK24... It will tell you it installed correctly and reboot, you can double check by going into your Modules section after rebooting and seeing if it show up there... its a weird feeling but if it does show up that already means you successfully installed the xposed framework through Magisk.
3. Install (or just open if you previously installed it) the "Material Design Xposed Installer", it will either tell you it failed to detect Xposed or it will say its all perfect and you will be able to use Xposed normally. In case it says it failed, like it did to me, simply update the xposed app within itself. In my case, there was a notice at the bottom suggesting me to install the newest "Material Design Xposed Installer" and the problem was fixed immediately as I did it.
DONE
Keep in mind that by using this Magisk Method you are avoiding modifying the system partition, meaning its a lot less likely for you to brick your phone while trying different xposed files (apks are the only xposed files you need anyway). I hope this helps you and anyone else with this problem, keep in mind its 4am, and I'm really sleep so somethings MIGHT not be perfect. I also have a busy week coming up so I might not be able to respond any messages any time soon. Cheers!
Was looking exactly for this. Gonna try this in a day. Gonna post on the progress once done. Thanks!
If i did this, am i going to lose my warranty?
Sent from my [device_name] using XDA-Developers Legacy app
mido_many2000 said:
If i did this, am i going to lose my warranty?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes.
Will i lose my data ?
Hi all,
I have installed Magisk 16.0 based on Maik93's post, and Xposed Framework SDK27 90.2-beta3 (Systemless), through Magisk modules.
When I enable the Xposed module, the phone first shows endless boot animation, and when restarting it again, it boots, but the Xposed app seems not installed (not listed in Settings->Apps and its icon is not present in chooser), although, in Magisk, it is visible in the Modules and it's checkbox is checked.
Did anybody successfully installed Xposed with A2 Lite? What can be the problem?
Thanks a lot,
Circum
Did you install the apk of xposed?
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
https://forum.xda-developers.com/attachment.php?attachmentid=4393082&d=1516301692
Here is the link from xda
No, sorry, I was not aware that it is a separate thing.
Now I have installed, but it says that no Xposed Framework is installed. If I try to install a framework from inside the installer (90-beta3), it -- obviously -- reports an error that /system/framework/XposedBridge.jar already exist...
Because of this, I cannot enable any module from Xposed Installer.
Any tips what do I do wrong?
I want to use Xposed too but we will have to wait for TWRP I guess.
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
mik.y said:
I want to use Xposed too but we will have to wait for TWRP I guess.
Click to expand...
Click to collapse
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
HoangP05 said:
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
Click to expand...
Click to collapse
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
mik.y said:
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
Click to expand...
Click to collapse
Not all are working apparently, but if it is bootloop, you so try to let it boot again, press power and volume down as the same time while it bootloop, the second boot always work for me
There is TWRP for Mi A2 Lite.
Search on google.
NOTICE: For now there isn't official TWRP. There'w unofficiak fork which can you install using fastboot. :good:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
HoangP05 said:
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
Click to expand...
Click to collapse
Xposed's Gravity box module works on Mi A2 lite?
Yes, GravityBox is working, although as I mentioned, there are issues with boot - I have to reboot several times until it succeeds...
performace drops significantly when i install the xposed module for magisk. i hope they fix it.
So far everything works fine on my end, I'm not noticing any performance drops in my day to day use. Then again I haven't used it much without Magisk + exposed but from what i'm seeing it's working well, no noticeable lag or stuttering.
I have gravity box, Amplify and Greenify modules running.
circum said:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
Click to expand...
Click to collapse
Magisk alone didnt give me boot problems. What rooting guide did you follow?
fake__knv said:
Magisk alone didnt give me boot problems. What rooting guide did you follow?
Click to expand...
Click to collapse
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
circum said:
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
Click to expand...
Click to collapse
I can assure you @BubuXP's guide is good. Used his rooting guide, followed the steps for updates and its good to go. I rooted my phone when Im on August update. Now Im in September update
Developer Preview is up if anybody wants to try it
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Holy Moly.
Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference
DoobyDroid said:
Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference
Click to expand...
Click to collapse
Seems like for now, most UI and user facing changes in general are hidden behind flags, this one is meant for the devs, so it's to be expected. The beta, on the other end, will be aimed at users, and then we will see what changes
I upgraded last night. Had to reboot twice after restart. Then everything was stable. First time it rebooted after install, nothing seemed to want to work and kept FCing. Second reboot, everything is fine now. Sometimes, Nova needs to be indicated when I press the home button that it's default, otherwise, everything is working fine.
Is it me or does the Android version still say 11 but the build is "S"?
I downloaded the 12 DP1... and it just isn't ready yet (understandably so) for the daily driver use I need.f
Rooting it requires disable verity and verification. You'll need magisk 23 or canary to patch boot.img as well. Not disabling verity/verification, it will only boot back into fastboot and list the reason as something like, "unable to load boot image".
Once rooted, I moved on to installing edxposed --- using riru, riru edxposed, and edxposed manager. Everything installs without problems. Final reboot, and reboots as normal. But then about 90 seconds later, you'll start getting FC after FC after FC. All apps too, and background apps, and systemui, etc.
Removing the riru components and edxposed manager, doesn't correct this problem.
Did fresh format and reinstall of the DP1... rooted again... and then tried Viper4Android. I use a very simple version. You just flash it, and its done (no manual driver install either). Rather than the 3 reboot, AML, driver install, etc.
V4A installs with good logs. Reboots without a hitch. But I noticed the v4a icon in the status bar is missing. I open it up manually, and start getting freezes and fc's. Within 5 minutes, I get kernel panic reboots -- and non-bootloop freezes on the working G screen.
Reboot manually with long press power, get it loaded back up and immediately remove V4A. Reboot and now I'm back to stock.
Get FC's every hour or two. Random reboots too. Battery life is struggling.
I decided to wait until a better version drops, perhaps the beta or at least a DP2.5 or 3.0. As of right now, having Android S is mostly just a status thing -- to show people how cool we are to have access to it as such an early stage. But unless you are dedicated to helping improve the ROM through daily use and reporting... I highly recommend that you stick with Android R.
Just flashed the 1st public android 12 beta bramble-ota-spb1.210331.013-3c294b13.zip with adb sideload. Listed as android S atm, surprised 5G was enabled as this wasn`t the case with android 11 in the Netherlands. All apps working fine so far and still finding out the new stuff.
Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.
ekowwillis said:
Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.
Click to expand...
Click to collapse
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something
galza said:
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something
Click to expand...
Click to collapse
Clean wipe and follow the OP instructions in this Pixel 5 thread. Make sure you use the images for 4a5g where needed
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
Hello Guys,
We know, Some App in Our Devices doesn't allow us to Take ScreenShot.
and We See an error saying "Couldn't Take Screenshot" OR Similar.
I'm Creating This Post Because I haven't Found Any. (I'll try to make it Up to date, Specially for whichever ROM I'll be Using in the Future).
So I Made a Magisk Module using The Smali Patcher
It will allow the User to Take ScreenShot in Protected Apps.
Just Flash it From MAgisk and Enjoy
Currently Only Available for Xiaomi EU Beta 21.5.12 ROM
Download Link:- Click Here
If you Want to Make For Your Device/Rom, You Can Use Smali Patcher,
Follow The Instructions from The Post. Click Here.
Please Comment Down for Issues OR Suggestions.
You can Contact Me on Telegram @itspdp
Click on That Thank Button, If It was Helpful.
Thanks, interesting
I remember I encountered an app or two not allowing screenshots - but I forgot now, can you please tell which apps to test with
Btw, I have Mi 9T (not Pro) and Xiaomi.eu 21.5.20 (davinci was 'delayed' a week later than your raphael), but I think the module should work as well
Btw, as I can see, changes should be systemless, hence if anything goes wrong just disabling the module (and reatarting the phone) should be enough to go back to 'normal'
Y
zgfg said:
Thanks, interesting
I remember I encountered an app or two not allowing screenshots - but I forgot now, can you please tell which apps to test with
Btw, I have Mi 9T (not Pro) and Xiaomi.eu 21.5.20 (davinci was 'delayed' a week later than your raphael), but I think the module should work as well
Btw, as I can see, changes should be systemless, hence if anything goes wrong just disabling the module (and reatarting the phone) should be enough to go back to 'normal'
Click to expand...
Click to collapse
Yes Everything will be Systemless, we can try, if anything goes wrong we can remove that module (Even from Recovery)
Use The Smali Patcher to Make Modulw for Your Device.
(Link and Tutorial already inside the post),
It's easy and will take about 5-10 minutes only.
P.s. :- This Module is Device and Rom (Including Version) Specific, You Have Make For Your Own Rom/Device amd Update it with Each OTA Update of Your Rom.
After some troubles with the PC, I was able to run Smali Patcher to create a module for my Mi 9T, Xiaomi eu 21.5.20 - do you know please a (system) apk in Xiaomi.eu that does not allow screenshots, that I can test with and without the module, to check does it work
zgfg said:
After some troubles with the PC, I was able to run Smali Patcher to create a module for my Mi 9T, Xiaomi eu 21.5.20 - do you know please a (system) apk in Xiaomi.eu that does not allow screenshots, that I can test with and without the module, to check does it work
Click to expand...
Click to collapse
Try Chrome incognito mode
ca_guri01 said:
Try Chrome incognito mode
Click to expand...
Click to collapse
Thanks, I tried Chrome Incognito window with the my Smali patch module disabled and it complained that screenshots are not allowed
I enabled the module, rebooted and tried again, and it successfully made the screenshot
Thanks, it works (Mi 9T, Xiaomi.eu 21.5.20, Magisk v23)
I don't know what's wrong now - I tried to repeat everything with Xiaoni eu 21.6.9:
- Connected again my phone to (the same PC), ran SnaliPatcher (as admin) again, successfully created a module for Secure Screenshot
- Module installls from Magisk app with no errors (everyrthing the same as when did first time for 21.5.20)
But when I reboot, it fails and after a long time staying on MIUI splash screen, it eventually reboots to TWRP.
I have to remove the module to be able to boot
Tried two times (rebuilding the module by SmaliPatcher, installing the new module), no success
zgfg said:
I don't know what's wrong now - I tried to repeat everything with Xiaoni eu 21.6.9:
- Connected again my phone to (the same PC), ran SnaliPatcher (as admin) again, successfully created a module for Secure Screenshot
- Module installls from Magisk app with no errors (everyrthing the same as when did first time for 21.5.20)
But when I reboot, it fails and after a long time staying on MIUI splash screen, it eventually reboots to TWRP.
I have to remove the module to be able to boot
Tried two times (rebuilding the module by SmaliPatcher, installing the new module), no success
Click to expand...
Click to collapse
Managed to make the module again with Xiaomi.eu 21.6.16:
- I used SmaliPatcher to create the module before (!!!) I installed Magisk.
That is, I installed Xiaomi.eu 21.6.16 and used SmaliPatcher to create the module for Secure Screenshot, only then I installed Magisk and finally installed my SmaliPatcher module - it boots properly to Magisk and Secure Printing works
I think this is the same way I also successfully used SmaliPatcher with Xiaomi.eu 21.5.20
However, when I was on Xiaomi.eu 21.6.9 and when I reported a bootloop, I did it by slightly different order:
- I upgraded to 21.6.9 and immediately installed Magisk, then I used SmaliPatcher to create the module, installed the module and rebooted, but instead of to system it eventually booted to Recovery (TWRP)
This is actually what I was looking for. Btw some apps don't allow us to copy / paste, could you help me with this problem?
verydp1 said:
This is actually what I was looking for. Btw some apps don't allow us to copy / paste, could you help me with this problem?
Click to expand...
Click to collapse
Settings, Apps, find your app, Permissions and enable Access items in the clipboard
this give me a bootloop, anyone know other apps that can do Secured ScreenShot
remorze said:
this give me a bootloop, anyone know other apps that can do Secured ScreenShot
Click to expand...
Click to collapse
Magisk module as attached to OP post will work for you only if you have Mi 9T Pro/Redmi K20 Pro with Xiaomi.eu 21.5.20 (exactly that build)
Otherwise you have to install SmaliPatcher to PC, connect to your phone and follow instructions for the patcher to make yourself the Magisk module for your phone
I don't have Pro but 'plain' Mi 9T, and I'm on newer Xiaomi.eu builds, hence I had to do myself Magisk modules three times (Xiaomi.eu weekly releases).
First time it worked fine for me, next time I also had the bootloop when I made and installed the module (AFAIK, I was following the same patching procedure, with the same phone and PC, hence I don't understand why that time I had a problem). Third time again everything was ok (I got the module for Magisk that does not produce bootloop and it 'unlocks' screenshoting from the apps otherwise not allowing)