Hi xda,
Im thinking about rooting my nexus 7 2013 but the problem is that I also want to be able to update my device with google's ota updates. Is there a way to root your device and still recieve ota updates from google? If there is a way, does that mean that you could update your device and still keep root? What im trying to say is that is there a way to update the device while keeping root on stock rom and stock kernel?
Thanks
speedsolve said:
Hi xda,
Im thinking about rooting my nexus 7 2013 but the problem is that I also want to be able to update my device with google's ota updates. Is there a way to root your device and still recieve ota updates from google? If there is a way, does that mean that you could update your device and still keep root? What im trying to say is that is there a way to update the device while keeping root on stock rom and stock kernel?
Thanks
Click to expand...
Click to collapse
Being rooted has no effect on getting OTAs. If you are completely stock (w/ stock recovery), you will still get an OTA notification. If you're using SuperSU Pro, there's an OTA survival mode that should keep you rooted even after updating via OTA. Worst case scenario is you lose root, in which case, all you gotta do is flash SuperSU again in recovery and you're good to go.
Check this out: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
It's in the Nexus 5 forum, but still serves pretty good insight on how OTAs work.
Yes and no. I've updated before with custom recovery and root and had no problems, but another time I got an error message because one of my system files may have been unintentionally modified even though I was careful not to modify any system files. So it usually works, but no guarantees.
Sent from my Nexus 10 using xda app-developers app
gc84245 said:
Yes and no. I've updated before with custom recovery and root and had no problems, but another time I got an error message because one of my system files may have been unintentionally modified even though I was careful not to modify any system files. So it usually works, but no guarantees.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
In that case, all you would have to do is flash the system.img from the factory image, then flash the OTA update zip in recovery.
Sent from my Nexus 5 using xda app-developers app
Thanks
Gesendet von meinem Nexus 7 mit Tapatalk
Related
Hello fellow XDA members!
I was just wondering about OTA updates, and since there seem to be a lot of rumors around the interwebs, i figured i might as well ask. Are the OTA updates affected post root and CWM flash? And if it is, what can one do to still get OTA updates if so?
Thanks in advance!
You can reinstall the stock recovery. You will lose your root if and when you utilize the OTA.
Sent from my SAMSUNG-SGH-I747 using xda premium
d3athsd00r said:
You can reinstall the stock recovery. You will lose your root if and when you utilize the OTA.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Great thanks! Is there anyway around this without losing root and/or CWM or would i have to update through kies? One more thing, if i remove bloatware from my device, would i still be able to update through kies?
lemonbox said:
Great thanks! Is there anyway around this without losing root and/or CWM or would i have to update through kies? One more thing, if i remove bloatware from my device, would i still be able to update through kies?
Click to expand...
Click to collapse
There is usually a flashable zip made available of a rom update. These are typically already rooted. Usually happens within 12 to 24 hours has been my experience. I usually just wait. Not sure abt up up updating thru Kies with bloat removed.
I have a i9250 gsm Galaxy Nexus, maguro. JWR66V. It used to be Yajuux but I changed this to Yakju with Wug Fresh's Nexus Tool kit. I manually updated my phone to 4.3. However, about once a week, I get a notice that my phone would like to update to 4.3. The download is only 1.7mb. Once I allow the update, the phone reset, boots up and says "installing system update" with the android mascot on the screen and a swirly atom-thing at his stomach. After about a minute a message comes up that says "error!" with the android mascot now on his back. I have to remove the battery and restart my phone, otherwise it hangs. The update notice won't come back for another week, unless I stop the google service framework app and clear the data. I'm assuming these system updates are to upgrade to JWR66Y, but I don't know why I keep having these errors. Any help/advice would be appreciated.
Figured it out
Solved. I managed to sideload the update through the Nexus toolkit. Even after updating though, it didn't show the correct version. I had to unroot by uninstalling supersu (survival mode didn't work), then doing the OTA update, then reinstalling the binaries for Supersu.
Can anyone recommend a good site/feed that keeps track of these security updates/other major updates?
And the toolkit gets the credits, even when the user still has no idea what just happened.
beekay201 said:
And the toolkit gets the credits, even when the user still has no idea what just happened.
Click to expand...
Click to collapse
braindead users win again!
No Clue..
Can someone, Experienced.. Tell me what exactly to do here.. I am on Stock Rom, Rooted, with TWRP Recovery. Exact same problem when I try to install the Update. Same 1.7 MB Update. Any Help would be much appreciated.
dipenv said:
Can someone, Experienced.. Tell me what exactly to do here.. I am on Stock Rom, Rooted, with TWRP Recovery. Exact same problem when I try to install the Update. Same 1.7 MB Update. Any Help would be much appreciated.
Click to expand...
Click to collapse
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for this explanation. Very helpful to braindead user like myself, and will help me know what to do for future updates.
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Does doing this wipe the phone?
Not if you only install the update. You will have to reinstall supersu after the update because you will lose root.
Sent from my Galaxy Nexus using Tapatalk 2
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
thats not correct. ive updated with OTAs through TWRP.
the update is failing because something isnt stock.
Zepius said:
thats not correct. ive updated with OTAs through TWRP.
the update is failing because something isnt stock.
Click to expand...
Click to collapse
Update through twrp by downloading the update not through ota since you have third party software.
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Update through twrp by downloading the update not through ota since you have third party software.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Requesting the download link if possible. Searched the forum but couldn't found one. Tx in Advance.
Solved. Got it! HERE
Simple question, if possible to be stock rooted and still have access to the OTA updates?
Sent from my Nexus 7 using XDA Premium 4 mobile app
moeinyoho said:
Simple question, if possible to be stock rooted and still have access to the OTA updates?
Click to expand...
Click to collapse
Yes, use the latest SuperSU 1.55. Versions prior to that had an issue that would block OTAs from completing successfully.
sfhub said:
Yes, use the latest SuperSU 1.55. Versions prior to that had an issue that would block OTAs from completing successfully.
Click to expand...
Click to collapse
I'm still a rookie with this nexus but I would need to unlock the bootloader then root right?
Sent from my SPH-L900 using XDA Premium 4 mobile app
sfhub said:
Yes, use the latest SuperSU 1.55. Versions prior to that had an issue that would block OTAs from completing successfully.
Click to expand...
Click to collapse
Is this true even if you loaded a custom recovery such as TWRP or CVM? My (probably faulty) understanding is that the custom recoveries were missing "something" that kept them from doing an automatic OTA update. Is that still correct?
PJ Clifford said:
Is this true even if you loaded a custom recovery such as TWRP or CVM? My (probably faulty) understanding is that the custom recoveries were missing "something" that kept them from doing an automatic OTA update. Is that still correct?
Click to expand...
Click to collapse
There is potential for custom recovery to be missing something as they sometimes use custom kernels which sometimes aren't built the exact same way as google/asus, so to be safest stick with stock recovery. I've had this problem on past platforms. On LG, the custom recovery would be able to flash everything except the Phone's radio, because the sequence for that was done in a proprietary manner. That left you with the new rom but the old phone radio, which basically wouldn't boot.
As it stands right now, TWRP 2.6.0.0 includes the stock kernel and has been verified to work for OTA updates. TWRP 2.6.1.0 includes a custom built kernel by the TWRP developers, so it hasn't been tested.
My advice is, stick with stock recovery, then wait it out for someone else to test out OTA updates on the particular custom recovery you are interested in, and then if that is successful, you can consider using that in the future.
What I can say is Google tests their OTA updates using stock recovery, so that is the safest to use, but other recoveries can also work especially if they include a stock kernel (but the chances for issues increases the more they deviate from stock)
Probably just me, but it seems like it is. albeit minor, step backwards going to the stock recovery...
The easiest way would be, if you just boot in the custom recovery to root you device.
fastboot boot name_of_the_recovery.img
Then make a nandroid-backup, so you could easy go back to stock.
(Also choose to backup the recovery)
And after it you could flash the superuser.zip in the recovery.
Gesendet von meinem Nexus 7 mit Tapatalk 4
Appreciate the answers but I just rooted n flashed Clean ROM lol
Thought I wouldn't have time to figure how to root a new device but did it in like 45 minutes
Sent from my Nexus 7 using XDA Premium 4 mobile app
Help !!!
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
I auto updated my nexus 7 2013 wifi 32gb with 4.2.2 and there were no problems. I put the device back to stock 4.4 first and unrooted the tablet as well. My suggestion is to get the toolkit and select any version for device then select flash stock and unroot box. I did this and received the ota update the next day. After updating successfully you can root and install custom recovery again if that is what you want. Do not OEM lock the device because every time you unlock it again you will erase all content.
Best of luck
Sent from my Nexus 7 using xda app-developers app
OP: Uninstall stickmount (easiest) or flash the debuggerd in this thread.
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
player911 said:
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
Click to expand...
Click to collapse
Being rooted is fine. I was rooted just had to uninstall stickmount, and it updated from 4.3 to 4.4.2, I did lose root, but that was easily rectified.
mdamaged said:
Being rooted is fine. I was rooted just had to uninstall stickmount, and it updated from 4.3 to 4.4.2, I did lose root, but that was easily rectified.
Click to expand...
Click to collapse
How did you update? Side-load?
I'm guessing the Stickmount issue is only present on 4.4 because I was on 4.4.1 (Stock Rooted ROM by Scroler) and flashed the OTA I received on device in TWRP and it successfully updated to 4.4.2...and I never lost root ?
Sent from my Nexus 7 using Tapatalk 4
Richieboy67 said:
How did you update? Side-load?
Click to expand...
Click to collapse
Nope, OTA.
thanks
Jleeblanch said:
I'm guessing the Stickmount issue is only present on 4.4 because I was on 4.4.1 (Stock Rooted ROM by Scroler) and flashed the OTA I received on device in TWRP and it successfully updated to 4.4.2...and I never lost root ?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Can you give us the link to the stock rooted rom by scroler?? i can't seem to find it anywhere. thnks alot!
mdamaged said:
Nope, OTA.
Click to expand...
Click to collapse
Cool, I just ran the update myself with no issues. I just changed back to the stock recovery first and ran the ota to 4.4 no problem. I was worried about it though because I had issues when doing my Nexus 4 but it was my fault. At the end in the recovery when it asked if I wanted it to fix root I clicked yes. I should have clicked no and just rerooted using wug or something.
Now I am going to grab the 4.4.2 update. I do not have ota yet for 4.1 or 4.2 on my Nex 7. My Nex 4 though is all set at 4.4.2 and it seems like they really fixed tons of stuff! I can't wait to get that on the 7!!
Thanks:good:
mdamaged said:
OP: Uninstall stickmount (easiest) or flash the debuggerd in this thread.
Click to expand...
Click to collapse
I used to have OTA problems with Stickmount and that damn debuggered file on my 2012 Nexus 7. Never installed it on my flo as a result.
Are you saying that simply uninstalling Stickmount will be sufficient for an OTA to take successfully? Does uninstalling reinstate the previous debuggered file, or must we replace it manually?
mlj11 said:
I used to have OTA problems with Stickmount and that damn debuggered file on my 2012 Nexus 7. Never installed it on my flo as a result.
Are you saying that simply uninstalling Stickmount will be sufficient for an OTA to take successfully? Does uninstalling reinstate the previous debuggered file, or must we replace it manually?
Click to expand...
Click to collapse
Yes. Upon installation, Stickmount makes a backup of debuggerd in the same directory with a bak extension, when uninstalled it renames it to debuggerd, restoring the stock debuggerd, I did not have to put it back manually.
player911 said:
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
Click to expand...
Click to collapse
I flashed 4.4.1-> 4.4.2 successfully with twrp on a rooted device but it was just rooted with a modified host file, no other mods.
godutch said:
I flashed 4.4.1-> 4.4.2 successfully with twrp on a rooted device but it was just rooted with a modified host file, no other mods.
Click to expand...
Click to collapse
I thought the issue was to do with OTA updates and and not flashing updates from recovery as this is defeating the purpose of OTA udates.
Sent from my Nexus 7 using xda app-developers app
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
vivre said:
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
Click to expand...
Click to collapse
You could always just do a full wipe and restore it to factory defaults. That'll do it for sure.
Sent from my Nexus 7 using Tapatalk
dmginc said:
You could always just do a full wipe and restore it to factory defaults. That'll do it for sure.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Anyway to do it without wiping data? :crying:
vivre said:
Anyway to do it without wiping data? :crying:
Click to expand...
Click to collapse
Sorta yeah. But it hurts more than it helps. Wiping is really the best way to go. Or just wait a day or two and see if it comes.
Sent from my Nexus 7 using Tapatalk
vivre said:
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
Click to expand...
Click to collapse
The over the air will not work if you have a custom recovery. You have to flash the update zip with TWRP or whatever custom recovery you are using. You could move the update from "cache" to "storage" if you still had it or just download it to storage and then flash (Install) it with TWRP..
wantabe said:
The over the air will not work if you have a custom recovery. You have to flash the update zip with TWRP or whatever custom recovery you are using. You could move the update from "cache" to "storage" if you still had it or just download it to storage and then flash (Install) it with TWRP..
Click to expand...
Click to collapse
Thanks.
Your method worked.... but only after I uninstalled Xposed Framework ! :good:
Hello
Thanks to this forum, I was able to Root my Tab Pro 10.1 and edit my permissions.xml so Apps can use my SD card.
Now that I am rooted, what happens if Samsung pushes a update? Are they any apps that help preserve root over a update (I used to use Voodoo Root Keeper on my old Asus Tablet).
Or do we update and have to wait for a new root method?
Sorry if this has been asked before, I appreciate any advice.
Thanks
Jason
jericko said:
Hello
Thanks to this forum, I was able to Root my Tab Pro 10.1 and edit my permissions.xml so Apps can use my SD card.
Now that I am rooted, what happens if Samsung pushes a update? Are they any apps that help preserve root over a update (I used to use Voodoo Root Keeper on my old Asus Tablet).
Or do we update and have to wait for a new root method?
Sorry if this has been asked before, I appreciate any advice.
Thanks
Jason
Click to expand...
Click to collapse
I don't think you'll be able to do an ota update. When I have my rooted Tab Pro 12.2 check for updates, I get this message, "Your device has been modified. Software updates are not available." Hopefully SamMobile http://www.sammobile.com/firmwares/ has the update soon after the ota. Then download for your region and try to root again. It'll be a first for me too.
jericko said:
Hello
Thanks to this forum, I was able to Root my Tab Pro 10.1 and edit my permissions.xml so Apps can use my SD card.
Now that I am rooted, what happens if Samsung pushes a update? Are they any apps that help preserve root over a update (I used to use Voodoo Root Keeper on my old Asus Tablet).
Or do we update and have to wait for a new root method?
Sorry if this has been asked before, I appreciate any advice.
Thanks
Jason
Click to expand...
Click to collapse
First of, you should never have to root again. The scary part is over. You should however install TWRP. Then when a new ROM gets released, you do a TWRP backup, and flash the new ROM . No muss, no fuss. You should also be using Titanium Backup on a regular basis so that you always have a current backup of your apps and data. Much faster, easier and SAFER than an OTA backup from the manufacturer.
Sent from my SM-T520 using Tapatalk
Jerryo100 said:
I don't think you'll be able to do an ota update. When I have my rooted Tab Pro 12.2 check for updates, I get this message, "Your device has been modified. Software updates are not available." Hopefully SamMobile http://www.sammobile.com/firmwares/ has the update soon after the ota. Then download for your region and try to root again. It'll be a first for me too.
Click to expand...
Click to collapse
aybesea69 said:
First of, you should never have to root again. The scary part is over. You should however install TWRP. Then when a new ROM gets released, you do a TWRP backup, and flash the new ROM . No muss, no fuss. You should also be using Titanium Backup on a regular basis so that you always have a current backup of your apps and data. Much faster, easier and SAFER than an OTA backup from the manufacturer.
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
Hello Aybesea69, are there just stock ROMS of the OTA released?
I am familiar with TWRP, TB and flashing.
If you're feeling adventurous, there's this: http://forum.xda-developers.com/showthread.php?t=2776206
It's still in the early stages, but looks promising.
I was only able to update using Kies, not OTA. Root was gone.
Sent from my SM-T520 using XDA Premium HD app
jaegorith said:
I was only able to update using Kies, not OTA. Root was gone.
Sent from my SM-T520 using XDA Premium HD app
Click to expand...
Click to collapse
So you were rooted, and updated using Kies? Then you lost root? Were you able to re-root?
jericko said:
So you were rooted, and updated using Kies? Then you lost root? Were you able to re-root?
Click to expand...
Click to collapse
Sorry, I haven't tried to re-root. I'm going to wait until custom ROMs are available. But yes to your other questions. While my device was rooted, whenever I checked for updates from the tablet, I kept getting the error message that my device is modified and no updates were available. So I installed Kies on my PC to check for updates. Kies found the latest update and installed it successfully. I lost root once the update completed.
Sent from my SM-T520 using XDA Premium HD app