Related
Update 2: Root was still acting wonky. I was getting multiple requests per app and it wasn't remembering my preference even with the box checked. I tried to allow all but it just wouldn't work at all that way. So I went to update the binaries just to be sure and I had version 3.2 while the latest (and I'm assuming stable) version is only 3.1.1. So if anyone has the problems I did, UPDATE YOUR BINARIES! That fixed everything for me.
Update: I uninstalled the Superuser apk via ES File Explorer, reinstalled it from the Play Store, and just let the phone sit while I was browsing and looking for an answer and when I went back to it Superuser opened and my root was back. I'm not sure if what I did helped but if anyone else has this problem then I can only recommend what I did. If someone can explain what I did wrong or why I lost root, that would still be helpful. If this post needs to be deleted then the mods can do so, I left it in case anyone else runs into this and searches the forums for it.
I have the At&t ion and I managed to get root on ICS on my second try. I was happy about it and decided to start flashing some zips after installing CWM so I deodexed, rebooted, and then flashed one of the status bar tweaks. When I rebooted again Superuser would force close as soon as it opened with the message "Unfortunately Superuser has stopped working". I still have root access in ES File Explorer since I granted it before Superuser stopped working. I cannot however grant any new root permissions since Superuser won't open.
I'm willing to reflash GB and start from scratch again, I'd just like to know what the reason is (was it deodexing? Flashing the zip for the status bar? Or is this just something that can happen?) so I can avoid it the next time. I'm not too excited about having to redownload all my apps for the 3rd time (I was living without root on ICS but decided to go ahead and get it) so if there's a way around it I'd like to find it. Any help is appreciated. I'll try to reply as quickly as possible, thanks guys.
Hello, mates!!
I have a little problem with Dark Knight game in my unrooted Galaxy Note 8 (4.2.2)
About months ago i had version 1.1.3 installed and worked just fine, but i had to delete it because i needed internal storage space.
This week i tried to install it again, but when i start new game and tryin to play intro video, the game freezes (black screen with only skip icon showing but inactive).
Had someone the same problem? Is there a fix?
I have tried almost every version but the same things happens.
So it's probably the android version or some settings fault since i used to play this game...
thanvot said:
Hello, mates!!
I have a little problem with Dark Knight game in my unrooted Galaxy Note 8 (4.2.2)
About months ago i had version 1.1.3 installed and worked just fine, but i had to delete it because i needed internal storage space.
This week i tried to install it again, but when i start new game and tryin to play intro video, the game freezes (black screen with only skip icon showing but inactive).
Had someone the same problem? Is there a fix?
I have tried almost every version but the same things happens.
So it's probably the android version or some settings fault since i used to play this game...
Click to expand...
Click to collapse
Run saferoot and root your device. You can get it on the Easy way to root.. thread.
Once you root, download Ti backup and have it uninstall orphan apps. Somewhere in the system there are files that are left over from your game.
Safe root will not flash increment your counter so performing stock update will function normally. The only issue is Samsung Book Hub will not run in rooted devices. You can hide the root using substrate and Rootcloak to allow apps that do detect rooting to function.
If you are not willing to saferoot... then backup your apps and settings with Kies, and do a factory reset of your system. Then restore your apps and settings before installing your game.
If the game still does not run properly after any of the options I gave, then it is possible you are side-loading part of the app. Some apps like Samsung's Link will not side load properly without permissions and data properly transferred.
Since your not rooted at this time, doing any manual work to fix the issue will not be an option..
gooberdude said:
Run saferoot and root your device. You can get it on the Easy way to root.. thread.
Once you root, download Ti backup and have it uninstall orphan apps. Somewhere in the system there are files that are left over from your game.
Safe root will not flash increment your counter so performing stock update will function normally. The only issue is Samsung Book Hub will not run in rooted devices. You can hide the root using substrate and Rootcloak to allow apps that do detect rooting to function.
If you are not willing to saferoot... then backup your apps and settings with Kies, and do a factory reset of your system. Then restore your apps and settings before installing your game.
If the game still does not run properly after any of the options I gave, then it is possible you are side-loading part of the app. Some apps like Samsung's Link will not side load properly without permissions and data properly transferred.
Since your not rooted at this time, doing any manual work to fix the issue will not be an option..
Click to expand...
Click to collapse
Wow, thanks for your advice... I don't feel like rooting this baby for a while.. but i will try factory reset when i find time to.
I'm not sure i understood what side-loading is... but i'm 100% sure that somewhere in the system there are files that are left over. I wish i could find them or perhaps a Kitkat update sometime soon maybe help. Anyway, i'm going to try new games and then come back with this...
Greetings all..
I am working on the Not e 4 and run a large collection of Xposed mods
I have a Sprint Note 2, Note 3 and Note 4 and the 2&3 have never given me any issues with Xposed Framework Modules.
The frame work
Several are causing boot loops upon reboot.
The device will not boot into safemode- which is a huge pain if you did not do a backup in recovery.
I just wanted to remind everyone that if you install Xposed ( and ignore all of the "make sure you nandroid/ backup first messages) this time REALLY MAKE SURE YOU BACK UP /System at least before you activate mods.
I will post a list of the ones giving me issues shortly as I work out process of elimination.
Do you have an idea why my phone says "updating" after I install Xposed?
It's not stuck or anything but in the status bar it has a logo with a checkmark and I have no service. Am I supposed to freeze something?
I don't use many xposed modules and don't have boot loop issues with the ones I use. My problem is not all options in Wanam works. Like disabling sound waning when putting the volume too high. Hopefully the Wanam devs will fix that.
gfp11289 said:
Do you have an idea why my phone says "updating" after I install Xposed?
It's not stuck or anything but in the status bar it has a logo with a checkmark and I have no service. Am I supposed to freeze something?
Click to expand...
Click to collapse
If you turn off Software Updates from the ApplicationsManager you wont see it anymore.
xxSTARBUCKSxx said:
If you turn off Software Updates from the ApplicationsManager you wont see it anymore.
Click to expand...
Click to collapse
I turned off Software Uodates and it still comes up in the notification bar
I don't get any service either upon installing and restarting with xposed
When you installed xposed installer (assuming this was not from a titanium backup), it should have saved a zip file called, Xposed-Disabler-Recovery.zip to your sdcard or internal memory.
Install it in recovery and it will disable xposed framework so you can figure out which module is not working.
Here's a link:
http://www.datafilehost.com/d/ccb18d00
Deleted. Thanks. ^^^^^^^^
hermeticist said:
When you installed xposed installer (assuming this was not from a titanium backup), it should have saved a zip file called, Xposed-Disabler-Recovery.zip to your sdcard or internal memory.
Install it in recovery and it will disable xposed framework so you can figure out which module is not working.
Here's a link:
http://www.datafilehost.com/d/ccb18d00
Click to expand...
Click to collapse
I'll try it when I get home
I just install this in TWRP?
gfp11289 said:
I'll try it when I get home
I just install this in TWRP?
Click to expand...
Click to collapse
Yes. It removes xposed framework without uninstalling anything.
This way you can use the process of elimination add to which xposed module is screwing up your system:
Reinstall framework, turn one module on at a time, reboot, repeat.
If you are sure individual modules are not messing up, don't bother turning them off.
hermeticist said:
Yes. It removes xposed framework without uninstalling anything.
This way you can use the process of elimination add to which xposed module is screwing up your system:
Reinstall framework, turn one module on at a time, reboot, repeat.
If you are sure individual modules are not messing up, don't bother turning them off.
Click to expand...
Click to collapse
The thing is that I didn't have any modules on. I just installed it, updated it, rebooted, and I'm stuck with no service until after I uninstall it
Weird
Maybe I could try to flash Xposed in TWRP? If that's even possible..
gfp11289 said:
Maybe I could try to flash Xposed in TWRP? If that's even possible..
Click to expand...
Click to collapse
All you have to do is install the apk. Then once in Xposed, install the framework.
Id try uninstalling the framework, deleting the apk and download a fresh apk of xposed and start fresh. Dont associate TWRP with installing Xposed.
I think its working now. For some reason the update stays on my status bar for awhile before it turns off by itself. I tried to send myself some text messages last night and they took a long time to send, or just never sent at all. I have some decent status by my house so that wasn't an issue. I might've not given my phone enough time to boot up xposed or something, but regardless it's working now.
Being connected to wifi, does in anyway affect sending text messages while I'm on xposed? I barely had enough time to test it out when I was at home but driving around my city I was sending myself text messages and they seemed to go through okay.
Wanam Xposed
11/5/14 Wanam Xposed Module update available.
Drama!!! It is just Xposed Framework.
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
I am on latest March security patch .M305FDDU4CTC1 (Android 10 Q).
I got root access with magisk successfully. But one big problem I am facing is root access only working till the phone is not rebooted. What I am saying is I use root explorer, Replace a system app (like weather/clock etc with latest apk got from apkmirror).
It got replaced. Then I reboot my device so that changes takes place but all changes are gone once device is rebooted. The old apk which I replaced is still there and new apk that I placed there is gone! Not even build.prop is editable. Once I edit build.prop and reboot device, it's same as original and edited one is gone. Do anyone has any idea what's going on here ? Please help. Thanks.
To reboot, press and hold vol up+power key together and release 'em both as soon as you see the bootloader warning message. This way, you would be able to reboot the system with magisk. If you try to boot the normal way (pressing power-key), the magisk is likely to be gone.
By pressing vol up and power key together, it takes me to the recovery mode. And I get no bootloader warning.
akhil093 said:
I am on latest March security patch .M305FDDU4CTC1 (Android 10 Q).
I got root access with magisk successfully. But one big problem I am facing is root access only working till the phone is not rebooted. What I am saying is I use root explorer, Replace a system app (like weather/clock etc with latest apk got from apkmirror).
It got replaced. Then I reboot my device so that changes takes place but all changes are gone once device is rebooted. The old apk which I replaced is still there and new apk that I placed there is gone! Not even build.prop is editable. Once I edit build.prop and reboot device, it's same as original and edited one is gone. Do anyone has any idea what's going on here ? Please help. Thanks.
Click to expand...
Click to collapse
Mate, it's because of encryption. No you can't make changes to system directory but you can use magisk modules. Have fun ?
akhil093 said:
I am on latest March security patch .M305FDDU4CTC1 (Android 10 Q).
I got root access with magisk successfully. But one big problem I am facing is root access only working till the phone is not rebooted. What I am saying is I use root explorer, Replace a system app (like weather/clock etc with latest apk got from apkmirror).
It got replaced. Then I reboot my device so that changes takes place but all changes are gone once device is rebooted. The old apk which I replaced is still there and new apk that I placed there is gone! Not even build.prop is editable. Once I edit build.prop and reboot device, it's same as original and edited one is gone. Do anyone has any idea what's going on here ? Please help. Thanks.
Click to expand...
Click to collapse
This should not happen, as I am rooted, and I have changed a lot of stuffs. Just ensure you give proper permission, and you exit the file explorer. BTW, you will have to mount as root+mount in read-write, else your changes will not work.
That was happening because I was using stable magisk. When I switched to canary magisk, I was able to push apps into system via lucky patcher. But nothing matters now, as I unrooted & locked the bootloader back. Google killed magisk hide by applying hardware attestation in safteynet which fails our devices to hide our bootloader status. Most safteynet apps (paytm, netflix, google pay, pokemon go & banking apps) could stop working in future.
akhil093 said:
That was happening because I was using stable magisk. When I switched to canary magisk, I was able to push apps into system via lucky patcher. But nothing matters now, as I unrooted & locked the bootloader back. Google killed magisk hide by applying hardware attestation in safteynet which fails our devices to hide our bootloader status. Most safteynet apps (paytm, netflix, google pay, pokemon go & banking apps) could stop working in future.
Click to expand...
Click to collapse
I actually am fully rooted and also have banking apps working. I seriously do not trust PayTM, PhonePe, etc, as all are big time cheaters, and all are data sellers. Morons. Anyways, I do not use fuuked apps (read gapps), and am fully FLOSS (except for banking apps).
All safteynet apps working now but once Google flick the "switch" of Safteynet (which now uses hardware backed attestation) all of those apps will know the device is rooted and will stop works.
akhil093 said:
All safteynet apps working now but once Google flick the "switch" of Safteynet (which now uses hardware backed attestation) all of those apps will know the device is rooted and will stop works.
Click to expand...
Click to collapse
FOSS and FLOSS will not have this. So I am fine. All I use is one banking app, which I can very well use via browser. So no worries for me.