Related
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 guys. I've been holding off on KK until the root came out so it sounds like I can finally make the swap. My questions are more concerned with going from 4.3 MJ5 to 4.4.2. Currently I have my MJ5 rooted, along with apps like TB, Greenify, Xposed, etc.
If I do the OTA (currently disabled in TB) I assume it will upgrade to KK, keep all my apps, and also take away root. However, what about the fact xposed is installed without root? Or say the frozen apps I have in TB? What happens to them? Will I need to first uninstall Xposed and TB before installing the OTA or can I safely move to an unrooted KK before applying the new towelroot?
Thanks
First of all if your on 4.3 mj5 you have to update to 4.3 nb4. Then again you will have to update to 4.4.2 nc2.
The first scenario is updating to nb4. If your rooted you will lose it, but you'll update. The problem starts when you want to update to nb4. If you have deleted any system apps in mj5 your update will probably fail. If it works superuser will remain installed but useless. Same with xposed etc... so then you can re-root with towellroot. You'll need to uninstall superuser and reinstall superuser version 1.99 because the previous version won't work. Then your xposed and whatnot will need to be updated but still work.
If your update to nc2 fails you need to find the thread in the general section that restores mj5. Then again update to nb4, and again to nc2. Then root and reinstall xposed etc.....
If I were you I'd restore any frozen or uninstalled apps with titanium. Uninstall any apps requiring root like xposed etc... Then un-root mj5 and pray you update all the way thru.
440bro said:
First of all if your on 4.3 mj5 you have to update to 4.3 nb4. Then again you will have to update to 4.4.2 nc2.
The first scenario is updating to nb4. If your rooted you will lose it, but you'll update. The problem starts when you want to update to nb4. If you have deleted any system apps in mj5 your update will probably fail. If it works superuser will remain installed but useless. Same with xposed etc... so then you can re-root with towellroot. You'll need to uninstall superuser and reinstall superuser version 1.99 because the previous version won't work. Then your xposed and whatnot will need to be updated but still work.
If your update to nc2 fails you need to find the thread in the general section that restores mj5. Then again update to nb4, and again to nc2. Then root and reinstall xposed etc.....
If I were you I'd restore any frozen or uninstalled apps with titanium. Uninstall any apps requiring root like xposed etc... Then un-root mj5 and pray you update all the way thru.
Click to expand...
Click to collapse
I was afraid you were going to say that. I guess it wont be the end of the world but will definitely be time consuming. So if I restore all hidden apps (didnt delete any), unroot, etc, once I turn the OTA services back on, which should it download? Or can I manually flash a version from somewhere on the net?
Also there is no way to avoid the nb4 route and go right to nb2? Thanks
http://forum.xda-developers.com/showthread.php?t=2786043
Sent from my SM-N900A using Tapatalk
thanks. is there a file for nb4 though or will the OTA bring me there? I believe I have to do MJ5 to NB4 to NC2?
Kingo has an unroot option might try unfreezing all your apps and removing all your root apps and settings then running unroot I'm really curious if this will work.
My wife's phone is rooted mj5 and I'd like to update but my wife won't let me so I've been wondering the best way to not lose all my settings
Sent from my XT907 using XDA Free mobile app
When I purchased my Droid Maxx it was running 4.2.2 and I used the PIE exploit to root it. At the time, I didn't realize that allowing the 4.4.4 OTA update would completely frag the root so I took it. Now, on 4.4.4 I of course have very buggy and inconsistent root access. So, I decided to just unroot and forget about it for this phone. To that end, I ran a full unroot from SuperSU and the app disappeared. Great...until I rebooted and it came back. I went back into the app, disabled it via the app settings, full unroot again, and again the app reappears on reboot. I can't delete the apk from the System folder because even with SuperSU enabled it won't grant me write access (see above: root fragged). So what the hell am I supposed to do? The phone is essentially unrooted, but on every reboot, regardless of unroot attempts, SuperSU reinstalls itself.
Any ideas on how to get rid of it?
Either root it properly and use that to remove it, or reflash your full stock firmware.
I downgraded my Xperia M2 dual d2302 to 4.3 and rooted with towelroot and then flash 4.4.4 followed by flashtool force towelroot using super su. This would uninstall super su on my phone and install its own super su binaries and busybox content. The super su pro would however, remain installed. So, I would have to redownload the super su and as soon as i would open it, it would ask for binary update and then ask for reboot. I would just follow the prompt without question. As soon as it reboots,though the root would be there but sd card and system rewriteable will be gone and there is no way to make my system rewriteable without flashtool reflashing back to 4.3 and following the long procedure. I till now, would blame kitkat and sony for that. This continued for over 8 days till I realised that the real culprit was not sony or kitkat but super su binary update followed by reboot. This is highly anoying. What is the point of root if system or sd card writing is not allowed? For now, I am living with super su by canceling the binary update everytime I open it. I have OCD and I find it highly annoying. I tried searching for an option to cancel auto search for updates bur in vain. My phone works just fine without update. I need no updates and need a way to stop super su asking for update everytime. Please suggest me something.
I have now discovered that even if I cancel binary updates, supersu auto updates causing the same problem. So, now I have decided to live without Supersu as supersu is not needed for root. I have an unlimited root access for all my apps which have root permission now and to add icing to the cake, my bootloader is locked. If anyone else is searching for a way to make Sony Xperia M2 dual 4.4.4 system writebale without unlocking bootloader, just follow:
LOCKED BOOTLOADER
1. Downgrade to JB, Root your Phone using Towel Root in Jelly Bean
2. Update via OTA to KK 4.4.2 or KK 4.4.4 whatever you need (4.4.4 is recommended)
3. In this process, don't try to install or uninstall anything
4. Wait for booting finish
5. Install latest SuperSU from Play Store
6. Open Flashtool in PC
7. Connect your phone to PC
8. Now flashtool will describe your phone information, then click Root Tab in top, after that choose force root by TowelRoot
And after this, do not install supersu or any other root control app. Just let your phone be as such without updating binaries or anything and you will have root. You will have unrestricted root on Xperia M2 dual, Enjoy and remember not to install supersu, kingsu, cm superuser or any similar app.
I was thinking to help you, but then i was worried if something else goes wrong, then you will blame me, just like you blame super su.
Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt
gauthamraob said:
Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt
Click to expand...
Click to collapse
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
---------- Post added at 02:42 PM ---------- Previous post was at 02:31 PM ----------
BTW, tell us what do you need on your device that will make you feel better. (About the superuser @ root thing of course)
NeoLogY said:
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
Click to expand...
Click to collapse
No, I am already having root . I have integrated most of the updates to my system app to my sys/app folder through lucky patcher and have installed the modded play store . I can even edit and delete system files in "ES explorer" file manager and stop items from startup using "all-in-one-toolbox" boot manager. I have an older version of su binaries which was installed automatically into my phone by "flashtool by androxide" using the force root mode using towel root :good: . But the supersu app was not installed and if the app existed before rooting, flashtool would uninstall it and also replace the new su binaries with an older version ! So, I already have full root access without the supersu app.
As far as i know, supersu is not needed for root. It is only a gatekeeper app which restricts the unlimited access of root to any app by making the apps that need root to ask for permission first. Without supersu installed, root apps get root access without asking permission provided binaries (any version) are already present. Also, for normal people who don't know or can't install binaries directly, they rely on apps like supersu, CM etc for installing the binaries. But once the binaries are installed, the supersu app is no longer needed for root (except in cases of OTA updates or updation of binary to a newer version) but instead works as a security guard for root.
Edit:
What I want is a way to make supersu submissive and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like.
What I want is a way to make supersu submissive to my command and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like and must not be done
Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?
NeoLogY said:
Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?
Click to expand...
Click to collapse
At present I am using my phone without supersu as I will have to spend a lot of time downgrading to 4.3 and then rooting followed by painfully slow 4 OTAs in succession (there is no single direct OTA from 4.3 to 4.4.4 on Xperia M2 dual, unfortunately :crying: ) followed by installation of all my apps. I too wish there was a fix for supersu but the time I'll have to spend on that will be enormous and also considering that in this september my phone will mostly get lollipop 5.1, the 4.4.4 woes will soon be history.
Also, I want to mention that I haven't unlocked my bootloader yet. If I unlock my bootloader, all these problems with supersu will vanish. The actual difficulty I am facing is because there is no single post on the internet that says how to get system to be rewriteable without unlocking bootloader in Xperia M2 devices. Every post I have read of only has people with unlocked bootloader saying what to do and people with locked bootloader complaining that they aren't able to make their system rewriteable. I am probably one of those rare people who managed to get complete root with locked bootloader and hence facing the issue of lack of peer help.
Anyways, I really appreciate your interest shown in helping me. If I ever have to update my binaries in the future I will definitely take a log of it and pm it to you in case similar situation arises.
Cheers.
Same thanks to you. Actually, i think it is better to put the log here, as more hands and mind will be able to reach it, meaning higher percentage on discovering any hidden in the log. You are right about the lock bootloader, even until now i still unable to manage to truely understand about bootloader, as i didn't have any device with it to get inhand with the system. As always, i do appreciate any kinda knowledge exchange. Thanks in any way.
That's exactly why your system is read only and you can't move apps/data to sd ect without supersu installed and the binaries updated and Sony ric killed you don't have full root r/w access to system. The way you have rooted your device is the same way I did mine it's the easiest way there is if you can't get it right doing that way then maybe you should put your Phone back to stock. Flash jb, root with towelroot apk(at this point do not update anything), now update over the air to 4.4.2 then again to 4.4.4(again update nothing but phone)root will stick after each update. Download supersu connect your phone to flashtool and click on the force root tab(kills Sony ric installs supersu binaries and busybox) making system r/w
Search on here for the m2 forum if you still have problems
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
Hi, I recently rooted my Z3c using KingRoot. I ten installed custom Rom: SLiM ROM 4.9. Works great, but now I found out Kingroot is very untrustworthy. How do I remove/replace kingroot without loosing root?
I rooted as per these instructions:
whattechsays.com/root-xperia-z2-z3-lollipop
So I have SuperSU installed, but KingRoot does not appear in apps list - so no option to uninstall. I can see kingroot folder in internal memory. Is deleting this sufficient to remove kingroot and any potential back-door?
I am new to rooting, so please explain simply if you can.
Many thanks.
Better remove Kingroot, and unroot all at once. You have Slimrom installed so I'm assuming your bootloader is unlocked so simply flash SuperSu Zip via recovery to get back root.
Kingroot is unreliable and shady when it comes to rooting devices in fact its not even endorsed here in Xda
Revontheus said:
Better remove Kingroot, and unroot all at once. You have Slimrom installed so I'm assuming your bootloader is unlocked so simply flash SuperSu Zip via recovery to get back root.
Kingroot is unreliable and shady when it comes to rooting devices in fact its not even endorsed here in Xda
Click to expand...
Click to collapse
I already have SuperSU installed already. And when I run rootcheck it says SuperSU has root. I have ' uninstalled' Kingroot, however kingroot folder/files remain on internal memory and I assume it could still be active and hiding it's process?
Sent from my D5833 using Tapatalk
Came across this thread from Google, but since it doesn't look like you really got an answer, here goes.
When you flashed Slim ROM, you would have replaced the system partition where Kingroot was installed, meaning it is no longer there at all.
The files left on the internal memory would have been written by Kingroot before and can just be deleted.
Frenik said:
Came across this thread from Google, but since it doesn't look like you really got an answer, here goes.
When you flashed Slim ROM, you would have replaced the system partition where Kingroot was installed, meaning it is no longer there at all.
The files left on the internal memory would have been written by Kingroot before and can just be deleted.
Click to expand...
Click to collapse
Oh dear, another Kingroot user stuck, how many warnings about Kingroot need to be posted on the threads before people listen.
Personally, knowing about what Kingroot does and the information it sends to China, I would wipe my phone and start from scratch.
There is a good guide written by bilboa1, which is very easy to follow.
Frenik is right, if you flash a rom, then the system should get wiped also. Just make sure you wipe data as well as dalvik/cache then you might end up with a Slim rom with SuperSU.
http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/
I used the version 2.4 and worked like a charm
Although as above... even though i have stepped on the same rake as you... don't use KingsRoot... there probably is a fake copy of my phone somewhere in china thanks to that...
"use SuperSu Me" app
Sent from my D5833 using XDA-Developers mobile app
Hi fellas. I write ehre in order to not open a new thread. I recently bought one of this little beasts. I'm running 23.4.A.1.264 (stock in phone), Android 5.1.1. I've succesfully rooted it with king root 4.9.5. I've tried to change it to Supersu without success. I've tried supersu me, the script to remove kingroot to supersu from ver 1.8 to 2.4 and always lose root permissions. Could someone tell me what the f*** I am doing wrong?