Here is what happened: i had root access on v10d and my phone was getting too hot and WiFi didn't turn off in sleep. So I decided to factory reset and thought that I didn't have root after that. Then I updated to v10f using OTA and I was using an app that needed root. It was apex launcher. And I was able to add widgets from the app drawer. Then I installed superuser and root checker and my phone was rooted. Is that normal???
muzamal said:
Here is what happened: i had root access on v10d and my phone was getting too hot and WiFi didn't turn off in sleep. So I decided to factory reset and thought that I didn't have root after that. Then I updated to v10f using OTA and I was using an app that needed root. It was apex launcher. And I was able to add widgets from the app drawer. Then I installed superuser and root checker and my phone was rooted. Is that normal???
Click to expand...
Click to collapse
As the su binary is stored in /system, it is not affected by a factory reset (which wipes the /data partition. And the OTA seems to keep the root, as it has been mentioned in the firmware thread.
Related
I had to Factory reset to remove the primary account on my Tab (SPH-p100). Was rooted with Z4root.
The Superuser Permissions app disappeared and it appears my tab is no longer rooted. Root checker confirms this
I have tried Unroot and Permanent Root with Z4Root but they both hang running exploit to obtain root access. I have tried this multiple times and the programme either quits whilst running or just will not progress past phase 1
I want to reroot but it looks like the root apk will not unroot or root the device.
Any ideas on how to fix this?
try super one click root 1.9
I have a rooted Note.
And about 2 weeks ago I checked and found an update available to 2.6.35.7-N7000XXLA4-CL886827 [email protected]#2 GINGERBREAD.XXLA4
I have seen a couple of interface changes, and overall it is nice...
Afterwards I did find that some of the apps stopped working:
gmail
Draw something.
I fixed it by updateing/ deleteing re-downloading them.. And it worked fine afterwards...
However my battery ran down and after I started up again the apps was once again broken
What I did notice is that some updates for apps I have already "applied" is once again available on the play store.
I am really looking forward to the ICS update and was planning to do a factory reset before that. However looking at the version I received (I really check regularly) this seems to be a "oldish" update Jan 2012. So I am not optimistic that even when it becomes available it will be available in South Africa.
What I want to know is if this a known issue? and is there a fix? Or would I just be advised to backup and bite the bullet and factory reset
savagezaing said:
I have a rooted Note.
~~~~~~
What I want to know is if this a known issue? and is there a fix? Or would I just be advised to backup and bite the bullet and factory reset
Click to expand...
Click to collapse
If you upgraded your phone OTA, you lost your root, which explains the crashes!
I did do it OTA, however I still have root, Superuser still works and I installed Titanium backup and it also received su access.
I have check and found that applications installed after the upgrade seems to break after the reboot.
Should I will try to re-root the phone?
savagezaing said:
I did do it OTA, however I still have root, Superuser still works and I installed Titanium backup and it also received su access.
I have check and found that applications installed after the upgrade seems to break after the reboot.
Should I will try to re-root the phone?
Click to expand...
Click to collapse
Just try if you could write on to /system folder. If you can't then re-root and check.
But if you have upgraded, the chances are that you may not be able to re-root with you current configuration, you will have to downgrade to a "rootable" ROM.
But never upgrade OTA when you are rooted, you will lose the root and will generally have issues.
But if you have root access, try wiping cache and see if that helps!
I cannot write to the /system folder, however I remember I had problems before the update already so not sure if it is a definitive proof. When using terminal emulator I can call "su" this is how it tested rooted previously.
I did try to re-root the phone with no success.
So how do I clear the cache???
Would it work if I reset to factory? What gets "cleared" when you do the reset?
All your apps and user data. Which include wifi settings, contacts, logs, etc
you cannot reroot with your configuration. you need to downgrade, root your phone and update via CWM, not OTA.
How Do I downgrade?? and what is CWM?
savagezaing said:
How Do I downgrade?? and what is CWM?
Click to expand...
Click to collapse
Here's a brief guide to downgrading and rooting I wrote a while ago:
http://forum.xda-developers.com/showpost.php?p=23606842&postcount=12
CWM = ClockWorkMod Recovery --> do a forum search to find out what it is.
So I just rooted my Motorola Droid since my contract expired with Verizon. I'm using this phone as practice so I'm not afraid to brick it. After using the superoneclick method to root the phone, it installs superuser fine, and I can access the app. I installed ROM manager for obvious reasons and every time I try to flash a recovery, it freezes at the point where the app is supposed to ask me for superuser permissions. I tried using titanium backup and it is not asking for permissions either. I then go into the superuser app and did the "Tap to check for updates" under the Su binary v3.0.3 label. The update fails every time on the "Gaining root access..." step. I tried unrooting and rerooting and everything. I went into the superuser settings and set the automatic response to "allow" and am still getting nothing. I have also force closed superuser, and then cleared all the data before restarting.
Am I just missing something important? Or am I just unlucky to the point where nothing I ever try in regards to rooting works the way it is supposed to?
furlessxp said:
So I just rooted my Motorola Droid since my contract expired with Verizon. I'm using this phone as practice so I'm not afraid to brick it. After using the superoneclick method to root the phone, it installs superuser fine, and I can access the app. I installed ROM manager for obvious reasons and every time I try to flash a recovery, it freezes at the point where the app is supposed to ask me for superuser permissions. I tried using titanium backup and it is not asking for permissions either. I then go into the superuser app and did the "Tap to check for updates" under the Su binary v3.0.3 label. The update fails every time on the "Gaining root access..." step. I tried unrooting and rerooting and everything. I went into the superuser settings and set the automatic response to "allow" and am still getting nothing. I have also force closed superuser, and then cleared all the data before restarting.
Am I just missing something important? Or am I just unlucky to the point where nothing I ever try in regards to rooting works the way it is supposed to?
Click to expand...
Click to collapse
Have you tried updating the superuser app itself? not only the su binary
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
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.