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.
Related
Hello everyone. I know I'm a noob, but am hoping I can get some help anyway. Tried searching and not too many people are having the same problem, so I started a new thread.
Anyway, I used the one click root found in this thread:
http://forum.xda-developers.com/showthread.php?t=1348557
( I tried to post in that thread, but can't since I don't have 10 posts )
I'm new to hacking and I'll be honest. I only wanted to root my phone so I could use wireless tether, and then use Titanium Backup to freeze a lot of the bloatware on the phone. I have no desire to install a different ROM. I'm happy with the one it has, and happy to take the updates Verizon pushes. Everything was good until the latest update came through. When it downloaded, and rebooted, instead of updating, it booted in clockwork mod recovery. No matter what I tried, I couldn't get the update to go through.
So I settled on never updating again and froze the updater to prevent my phone from trying to update and going to CMR at random times. About 4 days later, my bluetooth quit working. Couldn't figure out why. Thought I was going to have to send it in for warranty work, so I tried to undo all the mods. I unfroze everything, and then hit the one click unroot button. It said it worked. Problem is, superuser is still installed with no way to uninstall.
My first question is this: How do I get superuser gone so my phone can be back to factory so they'll never know it was rooted?
Next I tried to go ahead and get the update since the unrooting process was supposed to have reinstalled stock recovery. Well, it didn't. I still ended up booting up into CMR again. STILL can't update even after unrooting. Double checked, and wireless tether and Titanium backup both say "no root". On a whim, I try the blue tooth and guess what. It worked. May not need to send the phone off for warranty work after all.
So my second question is this: Would freezing the updater cause the blue tooth to stop working? If so, how can I either keep it working or stop the updates without freezing the updater? It's like I have to choose between having blue tooth or having my phone randomly boot into CMR whenever it tries to update.
Third question, pertaining specifically to the one click root I linked to above: How can I get rid of the CMR? Is it possible to root the phone without installing CMR? If I can get it unrooted back to factory ( without superuser or CMR ), how can I root it again so that it doesn't install CMR and keeps the stock one?
I know this is a lot of question and I'm a noob, but I'm a noob willing to learn. If this problem has been encountered before, I apologize in advnace for not finding the appropriate thread. I tried.
updater app
Yes freezing the software update app will cause your Bluetooth to stop working. I used a app called Gemini app manager to go change the permissions of the software update app so it did not have any permissions to do anything. I have not been bothered with update prompts since.
NewDroidXUser said:
My first question is this: How do I get superuser gone so my phone can be back to factory so they'll never know it was rooted?
Click to expand...
Click to collapse
There's no need. MTMichaelson has come up with a easy way to keep your phone rooted during the upgrade from ZV7 to ZV8.
NewDroidXUser said:
So my second question is this: Would freezing the updater cause the blue tooth to stop working? If so, how can I either keep it working or stop the updates without freezing the updater? It's like I have to choose between having blue tooth or having my phone randomly boot into CMR whenever it tries to update.
Click to expand...
Click to collapse
Yes it will. Several people have reported this in different threads. I'm not sure of a way around this, but I think others might have a way around it. If you follow MT's method to keep root during the upgrade, you want have to worry about it!
NewDroidXUser said:
Third question, pertaining specifically to the one click root I linked to above: How can I get rid of the CMR? Is it possible to root the phone without installing CMR? If I can get it unrooted back to factory ( without superuser or CMR ), how can I root it again so that it doesn't install CMR and keeps the stock one?
Click to expand...
Click to collapse
There's no need to do this either since you can keep root and upgrade.
Here's what you need to do.
1) Go here and root your phone again.
2) Go here to upgrade to ZV8 while keeping root. There's also a method for reinstalling CWM as the upgrade will remove it.
This will: keep your root, get you upgraded, fix your bluetooth and keep CWM.
Good luck!
brad6360 said:
There's no need. MTMichaelson has come up with a easy way to keep your phone rooted during the upgrade from ZV7 to ZV8.
Yes it will. Several people have reported this in different threads. I'm not sure of a way around this, but I think others might have a way around it. If you follow MT's method to keep root during the upgrade, you want have to worry about it!
There's no need to do this either since you can keep root and upgrade.
Here's what you need to do.
1) Go here and root your phone again.
2) Go here to upgrade to ZV8 while keeping root. There's also a method for reinstalling CWM as the upgrade will remove it.
This will: keep your root, get you upgraded, fix your bluetooth and keep CWM.
Good luck!
Click to expand...
Click to collapse
Ah, thanks. I'll post again to update how that went. Though, I'd like to keep the stock recovery. I'll try to do it without CWM.
latenighter49 said:
Yes freezing the software update app will cause your Bluetooth to stop working. I used a app called Gemini app manager to go change the permissions of the software update app so it did not have any permissions to do anything. I have not been bothered with update prompts since.
Click to expand...
Click to collapse
How did you change permissions in Gemini? I turned off all the autorun features and was able to get Bluetooth working but I didn't see anything about permissions in the settings. I could have missed it though being at work and all. Will turning off all the autorun features of the Software Update app stop it from trying to download the update in the middle of the night when I'm not looking like it sounds like it should?
In gemeni select block app. It's the same as freezing in titanium backup.
Sent from my VS910 4G using XDA
I have my D4 with the previous update, Gingerbread 2.3.6 (...219). It is rooted and I have a few of the pre-loaded apps frozen.
What should I do before allowing the new OTA update to ICS?
Should I leave it rooted? Should I "hide" root? Should I unroot (how)? Does it matter?
Should I unfreeze the apps? Leave them frozen? Doesn't matter because they will all be replaced/overwritten?
Should I uninstall Superuser and Busybox?
After the OTA update is complete, will I have to re-root? Is this what I should use, Droid 4 Utility Updated ?
Any other hints, suggestions, cautions, or problems from those who already did the official ICS update?
If you installed and used safestrap before, you will need to switch back to the original (unsafe) system, uninstall it, and restore the original contents of /preinstall. You should unroot after that. You can save root with OTA rootkeeper. Make sure you have the updated su binary, since the old binary won't run on ICS.
Sent from my DROID4 using Tapatalk
I generally find it easier to just flash the system and preinstall images from the FXZ with fastboot rather than trying to undo any changes I have made and then the update always works.
Also, preserving root is unnecessary because the RazrEdge ICS exploit works fine to root any of the updates.
If you use OTARootkeeper be sure to Temp Unroot first or the update will fail.
You will need to enable all the apps in /system and revert any changes you made in /system. The update scans /system and compares it to things within the update.
Sent from my DROID4 using xda premium
?
does anyone have all the original apps? i re-installed some i guess for the last ota update after i failed many times and finally got it to work. now i have the soak test and it keeps failing, so i'm assuming i'm missing something. i've removed everything that requires root just to be sure and it still fails.
I'm stock rooted 6.13.215.XT894 and I can't seem to get the 219 update to apply. Forum search didn't seem to help. I've tried Voodoo Rootkeeper, but it doesn't seem to help. Nothing else on here (no Titanium, Safestrap, etc.). Am I crazy?
rorytmeadows said:
I'm stock rooted 6.13.215.XT894 and I can't seem to get the 219 update to apply. Forum search didn't seem to help. I've tried Voodoo Rootkeeper, but it doesn't seem to help. Nothing else on here (no Titanium, Safestrap, etc.). Am I crazy?
Click to expand...
Click to collapse
Isn't 6.13.219 the Gingerbread update from April? I did the .215 to .219 back then, leaving my phone rooted and many apps deleted (not frozen). The OTA update went fine, though when done, I wasn't rooted anymore and all the pre-loaded apps were back.
I don't know if that OTA update going fine was just luck, which is why I am asking here about what to do before the OTA ICS update, from those who might share their ICS update experience (good or bad).
My ICS update went good, took a very long time though, and almost killed the battery.
First I used OTArootkeeper to unroot the phone, then installed the update. The update rebooted, and installed, rebooted again, and did a nother install, then said upgrading apps, at this point it took near 2hours, If you have a lot of apps, make sure to have the phone plugged in. I thought my phone was bricked at this point, cause the progress display stopped after a while. but after 2hours of that, it finished booting and was fine. Used otarootkeeper again, and regained root, and my phone is back to normal like nothing happened.
I really didn't play with the rom much, except to root it. Lots of new annoying bloatware though, have to see if they are just installed apps, or if they actually run.
Preinstall Files?
qe 1/1
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Deleting Facebook cache folder...
Verifying Current System...
assert failed: apply_patch_check("/preinstall/Knowyourdevice/Motorola_XT894_Batterysave.3gp", "71ce34b3b53ae3a2d9bbfb9ce3ba4452d73ea98", "4e7e24a6817763a5539e569c9d7e15c6e430a27b")
E:Error in /cache/Blur_version.6.13.219.XT894.Verizon.en.US.zip
(status 7)
Installation Aborted
- Looks like I need to replace the preinstall files? I dunno for sure how. I do have an image. Trying to Apply the soak to GB
After compulsively re trying the software update button I received a notification that said 217 was available. (I guess I somehow got into the soak test). Anyway, I downloaded it last night (officially) as well as Voodoo OTA Root keeper from the market. FYI: I am only rooted, no roms or safestrap. I went into superuser and made sure I had the current su binary. Back in Voodoo, "Protect root" - > "Temp Un- root". This can be tested by opening a root app and trying to use its root function, only to be denied. Then I installed the update and let it run its course. After I was running 4.0.4, and all my apps were updated from the market, I went into Voodoo and pressed "Restore root".
Now I am running stock ics on my rooted droid 4!
Sent from my DROID4 using xda premium
got it .0
i got it....
I followed some directions to return to stock and flash in a copy of the original system via adp.
worked great. Now I am in ICS!
Hello!
Already got iHackers 2.0 + .290-kernel running (complete installed system) on rooted Z1 (C6903)!
Wanted to grant some apps SuperSu-permission and wanted to check within SuperSu which apps already got granted SuperSu-permissions. SuperSu showed up a message: binary must be updated! So I checked update normal way but install/download failed!
So I've searched www and found that someone mentioned to another guy (got same problem) to download Chainfire 1.51-flashable-SuperSu and this guy mentioned: flash in recovery and do update later on!
I tried and now ROOT HAS GONE!
Is it possible to use KingoRoot now again to get Root-permission back without loosing something (data, dual-recovery, xposed-stuff which is already installed, ...)?
How am i able to get binary for SuperSu up-2-date?
Thanks,
DES75
DESASTER75 said:
Hello!
Already got iHackers 2.0 + .290-kernel running (complete installed system) on rooted Z1 (C6903)!
Wanted to grant some apps SuperSu-permission and wanted to check within SuperSu which apps already got granted SuperSu-permissions. SuperSu showed up a message: binary must be updated! So I checked update normal way but install/download failed!
So I've searched www and found that someone mentioned to another guy (got same problem) to download Chainfire 1.51-flashable-SuperSu and this guy mentioned: flash in recovery and do update later on!
I tried and now ROOT HAS GONE!
Is it possible to use KingoRoot now again to get Root-permission back without loosing something (data, dual-recovery, xposed-stuff which is already installed, ...)?
How am i able to get binary for SuperSu up-2-date?
Thanks,
DES75
Click to expand...
Click to collapse
I got the pro version of SuperSu which fixed that binary problem for me.. As always make a back up of everything just in case. As far as I'm aware you do not have to factory reset or wipe data to root with KingoRoot.
Try it, otherwise I'd personally just go through the procedure again (and wipe data if needed) to get the root back. If you make a back up, it won't be a problem. Just a little time.
Hi!
Do have Pro-Version, too, but SU-Binary will not be updated! So I do need a way to get that SU-Binary updated without loosing Root, ...!
Thx,
DES75
DESASTER75 said:
Hi!
Do have Pro-Version, too, but SU-Binary will not be updated! So I do need a way to get that SU-Binary updated without loosing Root, ...!
Thx,
DES75
Click to expand...
Click to collapse
Strange, I had exactly the same message. Firstly have you got Busybox Installed? Try installing this then updating again.
I'm researching it, a lot of other threads saying you may need to reroot to get it working, but try the above first.
This may help http://forum.xda-developers.com/showthread.php?t=2059440
http://forum.xda-developers.com/showthread.php?t=1847939
P.s try and use the search button. :angel:
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
newuzer1 said:
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
Click to expand...
Click to collapse
Do you have TWRP installed? If so try to get it to reflash the binaries again.
mjones73 said:
Do you have TWRP installed? If so try to get it to reflash the binaries again.
Click to expand...
Click to collapse
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
newuzer1 said:
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
Click to expand...
Click to collapse
I would assume not installing the SuperSU binary updates correctly broke SuperSU. You didn't lose root per say, you broke SuperSU which apps need to be able to run as root.
I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..
I have the same problem?? Did you get any answer from any body? Do I have to re root again?
Just flash super su in recovery. Same thing happened to me and i don't know what is the cause of the problem
Roamin64 said:
I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..
Click to expand...
Click to collapse
Im having similar issues. 6.0.1 on my tmo note 5 rooted perfectly using Max Lee's method. However as soon as I rooted and transfered all my data back I did a nandroid backup. Happen to wipe my phone the other night and and restored the nandroid backup and as soon as it restored I lost root. Happens everytime I restore even a newer nandroid in twrp. Never had this happen on any root method on any note.
WTF..
It's happened again this morning.. Root dissapeared by itself. The only recent thing I can think I did , was buying a game (The cave) from play store last night.
Any way to identify what is removing SU ?
Flash SuperSU 2.74 and delete 'SecurityLogAgent'
I also lost root
I have a Samsung Galaxy Note 5 on the Sprint Network. I just now noticed that my applications that require root access, including Titanium Backup are reporting that my device is no longer rooted. Weird. This has never happened in the past when I had rooted Samsung phones. I will re-flash the Super User file as instructed in this thread and see if that resolves the issue.
---------- Post added at 03:01 AM ---------- Previous post was at 02:32 AM ----------
Per your insstuctions, I reflashed SuperSU 2.74 using TWRP. Then once my Note 5 rebooted, I launched Titanium Backup and found "SecurityLogAgent" and uninstalled it. However, in order for me to access TWRP I have to reinstall it using ODIN and immediately after I get the green "PASS" light in ODIN I have to quickly do the 'three finger' button press to launch TWRP. Weird....
Anyway, so far so good.
Thank you.
Battlehero said:
Flash SuperSU 2.74 and delete 'SecurityLogAgent'
Click to expand...
Click to collapse
Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.
Bosbouer said:
Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.
Click to expand...
Click to collapse
Yes, follow Battlehero's instructions (post #6) worked fine for me.
Roamin64 said:
Yes, follow Battlehero's instructions (post #6) worked fine for me.
Click to expand...
Click to collapse
Thanks that worked to a certain extent. Titanium requesting root privileges for backup would still pop up as failed. Checking root would show as unrooted. The Superuser app was updated on the 5th of July 2016. Since I applied that update, i have not lost root on any of my devices.