Is there anyway I can re-root my device? I was originally rooted with Root De La Vega and did not freeze AT&T software update nor do the SU survival mode when I applied the new OTA update. Currently, I am "Custom" with "0x0" unrooted.
siviog1 said:
Is there anyway I can re-root my device? I was originally rooted with Root De La Vega and did not freeze AT&T software update nor do the SU survival mode when I applied the new OTA update. Currently, I am "Custom" with "0x0" unrooted.
Click to expand...
Click to collapse
This is all over the forum, you can just use Kingo re-root, there is another way as well where you dont have to use Kingo root keeper or something like that.
im not sure, but a quick search will bring all your options for you to chose from.
the2rrell said:
This is all over the forum, you can just use Kingo re-root, there is another way as well where you dont have to use Kingo root keeper or something like that.
im not sure, but a quick search will bring all your options for you to chose from.
Click to expand...
Click to collapse
I tried using Kingo 1.1.5 app but the result is "ROOT Failed - NotSupport" during the rooting process Downloading requisite default files...
Root was successful after -
1. Disable Lookout
2. Disable Security policy updates
3. Disable Verify Apps
4. Turned on USB Debugging
Stayed in Normal Mode
Kingo Recognized the device
Started the Root process
SuperSU was disabled - Enabled via Playstore
Root Verified
Related
if you have knox 0x0 and took a OTA update does this mean you cant re-root i was rooted then i was foced to update then my root was gone
but my custom rom stayed and super su has now lost all granted access so i'm confused am i not able to root any more because of the update
or what? because odin keeps failing i real want to root my phone again
please help thanks in advance here is my info
Right here: http://forum.xda-developers.com/showthread.php?t=2510603
Does not trip knox, roots MJ5, and does not wipe anything.
-----------------------------------------------------------------------------------------------------------------------------------------------
alwayswatching said:
if you have knox 0x0 and took a OTA update does this mean you cant re-root i was rooted then i was foced to update then my root was gone
but my custom rom stayed and super su has now lost all granted access so i'm confused am i not able to root any more because of the update
or what? because odin keeps failing i real want to root my phone again
please help thanks in advance here is my info
Click to expand...
Click to collapse
If su is still there (/system/bin/su or /system/xbin/su), all you need is SuperSU, which you can install from the Play store. (Without an "su-ish" app, apps can't get root, even though su is installed.) If su isn't still there you'll have to root again.
reply
ZOOPidy said:
Right here: http://forum.xda-developers.com/showthread.php?t=2510603
Does not trip knox, roots MJ5, and does not wipe anything.
-----------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
thanks so much i will try now didnt want to brick my new phone i got from the wife and the watch
thanks again
reply
Rukbat said:
If su is still there (/system/bin/su or /system/xbin/su), all you need is SuperSU, which you can install from the Play store. (Without an "su-ish" app, apps can't get root, even though su is installed.) If su isn't still there you'll have to root again.
Click to expand...
Click to collapse
thanks super su is still there so your saying all i need to do is upgrade the super su or reinstall it
then grant access ?
alwayswatching said:
thanks super su is still there so your saying all i need to do is upgrade the super su or reinstall it
then grant access ?
Click to expand...
Click to collapse
No, if SuperSU is still there and you don't get root, the su binry is evidently missing. That mans that you have to root all over again. (You need to be rooted to install the su binary, which you aren't, so ... which is why rooting uses an exploit [a different one in each line of phones] to get temporary root so it can install su to get permanent root.)
reply
Rukbat said:
No, if SuperSU is still there and you don't get root, the su binry is evidently missing. That mans that you have to root all over again. (You need to be rooted to install the su binary, which you aren't, so ... which is why rooting uses an exploit [a different one in each line of phones] to get temporary root so it can install su to get permanent root.)
Click to expand...
Click to collapse
i have tried with odin but it keeps failing should i use the kingo root insted ?
at this stage what would be the best way to re-root
thanks in advance
Are you following these instructions? http://forum.xda-developers.com/showthread.php?t=2559715
Everyone else seems to report that this method for getting root works.
Kingo root works (though some people don't like Kingo)
Also - always freeze OTA update app after you root, otherwise you'll lose root with every OTA update.
If you're expecting an OTA update, you can unfreeze the app, then use SuperSU survival mode, then let it update, and then turn off survival mode to get root back. But ofc it's too late for that now in your case.
reply
DrAzzy said:
Are you following these instructions? http://forum.xda-developers.com/showthread.php?t=2559715
Everyone else seems to report that this method for getting root works.
Kingo root works (though some people don't like Kingo)
Also - always freeze OTA update app after you root, otherwise you'll lose root with every OTA update.
If you're expecting an OTA update, you can unfreeze the app, then use SuperSU survival mode, then let it update, and then turn off survival mode to get root back. But ofc it's too late for that now in your case.
Click to expand...
Click to collapse
im not doing anything yet i don't want to brick the phone but in answer to your ? yes i want to try kingo
but there is a new version of kingo where you just let it run will that work also there is a video on it at you tube site
called kingo root note 3 should i do the fist kingo or the first one on the top of this thread
thanks in advance and thanks for the quick responce
I don't know the specifics of Kingo, I used the other method.
kingo one button
ok just did the new kingo for 4.3 with mj5 confirmed working
http://www.youtube.com/watch?v=hmc_QNJW68E
thanks again to all you guys who took time out to help me i am GREATLY APPRECIATIVE
AGAIN IT WORKS AND DOESN'T TRIP 0X1 IM STILL ON 0X0 NOW ROOTED AGAIN
its a great feeling now to stop the OTA UPDATES thanks guys
reply
alwayswatching said:
im not doing anything yet i don't want to brick the phone but in answer to your ? yes i want to try kingo
but there is a new version of kingo where you just let it run will that work also there is a video on it at you tube site
called kingo root note 3 should i do the fist kingo or the first one on the top of this thread
thanks in advance and thanks for the quick responce
Click to expand...
Click to collapse
ok just did the new kingo for 4.3 with mj5 confirmed working
http://www.youtube.com/watch?v=hmc_QNJW68E
thanks again to all you guys who took time out to help me i am GREATLY APPRECIATIVE
AGAIN IT WORKS AND DOESN'T TRIP 0X1 IM STILL ON 0X0 NOW ROOTED AGAIN
its a great feeling now to stop the OTA UPDATES thanks guys
Kingo is fine. The Heimdall and Odin one is a pain in the but and risky. Mostly for restoring. I used kingo and its just fine. If you mess up then you can go to that other link and restore with or without root.
reply
ZOOPidy said:
Kingo is fine. The Heimdall and Odin one is a pain in the but and risky. Mostly for restoring. I used kingo and its just fine. If you mess up then you can go to that other link and restore with or without root.
Click to expand...
Click to collapse
your right odin is a pain sometimes. kingo just worked first time boom one shot done
and i want to thank all the developers for there hard work and time for any program that allows us to do things we love to do with our phones
So i was Rooted on NB4 and after being unable to do the KK update OTA I manually installed it through recovery and it worked. After rebooting after the KK update was installed I still have the "Custom" padlock on the boot-animation and to my surprise the SuperUser app is still on my phone. I have tried to go into Application Manager to attempt to uninstall it but there is no uninstall option: Only the option to "force stop" and "turn off." If i try and open the SU app it just says "there's no SU binary installed. I've checked in Odin Mode and Knox is still 0x0, Binary say "Offiial" and Status is "Custom."
Anyone have any idea how to remove the "Custom" status and SU App?
Try doing a factory reset in recovery, and wiping the cache in recovery.
Tried that 2 times already. Also just went to set up ISIS wallet and I get an error message saying that "This phone has been rooted, ISIS is not supported"
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I am same situation and also want to know.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
It's almost acting as if the phone is rooted but there is no Root access or binary. I'm gonna attempt to install the update again and see what happens.
Reinstalled update and still SU is installed. I just want to get this thing back to stock
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Well when you root it installs certain files. When you update without unrooting, those files never get erased completely. Traces are left behind. Now that you've updated and don't have root access to remove them, you're stuck with them. You can try reverting back to mj5 (if it's possible because I don't know anyone tried yet) and updating again. Or you can patiently wait for root access to come along for the latest release.
2 routes that I see.
The XDA method of reverting back to MJ5 with Odin (but stop before rooting it)
or
megalomaniac's MJ5 for Safestrap. Install SS, install MJ5 to the stock slot. Reboot and you'll have to set the whole phone up again (AT&T Ready2Go will run), then you'll get the NB4 update almost immediately. If that won't load 4.4.2, at least it'll look like a stock NB4 (no "Custom" padlock) and Samsung (at BB) or AT&T will reflash it with their tool - which will let it accept the update to 4.4.2.
Here's what I did...
I went from the 4.4.2 leak back to MJ5 - no root - then accepted NB4 OTA. Then used Kingo 1.18 to root NB4. Explicitly copied all of the files from fix.zip and updated permissions.
Before accepting 4.4.2 OTA - go into SuperSu and go to options - fully uninstall root - then reboot.
Root will be gone - now proceed with 4.4.2 OTA (may need to set clock ahead or factory reset to trigger OTA download) and it installed w/o any issues.
Leak -> MJ5 stock/no root -> NB4 OTA -> root -> apply fix.zip -> Unroot -> 4.4.2 OTA
HTH - good luck!
Rukbat said:
2 routes that I see.
The XDA method of reverting back to MJ5 with Odin (but stop before rooting it)
or
megalomaniac's MJ5 for Safestrap. Install SS, install MJ5 to the stock slot. Reboot and you'll have to set the whole phone up again (AT&T Ready2Go will run), then you'll get the NB4 update almost immediately. If that won't load 4.4.2, at least it'll look like a stock NB4 (no "Custom" padlock) and Samsung (at BB) or AT&T will reflash it with their tool - which will let it accept the update to 4.4.2.
Click to expand...
Click to collapse
lehighkid said:
Here's what I did...
I went from the 4.4.2 leak back to MJ5 - no root - then accepted NB4 OTA. Then used Kingo 1.18 to root NB4. Explicitly copied all of the files from fix.zip and updated permissions.
Before accepting 4.4.2 OTA - go into SuperSu and go to options - fully uninstall root - then reboot.
Root will be gone - now proceed with 4.4.2 OTA (may need to set clock ahead or factory reset to trigger OTA download) and it installed w/o any issues.
Leak -> MJ5 stock/no root -> NB4 OTA -> root -> apply fix.zip -> Unroot -> 4.4.2 OTA
HTH - good luck!
Click to expand...
Click to collapse
What fix are you referring to? I'm on stock rooted NB4 with safe strap but I am thinking about going back to stock rom slot. Un installing safestrap. Then using SU to remove root. Then use king to u root after SU is gone. What do you think about that?
Sent from my SAMSUNG-SM-N900A using Tapatalk
If you un-root with superuser, you can't un-root with kingo too. Because you already un-rooted.
why are you giving up root?
I see so many people trying to go to stock KK but they will lose root forever - no? Why not use Knoxraid and have both (unless you are selling / taking it back)? Sorry - I'm a bit confused by this mass exodus from root ...
I am referring to the fix posted here: http://forum.xda-developers.com/showthread.php?t=2699321
It contains some system files to replace and a script.
I did not use SafeStrap at all.
rawb123456 said:
What fix are you referring to? I'm on stock rooted NB4 with safe strap but I am thinking about going back to stock rom slot. Un installing safestrap. Then using SU to remove root. Then use king to u root after SU is gone. What do you think about that?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Dont use the mj5 restore if you're on official 4.4.2 im pretty sure it wont work ( you may brick)
Sent from my GT-I9300 using xda app-developers app
Hey everyone. I am not new at rooting phones but this appears to be the one phone that is giving me issues.
My note 4 is telus, was n910w
installed this rom:
http://forum.xda-developers.com/note-4-tmobile/development/rom-vision-x-n4-intl-t2943448
working beautifully thus far but I cant seem to root....
I have tripped KNOX 5 times so far trying to do it, each time it appears my phone is not rooted as titanium cannot verify SU, and aswell I have a root checker which tells me it is not rooted.
I have tried several versions of ODIN, and cf auto root n910t, AND V.
Do I maybe have to reinstall my rom? Or is there something I am missing because this is frustrating me....
Is there something I am doing wrong? Superuser IS on my phone, but its not doing anything but being there.... Please any kind of help would be appreciated as I am stumped.
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Framaroot
Sent from my Trident-A1 using XDA Free mobile app
neofreek01 said:
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Click to expand...
Click to collapse
This worked, I am a dummy lol
Thanks alot!
Glad I could help
Glad you got it worked out but note that you can only ever trip Knox once. Once it's tripped it's tripped, so don't worry about it.
neofreek01 said:
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Click to expand...
Click to collapse
I had lost root after flashing the PopRocks ROM. Couldn't figure it out and stumbled across this post. Now it works perfectly. Thanks! :good:
I just picked up a used T817T yesterday. I was able to root it with Kingroot. I then found out that I lose root after a reboot. Even worse, without enabling the developer options and enabling the OEM unlock, it would no longer boot. I had to reflash the stock ROM with ODIN to recover.
I purchased and installed SuperSu Me-Pro and that replaced the Kingroot SU with SuperSu. Now I can reboot without losing root.
I'm being prompted to install an update T817TUVS2APB1/T817TTMB2APB1/T817TUVS2APB1. If I install this update, will I lose root? If I install it, can I still root with other methods?
I still have the stock recovery.
I'm currently on T817TUVS2AOL1.
I decided to roll the dice and try the update. I got a message that the software on my device was altered in an unapproved way and that it would not update. At least the nagging icon on the top of the screen is now gone.
DonS said:
I decided to roll the dice and try the update. I got a message that the software on my device was altered in an unapproved way and that it would not update. At least the nagging icon on the top of the screen is now gone.
Click to expand...
Click to collapse
Install it with Flashfire.
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!