[HELP] unrooted phone without uninstalling xPosed
Hi, I have a Wiko Highway that I want to send to warranty.
So i had my phone rooted, and unrooted it and then factory reseted it, but i forgot to uninstall xPosed and its modules.
Now i started to install some apps so i dont send the phone empty, and when installing snapchat it wont let me login (as it block's rooted phones)
So, by some way snapchat "thinks" i'm still rooted, i'm afraid the provider can tell that :/
Is there anyway to prevent this?
Thanks
Assuming you don't have a backup...
If it's a kitkat or older phone then reroot and uninstall using the xposed app.
If it's lollipop+ then, first off shame for not making a backup since you need a custom recovery to install lollipop version, use the uninstaller from the main download thread.
If it's kitkat or older and you can't root and the app claims xposed is active then when you boot the phone repeatedly press your power button til the phone vibrates a bunch and that should at least disable xposed.
As for sending it in for warrenty if they were going to reject it then they'd look at a tamper flag and there's a precious few devices that you can reset that on. Cross your fingers basically.
Hi, thanks for the reply
I tried rerooting and i'm not being able to :s
As for rebooting with xposed disabled it didnt make the app work
And how could i reset that flag?
Thanks again for the reply
Related
So I decided I should to a factory reset on my Moto X today to clean it up and make it run better. Anyway I downloaded Towel Pie Root, rooted the phone, and backed up my apps with TB. My phone hadn't been rooted up to this point. Anyway I did the app backup and pulled my /sdcard/ contents to my laptop with adb and did the factory reset. Afterwards I got everything updated, restored the apps I wanted with TB(after rerooting with TPR), and got the phone set back up like I wanted. I also decided I'd give Xposed a try being that rooting was fairly simple with TPR. I downloaded Xposed 2.6.1, installed the framework and did a soft reboot. After doing that I can't connect to WiFi anymore; I just get a "Failed to Connect to Network" toast notification when I try. A Hard Reboot fixes the issue until I reinstall Xposed then WiFi breaks again.
Any ideas on why this is happening or how to fix it? I know I read in the TPR thread that people were using Xposed with TRP like I'm trying to.
Sent from my MacBook Pro using Chrome
Phone: Moto X(XT1053) running Stock 4.4.3
I've seen this topic mentioned in the forum but I have yet to find an answer that works. Maybe there isn't one, but here goes...
I have a Droid Maxx that shipped with 4.4.2. I rooted it with the PIE Exploit and everything went as expected. I set SuperSU to survival mode, and took the 4.4.4 OTA. This did not seem to kill root access, so again, all was well. Then, I installed Xposed and rebooted...fine. Installed some modules, configured them, rebooted..."Xposed is not active." So, I updated the framework and soft rebooted...everything works. However, if I hard reboot at any time, I get the "latest version is not active" error in Xposed. The only thing that fixes it is to update and soft reboot.
Mind you, root access is surviving these hard reboots. I check with SuperSU, Terminal and Root Checker each time just to be sure, and root is not failing. So what the heck is the issue with Xposed? Every time I see this topic brought up, the only advice is to update Xposed or to make sure you have root. Check and Check. Unless I'm missing something, it seems like root is permanent since it survives reboot. I've tried uninstalling/reinstalling everything one at a time, denying/granting root access to Xposed, etc. but nothing fixes the problem.
Is there a solution to this that I'm not seeing, or is this actually an unfixable bug?
So i just finished the process of rooting my s2 tablet 810 5.1.1 and every time i reboot or turn the phone on and off i notice a message that says
"Kernel is not seandroid enforcing
set warranty bit: kernel"
Ive done some google searches and i would like to think its normal becuase i read in a thread that this is because of the knox trip.
however i also see threads dedicatied on how to resolve this "issue"
As some of you guys might already know if the version is 5.1.1, then you need a kernel to load during the process of root.
when i attempted to root the first time the kernel boot did not restart my tablet for me, so i manually restarted even though the option was set to auto-reset.
I now believe the process was incomplete because the tablet entered a boot loop after i ran the auto-root file. (Failed 1st attemp)
Second attempt i ran the kernel file and then the tablet rebooted successful, howver THIS is when the "Kernel is not seandroid enforcing set warranty bit: kernel"
is something wrong or is all good? gonna check if i have root after this post.
SIDE QUESTION
in the thread of the guy who posted about how to root he mentions how to put a custom recovery. Is that mandatory? or can i do this later when i want to install a custom ROM?
will post agian if anything important comes up after i check if ROOT
Okay so something interesting did come up. It seems i am rooted, however i keep getting a notification that an unauthorized action haas been taken and i must click on a restart to undo the changes that have been done.
its kind of annoying because it keeps popping up. I assumw this is the knox security.
there is an option for "sperate work and play" where i can install knox app in a safe and isolated space. what is this?
should i just ignore this poppup ? or is there a way to get rid of it?
someone to talk to would be nice right now .
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
I understand what a custom recovery does, ive had it on my two previous phones and have tried TWRP and CW.
however i only installed them because i wanted to flash a custom rom on those two phones. With my s2 tablet im looking to just stay with root for now, that is why i am asking if the custom recovery is a must? because i dont see any use for it if i am just going to keep my tablet rooted and not flash any roms yet
also any idea on how to get rid of that pop up in notification saying i must click the restart to undo the changes that have been made
danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Originally I said I froze and unistalled SecurityLogAgent, however I did not. So I did it now. I will report back if I go error free.
Thank you!
I am having this same issue. I have twrp recovery installed, I have disabled/unistalled everything with knox security symbol . I continue to get this error. I have wiped everything and started fresh and cannot get rid of this error. The second problem i am having, I cannot reinstall those apps with TB, I tried each of them and I even let it set overnight while I slept and it was still going when I woke up.....
1. How can I get rid of this error?
2. If I can't how can i get tb to reinstall knox or can I unroot without having these reinstalled?
this is everything I have froze, backed up, and unistalled
BBCAgent 2.0
com.samsung.android.bbc.fileprovider
com.samsung.knox.kss
com.sec.knox.containeragent2
com.sec.knox.packagegeverifier
com.sec.knox.sortcutsms
com.sec.knox.switcher
KLMS Agent 2.5.312
KNOX 2.3.0
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer2.4.0
Getting rid of all Knox apps is good when you are rooted but the anoying pop-up comes from SecurityLogAgent app and not from Knox apps, as soon as you freeze or uninstall it the message will stop.
Sent from my SM-T810 using Tapatalk
I've tried installing Xposed several times now with no luck. I install in TWRP, reboot, and then my phone sits on a black screen with the blue light for forever until it goes to the Sprint LTE logo and then just stops there. I end up having to shut my phone down (which won't happen unless it's plugged in to charge), go back into TWRP, and then use the Xposed uninstaller. Then when I reboot, everything loads back up perfectly. I don't really know what's causing this? I apologize as I'm kind of a noob to rooting & such.
I have a Galaxy Note 5 SM-N920P on Android 6.0.1. Any advice?
(The only reason I really wanted to get Xposed is so I could install a module to bypass the root status for Snapchat...lol)
kdisn said:
I've tried installing Xposed several times now with no luck. I install in TWRP, reboot, and then my phone sits on a black screen with the blue light for forever until it goes to the Sprint LTE logo and then just stops there. I end up having to shut my phone down (which won't happen unless it's plugged in to charge), go back into TWRP, and then use the Xposed uninstaller. Then when I reboot, everything loads back up perfectly. I don't really know what's causing this? I apologize as I'm kind of a noob to rooting & such.
I have a Galaxy Note 5 SM-N920P on Android 6.0.1. Any advice?
(The only reason I really wanted to get Xposed is so I could install a module to bypass the root status for Snapchat...lol)
Click to expand...
Click to collapse
Which Xposed file did you flash?
Sent from my SCH-R220
mattzeller said:
Which Xposed file did you flash?
Sent from my SCH-R220
Click to expand...
Click to collapse
I think I downloaded from here. Xda website wasn't working last night while I was doing it.
http://android.wonderhowto.com/how-...work-android-6-0-marshmallow-devices-0166278/
kdisn said:
I think I downloaded from here. Xda website wasn't working last night while I was doing it.
http://android.wonderhowto.com/how-...work-android-6-0-marshmallow-devices-0166278/
Click to expand...
Click to collapse
If you running stock 6.0.1 and not a CM ROM you need the specialized one for Samsung. Check this thread:
http://forum.xda-developers.com/showthread.php?p=62377731
Don't forget after flashing it you should wipe caches, and it will take a little while to boot the first time after flashing Xposed
Sent from my SCH-R220
mattzeller said:
If you running stock 6.0.1 and not a CM ROM you need the specialized one for Samsung. Check this thread:
http://forum.xda-developers.com/showthread.php?p=62377731
Don't forget after flashing it you should wipe caches, and it will take a little while to boot the first time after flashing Xposed
Sent from my SCH-R220
Click to expand...
Click to collapse
I'm running stock, yes. Thank you for the link. I'll try it and then let you know!!
mattzeller said:
If you running stock 6.0.1 and not a CM ROM you need the specialized one for Samsung. Check this thread:
http://forum.xda-developers.com/showthread.php?p=62377731
Don't forget after flashing it you should wipe caches, and it will take a little while to boot the first time after flashing Xposed
Sent from my SCH-R220
Click to expand...
Click to collapse
The file you sent worked great still can't get into Snapchat though, but that's another issue. RootCloak doesn't do anything for it.
kdisn said:
The file you sent worked great still can't get into Snapchat though, but that's another issue. RootCloak doesn't do anything for it.
Click to expand...
Click to collapse
Suhide hides root from snapchat, but Snapchat doesn't want you to have Xposed. There is a work around involving backing up app data on an unrooted, no Xposed phone and restoring that app data on rooted and Xposed phone
Sent from my SCH-R220
mattzeller said:
Suhide hides root from snapchat, but Snapchat doesn't want you to have Xposed. There is a work around involving backing up app data on an unrooted, no Xposed phone and restoring that app data on rooted and Xposed phone
Sent from my SCH-R220
Click to expand...
Click to collapse
I have tried several things and have been unable to get Snapchat to login. I have a backup of a logged in Snapchat from an unrooted device and when I install it onto my rooted phone, the app just logs me out.
kdisn said:
I have tried several things and have been unable to get Snapchat to login. I have a backup of a logged in Snapchat from an unrooted device and when I install it onto my rooted phone, the app just logs me out.
Click to expand...
Click to collapse
Maybe remove Xposed, then unroot, root systemless(at least SR2), root switch, then turn off root and login. Once logged in turn root back on and install Xposed. Should work
Sent from my SCH-R220
mattzeller said:
Maybe remove Xposed, then unroot, root systemless(at least SR2), root switch, then turn off root and login. Once logged in turn root back on and install Xposed. Should work
Sent from my SCH-R220
Click to expand...
Click to collapse
I'll try that. I flashed from Odin to wipe everything off and Snapchat works, but I don't have TWRP anymore. Even without Xposed and root, even when I JUST had TWRP, Snapchat wouldn't let me log in. But I'll try what you told me and hope it works
mattzeller said:
Maybe remove Xposed, then unroot, root systemless(at least SR2), root switch, then turn off root and login. Once logged in turn root back on and install Xposed. Should work
Sent from my SCH-R220
Click to expand...
Click to collapse
So after a bunch of trouble with my phone, I'm left with what I can only assume are leftover files of Xposed that I didn't get off my phone when I flashed the uninstall file. I'm not rooted and only have TWRP, but Snapchat still refuses to let me login.
kdisn said:
So after a bunch of trouble with my phone, I'm left with what I can only assume are leftover files of Xposed that I didn't get off my phone when I flashed the uninstall file. I'm not rooted and only have TWRP, but Snapchat still refuses to let me login.
Click to expand...
Click to collapse
Maybe do a factory reset to clear those out and see if snapchat will work
Sent from my SCH-R220
mattzeller said:
Maybe do a factory reset to clear those out and see if snapchat will work
Sent from my SCH-R220
Click to expand...
Click to collapse
I ran the uninstaller for Xposed again and it seems to have wiped the rest of the files because snapchat now lets me login. Now time to follow the instructions you gave me before w/ systemless rooting my NAND is backed up too just in case I screw up again.
2 days ago i rooted my G800F with CF-auto-root through ODIN. (Used the latest CF-auto-root from here , with ODIN v3.10.6)
But after that my device is too laggy!
Much slower as it had 512 RAM. Root success was confirmed with Root Checker
SuperSU was also installed but sometimes i get a message that SU binary isn't installed.
I 've tried with "ROM toolbox" and "System App Remover" to unistall some system apps but i got the message "Failed to Unistall xxxxxxx app". But if i entered again "ROM toolbox" i found out that the xxxxxx app wasn't there. It has been unistalled!
Once Play Store didn't let me upgrade some apps, because it said that i must logged in to my account (which i was already logged in), and others problems like that!
What shall i do now?
Root again the device? Unroot the device and root again? Unistall Knox? (i've read somewhere that Knox is responsible for problems after rooting). Find another version for CF- auto-root? (the latest is for Build ID LMY47X.G800FXXU1BPB2 but mine is LMY47X.G800FXXU1BPC4 if it matters)
Please help!
Yes, if you have root you must disable Knox. If it doesn't help, you can try go back to stock to see if it's a hardware issue (it will still lag), then root again if everything is fine for a day or two...
lfom said:
Yes, if you have root you must disable Knox. If it doesn't help, you can try go back to stock to see if it's a hardware issue (it will still lag), then root again if everything is fine for a day or two...
Click to expand...
Click to collapse
I have this device for about 2 years. These problems have begun just after rooting. So, i believe it is not a hardware problem.
By saying disable Knox you mean delete/unistall or freeze?
And how can i do that?
billphone said:
I have this device for about 2 years. These problems have begun just after rooting. So, i believe it is not a hardware problem.
By saying disable Knox you mean delete/unistall or freeze?
And how can i do that?
Click to expand...
Click to collapse
I would first use Link2SD to freeze all related to Knox and Security log first. If everything went right, backup and delete files.
lfom said:
I would first use Link2SD to freeze all related to Knox and Security log first. If everything went right, backup and delete files.
Click to expand...
Click to collapse
I freezed all apps and having the word Knox in their names. The phone isn't so laggy now but if i open some apps for rooted devices such as Busybox or Rom Toolbox they can't operate and got a message that my device isn't rooted. After that, no others apps for rooted devices are working! The SU doesn't open at all! All will work again after restart (except ofcourse Busy box Rom toolbox)
So what shall i do?
Unroot and root again? Root again over the previous root? What else?
billphone said:
I freezed all apps and having the word Knox in their names. The phone isn't so laggy now but if i open some apps for rooted devices such as Busybox or Rom Toolbox they can't operate and got a message that my device isn't rooted. After that, no others apps for rooted devices are working! The SU doesn't open at all! All will work again after restart (except ofcourse Busy box Rom toolbox)
So what shall i do?
Unroot and root again? Root again over the previous root? What else?
Click to expand...
Click to collapse
I thought that CF-Auto-Root disabled Knox protection when used, but maybe not... I think there is an option in SuperSU to disable it, you must use it as soon as you open it after using CF-Auto-Root and booting again to Android. If it doesn't have this option, it's not only Knox that makes the security system that prevents root, there is SecurityLog too (and on MM I think I've seen Rootpd that probably is a root protection daemon). Probably it removed su when you were disabling Knox. If you can root again over the current state, probably you can try disabling security system completely this time. Check other threads about rooting G800F, probably there is a list of apps you must disable.
lfom said:
I thought that CF-Auto-Root disabled Knox protection when used, but maybe not... I think there is an option in SuperSU to disable it, you must use it as soon as you open it after using CF-Auto-Root and booting again to Android. If it doesn't have this option, it's not only Knox that makes the security system that prevents root, there is SecurityLog too (and on MM I think I've seen Rootpd that probably is a root protection daemon). Probably it removed su when you were disabling Knox. If you can root again over the current state, probably you can try disabling security system completely this time. Check other threads about rooting G800F, probably there is a list of apps you must disable.
Click to expand...
Click to collapse
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
billphone said:
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
Click to expand...
Click to collapse
SuperSU is the app, su is the superuser daemon. Good luck.
billphone said:
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
Click to expand...
Click to collapse
So finally the problems are still here. The device is no longer laggy, but the root sometimes works sometimes doesn't.
I root again over the previous root, again the same. I unroot and again root, the same. I install a custom recovery and flash the SuperSU, the same results.
Initially working fine, giving rights to the applications but later sometime does not. With restart reverts briefly again.
What on earth has gone wrong? I have root many devices and all of them were working perfect!
I would like to avoid factory reset because i don't know how to restore my backup without problems.
Is there another solution?
Knox disables root, it can even revert custom recovery. Did you disable it, as well as Security Log (disable its updates in settings first), as suggested previously?
lfom said:
Knox disables root, it can even revert custom recovery. Did you disable it, as well as Security Log (disable its updates in settings first), as suggested previously?
Click to expand...
Click to collapse
Yes, i disable some apps with the word Knox in them. I don't know if is still a Knox app with a different name. Is there a list with Knox apps?
I didn't disable the Security Log neither its updates. Where can i find them?
So, finally i have a rooted device which randomly unroot itself!
And nothing can be done!