After successfully rooting my Turbo with the app version of Kingroot (PC Version never works for me), I'll open Sunshine and attempt to get to unlock the bootloader, but about 30 seconds to a minute after having success rooting, every single possible app on my phone starts crashing, and I get all those pop-ups, and am unable to get rid of them without restarting, after which root is gone.
What do I do?
Thanks in advance for your help!
maxtheax said:
After successfully rooting my Turbo with the app version of Kingroot (PC Version never works for me), I'll open Sunshine and attempt to get to unlock the bootloader, but about 30 seconds to a minute after having success rooting, every single possible app on my phone starts crashing, and I get all those pop-ups, and am unable to get rid of them without restarting, after which root is gone.
What do I do?
Thanks in advance for your help!
Click to expand...
Click to collapse
After much retrying, it finally worked for no reason whatsoever (I did nothing differently). I now have my bootloader unlocked, and I've flashed SuperSU, which I think is all I need to do...?
Related
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Drew333 said:
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Click to expand...
Click to collapse
Pretty sure you can't encrypt once you root. Or maybe it's once you put a custom recovery. I've never been able to use encryption after rooting my phones.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Drew333 said:
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Click to expand...
Click to collapse
I ran into this myself and couldn't figure it out. I had flashed, rooted, then tried to encrypt and had the same result you did. Finally I tried flashing, encrypting THEN rooting and it worked. Hope this helps.
Hey be careful if your looking to install Safe Strap. Word for word what hashcode said
"THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW."
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
STraver said:
I ran into this myself and couldn't figure it out. I had flashed, rooted, then tried to encrypt and had the same result you did. Finally I tried flashing, encrypting THEN rooting and it worked. Hope this helps.
Click to expand...
Click to collapse
I'm experiencing the same issue and changing the flash/encrypt/root sequence doesn't seem to change the results (encryption will not work, phone reboots). I'm attempting to root using CF's auto-root tools.
Wondering if there may be another root technique that wouldn't trip up the encryption process?
Disclaimers...
1. I know that encryption on a rooted device doesn't make much sense, but encryption is being forced down via the Exchange sync policies
2. I also know that the company might take a dim view of my attempt to root the device, but... they didn't explicitly tell me not to either
I have downloaded kingroot and have used it to remove some system apps. Because it is a temporary root, I have to reroot it every once in a while. One time, after being rooted, it began spamming the screen with error messages that the play store and other apps stopped running. I rebooted the phone and the root and the problem were gone. I tried to root again and I had the same problem. This time when I tried to restart the phone, I had to put it in that mode where you hold the power and volume down buttons and restart the bootloader and then power down and then power up. For now I have deleted the kingroot app, but there are still files that won't go away. How can I get rid of these? Also what suggestions do you have if I decide that I want to pay for sunshine in the future? What app should I use instead to get to where I can use sunshine?
Jefff0101 said:
I have downloaded kingroot and have used it to remove some system apps. Because it is a temporary root, I have to reroot it every once in a while. One time, after being rooted, it began spamming the screen with error messages that the play store and other apps stopped running. I rebooted the phone and the root and the problem were gone. I tried to root again and I had the same problem. This time when I tried to restart the phone, I had to put it in that mode where you hold the power and volume down buttons and restart the bootloader and then power down and then power up. For now I have deleted the kingroot app, but there are still files that won't go away. How can I get rid of these? Also what suggestions do you have if I decide that I want to pay for sunshine in the future? What app should I use instead to get to where I can use sunshine?
Click to expand...
Click to collapse
See the post I made on your other thread for instructions on how to remove Kingroot.
The latest version of Sunshine requires no other apps to unlock the Turbo.
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Just looked now. For one example, SuperSU acknowledges AdAway, but when I try to fire up AdAway, it won't work, saying it doesn't have access.
Did you install twrp and did it ask after you booted to twrp if you wanted to root the device.. if so this was a no no.. your already rooted twrp just get a little confused with the new kernels... you must remove root and reinstall supersu and when it ask when you load twrp do not root but reboot do not swipe... unless there is an easier way this worked for me...
I had the same or a similar problem. I didn't lose root completely but at times various apps were unable to gain root (after previously getting it successfully). The phone would freeze while Titanium or Root Explorer for example were waiting fruitlessly for root to be granted. It was haphazard. One time the app would work and next time it wouldn't, or another wouldn't.
Finally it got so frustrating that I installed my favorite rom on it (Tekhd). Now all is stable. I was hoping to keep it stock rooted until mm came out but I couldn't figure out what was going on so I blew it away. I had twrp on it too and would always be prompted "root not detected" but if I allowed it to install SuperSu it would loop.
Sent from my SM-N910T3 using XDA-Developers mobile app
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Eric618 said:
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Click to expand...
Click to collapse
you need to odin the firmware for your phone and then restart fresh
without root twrp won't install rom you will get error..
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Eric618 said:
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Click to expand...
Click to collapse
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Thanks! I'll give that a try when I get home today.
S5Sickness said:
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Click to expand...
Click to collapse
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Eric618 said:
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Click to expand...
Click to collapse
Your Welcome...
Eric618 said:
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Click to expand...
Click to collapse
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
marseillesw said:
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
I had tried that. It was very sluggish, and would frequently drop root access altogether. Since following S5Sickness's advice it's been solid, however.
https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app
I know these phones are a bit dated, but I have a pair of AT&T SGH-I747's that I've been trying to get rooted. Using Kingoroot, they both crashed and rebooted at different %'s and upon reboot one failed and one passed the root checker test.
The one that passed crashes upon attempting to do anything with root (seemingly as soon as an app requests the permission), this includes attempting to update the binary for SuperSU and any other root-based app.
The one without root continues to crash upon re-attempting the root process. Attempting a CF-Autoroot via Odin elicited a crash during the "Extracting" step on the phone (the actual Odin part went fine).
Is there any way to fix whatever may have been damaged/corrupted by the initial crashes and start over, or otherwise repair it? If there is a crashlog somewhere I can access I will post that if someone tells me where it may be.
Thanks in advance.
Hi guys,
I am using my 1+5T for almost 2.5+ yrs now and since beginning i rooted the mobile for trying new custom ROM's, installing substratum themes, ad blocking etc etc.
Now many banking/payment related apps, maadhar, etc are showing as my phone is rooted. Magisk HIDE is not helping anymore.
So, i uninstalled magisk root and still my OEM is unlocked. all the previous apps shows similar message as my mobile is rooted.
How should i completely unroot my mobile without leaving any trace so that these apps doesn't show rooted messages again ?
Any Idea ?
NOTE: Previously i completely unrooted my mobile & still many apps shows rooted so got to root my mobile and used magisk HIDE .....
Haki! said:
Hi guys,
I am using my 1+5T for almost 2.5+ yrs now and since beginning i rooted the mobile for trying new custom ROM's, installing substratum themes, ad blocking etc etc.
Now many banking/payment related apps, maadhar, etc are showing as my phone is rooted. Magisk HIDE is not helping anymore.
So, i uninstalled magisk root and still my OEM is unlocked. all the previous apps shows similar message as my mobile is rooted.
How should i completely unroot my mobile without leaving any trace so that these apps doesn't show rooted messages again ?
Any Idea ?
NOTE: Previously i completely unrooted my mobile & still many apps shows rooted so got to root my mobile and used magisk HIDE .....
Click to expand...
Click to collapse
As long as your bootloader is unlocked, they will report your device as rooted. If Magisk Hide alone doesn't work, try the "Repackage Magisk Manager" option in Magisk Manager settings. It works for me.
Sent from my #FlagshipKiller6T using Tapatalk
DarkSJ1998 said:
As long as your bootloader is unlocked, they will report your device as rooted. If Magisk Hide alone doesn't work, try the "Repackage Magisk Manager" option in Magisk Manager settings. It works for me.
Sent from my #FlagshipKiller6T using Tapatalk
Click to expand...
Click to collapse
I found the problem i uninstalled magisk manager then all apps started working with boot lock loader Unlock.
Now i locked everything and went back to normal.
Haki! said:
I found the problem i uninstalled magisk manager then all apps started working with boot lock loader Unlock.
Now i locked everything and went back to normal.
Click to expand...
Click to collapse
Hi, I too have your own problems with an app. I can no longer hide the root. How did you do? I Magisk I had flashed via Recovery
Fix_ita said:
Hi, I too have your own problems with an app. I can no longer hide the root. How did you do? I Magisk I had flashed via Recovery
Click to expand...
Click to collapse
I unrooted my mobile but still magisk manager was installed so apps showed message "my phone is rooted". After that i uninstalled magisk manager and all apps started working fine.
Now i am unrooted but my bootloader is unlock.
Well, I still have that same problem. But only from Samsung Pass with an actual message box, which says that my device is rooted so can't use the app for security reasons.
I rooted my Galaxy S20 FE 5G SM-G781B with Magisk and afterwards uninstalled it with the Complete Uninstall method, but after automatic boot, that procedure only gave me some weird errors and I couldn't boot the phone.
It got stuck to this error filled download mode screen. There I saw an option to lock the bootloader back. Well, did that but then my phone got itself into a boot loop!
I managed to get to the download mode (in between the loops) and then it became even more errored and with all red alert stuff there!
Thought I bricked the whole damn device which I only bought like two weeks earlier rip.
Well then after some google fun time I downloaded original stock firmware to odin it. Well, nothing worked and always failed!
Then afterwards it became to my attention to try to flash the firmware that I originally flashed just before installing Magisk.
Heck yeaaah that actually worked lol and all bank stuff works and even software update and I now have all the newest updates etc and Magisk and Root Checker shows no root and then I removed Magisk for good and rebooted the phone to check any surprises.
No surprises and everything works, EXCEPT Paypal app and Samsung Pass!
Paypal just says after trying to log in "Please check your information and try again", but Samsung Pass actually says that "Your device has been rooted. Samsung Pass cannot be used on rooted devices for security reasons."
So what the heck!
I hate myself for rooting the new phone for nothing and now my ocd suffers for having that stupid whatever error stuff there, especially since I actullay USE Samsung Pass and Paypal!
EVERYTHING else works just fine, but not those two!
Grrr!
So all you wise people, can I actually do something about this or not??
Cheers!
@Hopeasilmu I would expect that the Samsung apps will now be complaining since you probably tripped the Knox fuse when you unlocked the bootloader and rooted the device. Once that's tripped you can't get it back...
If you need more info on Knox there's plenty available both here on XDA (check the Samsung forums) and on the web in general.
Haki! said:
I unrooted my mobile but still magisk manager was installed so apps showed message "my phone is rooted". After that i uninstalled magisk manager and all apps started working fine.
Now i am unrooted but my bootloader is unlock.
Click to expand...
Click to collapse
You can still lock the boot loader. There is a way. I did that on my Samsung M31 however I cannot recall the steps.