Everything is messed up the wifi togle isn't turning on or off the wifi, apps freezing, syetem instability. All of these started after i rooted my phone and installed some root apps like luckypatcher, autovoice, tasker. I also installed custom blu_spark kernel and blu_spark twrp recovery and dolby atmos sound mod. I once also installed moded google play store.
Now i have countless system problems and planning on starting every thing from scratch, fresh firmware install and root. So after i root the phone what are some root apps or other things that i should stay away from?
I hear some people saying you should stay away from luckypatcher and moded apps. Is that true?
Please give me youe insight towards dangerous root habbits.
If you're using Magisk to root, then you should be okay. Just install one thing at a time and see how it goes.
Sound mods can and do cause system instability. Test those out one at a time before moving on to your next mod. Take is slow.
Lucky Patcher is potentially very dangerous to the Android OS and unless you know what you're doing I would stay away from it. It's also a banned app on this forum so any discussion about using it should be taken elsewhere.
I rooted my phone after clean flashing the old 8.1. just magisk manager and till now I had no problem. My only use case for root is control over my apps with greenify and using adblock.
Don't use Lucky Patcher. Also try dirty flashing your room and then root again.
Related
So, i've used Snapchat on both
Stock (5.1.1 - Oi1 Rom) and Custom Rom (Renegade)
I can't seem to get it to work on the custom rom, i've always had to use the stock rom and it would work just fine, but on the other it would say "temporarily logged out" or something different, but when i boot back to stock, its fine and doesn't hesitate to say that.
Am i missing something here?? i've already tried resetting my password 5 times to be sure.
Snapchat 9.1.17.1.0 -- Xposed Snapprefs 1.6.2
Snapchat and Root
I don't use Snapchat, but this might explain your issue:
http://www.xda-developers.com/snapchat-is-at-it-again-and-blocks-root-users-but-for-how-long/
Snapchat detects Root and stops working, XDA builds a work-around into Xposed, Snapchat puts out a new patch and repeat.
Found something new: Try updating to Snapprefs 1.6.4. And you will find more help here: http://forum.xda-developers.com/xposed/modules/app-snapprefs-ultimate-snapchat-utility-t2947254
Thank you!
I've actually ended up researching and figuring it outmyself my way or work around.
Snapchat checks or scans to see if "Xposed" which leads me to not log in.
So in order to use Snapchat with Snapprefs or 3rd party, you would need to either
Install stock and root it, then log into snapchat with the latest version and then go to recovery to install xposed.
or
Install stock and root then boot to recovery to install the custom rom and do no install xposed framework.
Once done with booting up and setting up, install snapchat latest version, log into it and then install xposed.
once thats done download 'xinstaller' and check to enable downgrading and updating and then install 'snapprefs' for all the
juicyness of customizations.
Profit!
My configuration.
Snapchat -
9.17.1.0
Xposed -
75 wanam 20151008 - seems to work best for me on both roms instead of v79.
Snapprefs -
1.6.2
koop1955 said:
I don't use Snapchat, but this might explain your issue:
http://www.xda-developers.com/snapchat-is-at-it-again-and-blocks-root-users-but-for-how-long/
Snapchat detects Root and stops working, XDA builds a work-around into Xposed, Snapchat puts out a new patch and repeat.
Found something new: Try updating to Snapprefs 1.6.4. And you will find more help here: http://forum.xda-developers.com/xposed/modules/app-snapprefs-ultimate-snapchat-utility-t2947254
Click to expand...
Click to collapse
I found a work around for it my phone died and I signed into my sc from another device used it and logged off when I tried signing in on my phone I got temp login failure notice this is what I did to get back on:
On a second device, download latest version and sign into Snapchat
Once done, root second device and download titanium backup
Make a back up of Snapchat from second device and send the .tibkp back up or whatever to the first device
On first device download latest version of snapchat and titanium back up and restore the data only from the file you sent to the first device from the second device
Once done use sc like normal
Works fine unless you sign out from Snapchat on the second device so what I did is I froze Snapchat on the second device and erased the back up.
Why does Snapchat do this? Does anyone have any idea why?
MafiaIlluminati said:
Why does Snapchat do this? Does anyone have any idea why?
Click to expand...
Click to collapse
They make a silly app with an unenforceable premise, the app sucks and they block third-party alternatives, their security is awful, their background data drain is known to go nuts, and now they are blocking root users so they can better charge you for replays??
But still they can't tame the root..
p.s. the CEO is an Apple fanboy..
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
Suddenly I get a warning telling me to uninstall king root 4.9.6. I've been running same fulmics 6 for months and I just discovered the warning sign today.
What is this? Is there any potential danger to keeping king root? If I uninstall king root I will loose root privileges, yes?
joppy said:
Suddenly I get a warning telling me to uninstall king root 4.9.6. I've been running same fulmics 6 for months and I just discovered the warning sign today.
What is this? Is there any potential danger to keeping king root? If I uninstall king root I will loose root privileges, yes?
Click to expand...
Click to collapse
Fulmics has SuperSu installed as System application,there was no need to install KingRoot..
Also if you have two Root apps (same like SuperSu),then your phone isn't going to have a good time..
So delete KingRoot and stay with SuperSu.
Greetings.
Thx. I used king root to first get root access so I could install fulmics. Iirc I found the king root from a post here on the forum, so I assumed it was safe.
I disabled king root.btw it is fulmics 6.1 I got. It seems all things good now. I feel a little paranoid, as I discovered king root is from China ?
I wonder if I should do complete install from scratch or am I safe as long as king root is not longer active?
joppy said:
Thx. I used king root to first get root access so I could install fulmics. Iirc I found the king root from a post here on the forum, so I assumed it was safe.
I disabled king root.btw it is fulmics 6.1 I got. It seems all things good now. I feel a little paranoid, as I discovered king root is from China ?
I wonder if I should do complete install from scratch or am I safe as long as king root is not longer active?
Click to expand...
Click to collapse
The best choice is to uninstall it.Because it has setted it's self as a system application.
But also i think it has an option (in-app) "Uninstall".
In addition if Kingroot is unable to uninstall by using the inapp option then try installing an app from Play store called " System app remover" and delete it from there.
If nothing works then doing a clean re-installation of the ROM would be a great option.
A Tip:Never install an other Root application while you have SuperSU.
Let's take Kingroot for an example, when you have SuperSU and install Kingroot then automatically Kingroot detects that you have an other root application and it set's it's self as system app.
System app remover did the trick. Removed the King Root app. Result is o/c that adaway is no longer working. So I get to play around with SuperSU now. As I am new to SuperSU I am not sure how to get the correct settings. Should I make SuperSU a system app? Or set permanent full root?
Btw, I never had any problems running King Root. It was even a very nice way to charge the phone because King Root made charging go faster.
I've been thinking about the warning sign I got, and could it possible be a generic warning because King Root had root access? Meaning I would get the same warning with other apps with root access?
It seems strange that King Root that is mentioned som many times here on XDA should be crapware. Surely some smart people would have noticed and made posts about it? I am thinking maybe I panic'd and removed King Root prematurely?
Darn it. SuperSU won't run or allow me to set root access to apps. So no TWRP does not work, adaway does not work, root checker confirms I don't have root anymore and to make things worse, SuperSU says I need to upgrade, so I downloaded the latest version as a zip file to install from TWRP but guess what, no more root access. I will try to boot manually into TWRP and install SuperSU. Hopefully that will work.
And reading SuperSU thread it clearly says I must have ROOT prioer to install SuperSU.
Is there are fulmics setting somewhere I have overlooked? Can I set root from within fulmics tweaks?
Well I didn't get the SuperSU working, then I discovered that there was a newer version of KingRoot, v5.0. So for the ease of it I just installed KingRoot v5.0. As of right now, I don't have any warning signs saying Kingroot is bad news.
So unless it is a known fact that kingroot is infected by crap/malware/spyware/whatever I think I just stick to that one for now. I am used to it, I know how to work it and google didn't find any indications kingroot has been compromised . I saw a few posts about earlier version sending IMEI to china, but it seems that was v3xx. v4x and5x seems to be ok.
If this is stupid behavior and I should remove king root let me know and pls add some links or something to back it. I would hate to give a compromised app gateway into my phone but at the same time I think I was in panic mode earlier today and that my reaction was uncalled for.
joppy said:
Well I didn't get the SuperSU working, then I discovered that there was a newer version of KingRoot, v5.0. So for the ease of it I just installed KingRoot v5.0. As of right now, I don't have any warning signs saying Kingroot is bad news.
So unless it is a known fact that kingroot is infected by crap/malware/spyware/whatever I think I just stick to that one for now. I am used to it, I know how to work it and google didn't find any indications kingroot has been compromised . I saw a few posts about earlier version sending IMEI to china, but it seems that was v3xx. v4x and5x seems to be ok.
If this is stupid behavior and I should remove king root let me know and pls add some links or something to back it. I would hate to give a compromised app gateway into my phone but at the same time I think I was in panic mode earlier today and that my reaction was uncalled for.
Click to expand...
Click to collapse
Then if you are used to Kingroot just uninstall SuperSu(Install the system app remover from Play store ((the first app that appears)).
Because as i mentioned before if you have two Root applications your phone isn't going to have a good time.
(That may be the problem your phone went to Panic Mode)
If you have Kernel Panic mode problems (after unstalling SuperSU) a clean reinstall of the latest version of Fulmics ROM would be great..
PS:I don't know if Kingroot has any type of virus but I'll check if it has anything malicious.
As i checked you said that you lost root access and you took it back with Kingroot right?
Sotiris02 said:
Then if you are used to Kingroot just uninstall SuperSu(Install the system app remover from Play store ((the first app that appears)).
Because as i mentioned before if you have two Root applications your phone isn't going to have a good time.
(That may be the problem your phone went to Panic Mode)
If you have Kernel Panic mode problems (after unstalling SuperSU) a clean reinstall of the latest version of Fulmics ROM would be great..
PS:I don't know if Kingroot has any type of virus but I'll check if it has anything malicious.
As i checked you said that you lost root access and you took it back with Kingroot right?
Click to expand...
Click to collapse
Seems I am good after all. Turned out I messed up the fulmics 6.1 badly when trying to get adaway for youtube to work. So now I got fulmics 6.5. Yeah I know it is not the latest but I had slow internet connection and 6.5 was already downloaded but not yet installed so I just picked that and did a swipe, and twrp install of fulmics 6.5.
I did however install king root 5.01 again to get an easy way of getting everything else important installed that requires root.
If I don't see more warnings I think I will be fine. If I do I will take the plunge for superSU and read up on that before making the switch.
If I see those warning signs again I will try not to panic and try to keep calm
Ok so, I have known magisk for its root hide feature.....as systemless root method and, you know, first things you read about it
Now I'm realizing it's bigger than that......with modules!
wow, xposed wasn't f%&ing up our devices enough, now we need magisk modules too
joke, anyway....I once tried to flash it and resulted in bootloop (like 5/6 months ago) so it was closed story for me
BUT again....I see everyone asking for it, modules and stuff....
I know that unless you use special carrier features is not mandatory
So now....these are my questions to you, magisk power users:
1) Is it better/less invasive on the system than lastest superSU beta?
2) is it better for performance? or stability?
3) are there really useful modules? do many modules break things, decrease performance/stability as xposed does? (yes. I hate xposed)
thank you for your attention
Since no one else has given input yet, although I'm not very experienced with Magisk, I'm using it right now for the first time.
The most popular reason for using Magisk as far as I've noticed is so that you can successfully and easily hide that you're rooted so that you can use Android Pay, Pokemon Go and some other apps that check for that.
The only reason I'm using Magisk right now is because I'm running Viper10 ROM with it's all SuperSU option and although I believe my phone kept root after the Play Store SuperSU update to 2.80 and updating binaries/rebooting, the update to 2.81 broke SuperSU for me so badly that even flashing 2.8x or 2.79 SR3 SuperSU zips didn't restore root/SuperSU even after a dirty flash of the ROM.
I could've restored a TWRP backup but instead did a dirty flash of the ROM but with the full Magisk option and now root is restored.
Overall I like SuperSU better because I don't need any apps that won't run while detecting root, and I like SuperSU's ability to require a pin when granting superuser access.
By the way I really liked Xposed but I don't need it as much any more because of Nougat's custom tiles feature and the excellent ROMs available.
I'm really glad you asked this because I can' tseem to find a proper tutorial on how to install magisk and keep things such as my Banking app and other Finger print recognition software working correctly.
Have you found a tutorial which shows you how to do this?
gaiden0000 said:
I'm really glad you asked this because I can' tseem to find a proper tutorial on how to install magisk and keep things such as my Banking app and other Finger print recognition software working correctly.
Have you found a tutorial which shows you how to do this?
Click to expand...
Click to collapse
Instructions are in the Magisk thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
If you already have twrp then it's as easy as just flashing the zip file. For your banking app etc, after you've flashed Magisk from the above thread, you just need to open the Magisk Manager app, go to settings and enable Magisk Hide. Then go into the Magisk Hide menu and chose the apps want to hide root from.
Magisk is an amazing creation.
Although I am in no way a power user of Magisk, as I don't use it myself, at the moment. This doesn't mean I don't recognize the importance and brilliance of the Application and what it can do.
For awhile, it was mandatory to use Magisk ROMs for VoLTE/Wi-Fi Calling on Nougat firmware, but that was squashed (updater-script issues if I recall correctly. A great team effort though for those that fixed it).
Anyway, I guess my .2 cents is this. If you need a system-less set-up, for whatever reason. Be it Pokemon, or banking applications, etc...
Then Magisk is highly suggested, and really the only route. The modules that are being created are amazing.. However, they don't do anything that can't be done to the system itself. Unlike Xposed, which could do a lot of things (I also hate Xposed..) with its modules, this is different.
Such as this recent Magisk Module that was shared, I just went ahead and enabled it manually in my ROM.
Since I have no use for system-less I run my device the same way I always have. TWRP recovery and flashing custom ROMs. The latest SuperSU has fixed all root issues for myself on Sense based ROMs, and I like to use the stock LOS SuperUser on AOSP/LOS based ROMs.
I use multirom and it is an amazing creation, should check it out. Worth a peek.
Best of luck with whatever direction you decide to go.
Hey guys. Im new to this whole android rooting world, so i have a problem.
I rooted a phone with instructions i got from needrom.com.
I tried to flash it first with flash tool, but it always stops to an error.
Don't really know what im doing wrong.
So, anyway. I got now twrp installed, phone is rooted and magisk manager installed partly.
Reason i wanted to root this, is to spoof at pokemon go, so my disabled daughter can enjoy the game too, as my son and i am already.
But, as you know pokemon go wont work with rooted device straight, so i wanted to install magisk manager to hide root from pokemon go.
But phone wont flash to magisk manager version 14. It gets error too. With its own installer, and through twrp recovery mode too.
I was able to flash version 12.5 with no problems at all. But then i tried 13.5, and it gets the same error too.
Now i dont know what do i do. I can't make pokemon go to work at all on that device anymore. I tried to unroot from SuperSU, but then pokemon go said that:
This device OS or software is not compatible with Pokemon GO.
So i restored a backup with twrp. Its now rooted again.
I would like to get the Magisk manager to work properly of course. Please help me guys.