Everytime i reboot from recovery, i get this error message. I can either choose, yes fix root, or no reboot now. On 4.3 pacman, tried flashing supersu 1.65, tried updating Superuser binaries through recovery with SuperSU, and im still getting this. Any other way to fix this?
Say no. You won't lose root. I can't remember why that shows up, but just choose no.
Sent from my Nexus 4 using xda app-developers app
When i updated to 4.3 i started getting this. So i unrooted and re rooted, and the error was gone. Then titanium backup started telling me my su binaries needed to be updated, so i updated with supersu pro, and the error message came back. I know it seems harmless, but one in a while i have issues with apps that require root. Nothing major, just curious if theres a way to fix it.
Im curious, what happens if you click yes?
sinndissension said:
Im curious, what happens if you click yes?
Click to expand...
Click to collapse
it happened to me with stock rom. pressed yes, pressed no, unroot and root again nothing. after that i flashed twrp recovery and problem solved. to tell the truth twrp is better for me...
Related
Alright so I'm tired of the notification for the 4.2.1 update sitting in my notification bar. I rooted my phone right after I got it and did the very first OTA. I am running the latest version of CWM that I manually flashed. I thought I saw somewhere that ClockworkMod automatically installs OTA's, and keeps root when it's done? But every time I reboot to try to OTA, it doesn't work. It shows a little 3D Android with something spinning in it's stomach. CWM then pops up with a menu asking if I would like to install an untrusted zip (I'm assuming Google does something weird to the signature or something). But when I click to proceed, it just aborts after trying to flash.
Any ideas?
kcls said:
Alright so I'm tired of the notification for the 4.2.1 update sitting in my notification bar. I rooted my phone right after I got it and did the very first OTA. I am running the latest version of CWM that I manually flashed. I thought I saw somewhere that ClockworkMod automatically installs OTA's, and keeps root when it's done? But every time I reboot to try to OTA, it doesn't work. It shows a little 3D Android with something spinning in it's stomach. CWM then pops up with a menu asking if I would like to install an untrusted zip (I'm assuming Google does something weird to the signature or something). But when I click to proceed, it just aborts after trying to flash.
Any ideas?
Click to expand...
Click to collapse
CWM doesn't do a every good job with Nexus 4 yet. And OTA usually fails if you have custom recovery.
It is best to ADB sideload the OTA. To keep root, you can use the OTA root keeper app from playstore (free), or just reroot the phone afterward.
Both ways should be easy and painless.
kcls said:
Alright so I'm tired of the notification for the 4.2.1 update sitting in my notification bar. I rooted my phone right after I got it and did the very first OTA. I am running the latest version of CWM that I manually flashed. I thought I saw somewhere that ClockworkMod automatically installs OTA's, and keeps root when it's done? But every time I reboot to try to OTA, it doesn't work. It shows a little 3D Android with something spinning in it's stomach. CWM then pops up with a menu asking if I would like to install an untrusted zip (I'm assuming Google does something weird to the signature or something). But when I click to proceed, it just aborts after trying to flash.
Any ideas?
Click to expand...
Click to collapse
You need to have the stock recovery installed to install the ota update.
Sent from my Nexus 4 using xda premium
KyraOfFire said:
CWM doesn't do a every good job with Nexus 4 yet. And OTA usually fails if you have custom recovery.
It is best to ADB sideload the OTA. To keep root, you can use the OTA root keeper app from playstore (free), or just reroot the phone afterward.
Both ways should be easy and painless.
Click to expand...
Click to collapse
Alright, how would I sideload it with adb? And I'll try the OTA RootKeeper. Thanks for your reply.
nbeebe24 said:
You need to have the stock recovery installed to install the ota update.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
How can I get the stock recovery back? Is there an IMG somewhere that I can fastboot flash?
Sent from my Nexus 4 using Tapatalk²
kcls said:
Alright, how would I sideload it with adb?
Click to expand...
Click to collapse
Reboot to recovery. You should be able to find adb side load option.
Then proceed to your command prompt (computer) and use the command
adb sideload filepath/filename.zip
Click to expand...
Click to collapse
Reboot system and you're good to go. (remember to wipe cache/dalvik)
KyraOfFire said:
Reboot to recovery. You should be able to find adb side load option.
Then proceed to your command prompt (computer) and use the command
Reboot system and you're good to go. (remember to wipe cache/dalvik)
Click to expand...
Click to collapse
Alright, thanks. Sorry for all the questions, but where on the system is the ota stored?
Sent from my Nexus 4 using Tapatalk²
Assuming you haven't made any other modifications and you have a custom recovery installed you can just flash the ota like any other rom. Download it from here: http://forum.xda-developers.com/showthread.php?t=1971169. Put it in your internal storage and flash.
El Daddy said:
Assuming you haven't made any other modifications and you have a custom recovery installed you can just flash the ota like any other rom. Download it from here: http://forum.xda-developers.com/showthread.php?t=1971169. Put it in your internal storage and flash.
Click to expand...
Click to collapse
Awesome, I'll do that tonight. Thanks so much everyone!
Sent from my Nexus 4 using Tapatalk²
KyraOfFire said:
CWM doesn't do a every good job with Nexus 4 yet. And OTA usually fails if you have custom recovery.
It is best to ADB sideload the OTA. To keep root, you can use the OTA root keeper app from playstore (free), or just reroot the phone afterward.
Both ways should be easy and painless.
Click to expand...
Click to collapse
sorry to threadjack, but if i sideload an OTA, will my settings and files be wiped? I am on stock rom.
A doubt
I have a custom recovery (CWM) and have not installed any custom ROM, running Stock 4.2.1
If Google decides to push update 4.2.2 then will it work without me having to do anything. As in will it be a simple painless process ?
rahulkadukar said:
A doubt
I have a custom recovery (CWM) and have not installed any custom ROM, running Stock 4.2.1
If Google decides to push update 4.2.2 then will it work without me having to do anything. As in will it be a simple painless process ?
Click to expand...
Click to collapse
you may just lose recovery. other than than i do not think anything else will happen
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
moose&beer said:
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
Click to expand...
Click to collapse
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
sfobrien said:
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
Click to expand...
Click to collapse
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
sfobrien said:
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
Click to expand...
Click to collapse
No worries. And yeah, I did the OTA, but held off until Google pushed a notification to my N10 for the update. I'll give goomanager a try. Appreciate the replies. Thanks.
This is normal behaviour in a OTA update. Installs a couple of files that, if a custom recovery is installed, reflash stock recovery on reboot. This doesn't happen if you flash a factory image.
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
three west said:
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
Click to expand...
Click to collapse
Thanks - I'll give goomanager a try.
beekay201 said:
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I assumed the same, but I got the same situation as OP, I'll try reinstalling TWRP using Nexus Root Toolkit, or does goomanager have a special functionality for those conditions?
Update: Used NRT to install TWRP in the advanced settings, worked beautifully.
The latest Google OTA's are not successfully installing unless you restore stock recovery fist and some are failing if you are rooted as well.
Best bet if you are running as rooted or custom recovery is to backup first, un-root, restore stock then sideload the OTA. This will save you lots of frustration and heartburn.
It's easy enough to restore stock and to re-root so just make it part of your ota routine.
Got a question. I lost root after the 4.3 ota update. Is it possible to get it back without losing everything on the tablet again? I was running SuperSU and OTARootkeeper at the time. When I got into OTARootkeeper is says the su file is there, but when I click restore root it seems not to be able to. I am not a super power user. I used WUGs tookkit to unlock it and root it in the first place. Also does this mean I lost unlock also?
Thanks!
I was in the same situation after installing the update through custom recovery. I remained unlocked. I used Wugs toolkit to root and install custom recovery (TWRP). In recovery I installed Chainfire's updated SuperSu zip. After booting back up, I had root and custom recovery. Search for SuperSu v1.43.
Groid said:
I was in the same situation after installing the update through custom recovery. I remained unlocked. I used Wugs toolkit to root and install custom recovery (TWRP). In recovery I installed Chainfire's updated SuperSu zip. After booting back up, I had root and custom recovery. Search for SuperSu v1.43.
Click to expand...
Click to collapse
Did you lose any data?
xzb6np said:
Did you lose any data?
Click to expand...
Click to collapse
No, you do not lose data after flashing a recovery. Chainfire leased SuperSU 1.5 today.
Username invalid said:
No, you do not lose data after flashing a recovery. Chainfire leased SuperSU 1.5 today.
Click to expand...
Click to collapse
Flashed 4.3 and lost root. I have downloaded the latest SU to my N7 and how am unsure how to go about flashing the ZIP since I no longer have access to custom recovery.
it worked
Username invalid said:
No, you do not lose data after flashing a recovery. Chainfire leased SuperSU 1.5 today.
Click to expand...
Click to collapse
Ok opened up Wugs Nexus Root toolkit. Let it update everything it wanted to and then then told it to root. I was indeed still unlocked and it went ahead and reestablished root without losing anything. I updated OTA RootKeeper afterward and all seems happy.
Thanks!
killswitch11 said:
Flashed 4.3 and lost root. I have downloaded the latest SU to my N7 and how am unsure how to go about flashing the ZIP since I no longer have access to custom recovery.
Click to expand...
Click to collapse
Flash the TWRP image via fastboot. Either with a toolkit or manually.
xzb6np said:
Did you lose any data?
Click to expand...
Click to collapse
As username is invalid posted, no you do not lose data by that method. At least, I lost no data.
Groid said:
As username is invalid posted, no you do not lose data by that method. At least, I lost no data.
Click to expand...
Click to collapse
You only lose data if you lock/unlock bootloader or wipe it yourself
Sent from my Nexus 7 using XDA Premium HD app
OK got one crazy issue. I root but sometimes I lose it and have to reboot to get it back. SuperSu can't write the binary. Every time I open it it wants to write the binary but can't seem to. After a reboot Otarootkeeper say root is there. Then later it will be gone and I have to reboot to get it back.
Sent from my Nexus 7 using XDA Premium HD app
xzb6np said:
OK got one crazy issue. I root but sometimes I lose it and have to reboot to get it back. SuperSu can't write the binary. Every time I open it it wants to write the binary but can't seem to. After a reboot Otarootkeeper say root is there. Then later it will be gone and I have to reboot to get it back.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have the same issue, used Wugfreshs Toolkit to root after 4.3, on reboot i have no root.
Hello everyone,
I noticed that this is a common problem and I realize just not that I shouldn't have just updated without informing myself.
Anyway, I checked and the root seems to be gone (checked with Root Checker, although the SU app is still there [but not working]).
I checked the fastbook and it says 'unlocked', which is good, I don't have to lose data.
How do I re-root properly?
I am using OS X at the moment and I have access to adb but, if needed, I can access a Windows computer again and use Nexus Root Toolkit again (that's what I used the first time I rooted).
I have CWM-SuperSU-v0.98.zip and recovery-clockwork-6.0.1.9-manta.img.
I checked the bootloader and it says 'no command' but it still has:
- reboot system now
- apply update from ADB
- wipe data...
- wipe cache...
Thanks in advance for any help
First thing - Nearly always you will lose root after applying an OTA - at least lately so that's not really a big deal.
Second - Get and always use the Latest version of root zip from chainfire: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
Or you can also just apply SuperSU from google play and you will prompted to reboot to update binaries etc. after you apply the OTA.
His blog on latest version: https://plus.google.com/+Chainfire/posts/QhrEdeJ3nqQ
I got the same problem.
I solved it by just by downgrading and upgrading back to the latest version of Cyanogenmod.
lg Darcade
I have the same problem...
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Easily got my root back using Wugfresh toolkit.
Only the paid for version of SuperSU - "Pro" will attempt to keep root after an OTA update. It worked perfectly for me on a 5, 7 and 10.
[Lemmy] said:
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Click to expand...
Click to collapse
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
gee2012 said:
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
Click to expand...
Click to collapse
thats what I did by now, just with CWM instead of TWRP.
[Lemmy] said:
thats what I did by now, just with CWM instead of TWRP.
Click to expand...
Click to collapse
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
gee2012 said:
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
Click to expand...
Click to collapse
...after having to go through this over and over again with every single update I'm starting to think that having root is definitely not worth the pain.
If you switch to TWRP using its built in SuperSU install makes re-rooting a breeze.
Sent from my SM-T800 using XDA Premium HD app
Been on Mahdi forever on my VS980 and wanted to try the new KK so I tried to use TitaniumBackup and it says that I don't have root.
That is weird.
It looks like after upgrading on one of the last updates, I lost root along the way.
I tried to flash the latest SuperSu in recovery and it didn't work.
What else can it be?
i can get into recovery fine.
Lost root..
illyfilly said:
Been on Mahdi forever on my VS980 and wanted to try the new KK so I tried to use TitaniumBackup and it says that I don't have root.
That is weird.
It looks like after upgrading on one of the last updates, I lost root along the way.
I tried to flash the latest SuperSu in recovery and it didn't work.
What else can it be?
i can get into recovery fine.
Click to expand...
Click to collapse
So, if you havent already done it, first make sure root is enabled at all in developer options (it can be disabled).. if it is enabled, and you still dont have root. Back your stuff up with titanium backup or the like. Wipe/clean flash the rom/gapps/superSu. If that doesn't fix it, it is a problem with the rom file itself
Got it by flashing SuperSU from the play store
Sent from my g2 using Tapatalk