As a long time Android power user, I rooted my Nexus as soon as I got the phone. However, I completely forgot about the best thing Nexus devices have to offer, OTA updates.
I completely ditched OTA before since I was on custom ROMs most of the time on other devices.
So here are the questions.
1) How will modifying the system partition affect OTAs? Will they still show up and I won't be able to install them?
2) How can I get OTA back and working? Does a simple "fastboot flash system/boot system.img/boot.img" with the stock system and boot partition fix the issue? If not, what do I do? And will it involve data wiping?
3) If I don't do those, I can still do a manual update for the system partition using fastboot, correct?
Note: I rooted the device using the Nexus Toolkit method over at the dev sub.
Sent from my Nexus 6P using XDA Forums
341464 said:
As a long time Android power user, I rooted my Nexus as soon as I got the phone. However, I completely forgot about the best thing Nexus devices have to offer, OTA updates.
I completely ditched OTA before since I was on custom ROMs most of the time on other devices.
So here are the questions.
1) How will modifying the system partition affect OTAs? Will they still show up and I won't be able to install them?
2) How can I get OTA back and working? Does a simple "fastboot flash system/boot system.img/boot.img" with the stock system and boot partition fix the issue? If not, what do I do? And will it involve data wiping?
3) If I don't do those, I can still do a manual update for the system partition using fastboot, correct?
Note: I rooted the device using the Nexus Toolkit method over at the dev sub.
Sent from my Nexus 6P using XDA Forums
Click to expand...
Click to collapse
1. They'll still show up, but any attempt to install them will fail.
2. See my guide.
3. Yes.
Heisenberg said:
1. They'll still show up, but any attempt to install them will fail.
2. See my guide.
3. Yes.
Click to expand...
Click to collapse
So wait, what's the status now on the latest SuperSU package? I've heard that its system-less installation now?
Sent from my Nexus 6P using XDA Forums
341464 said:
So wait, what's the status now on the latest SuperSU package? I've heard that its system-less installation now?
Sent from my Nexus 6P using XDA Forums
Click to expand...
Click to collapse
There are two versions, the traditional version, and the systemless version.
Heisenberg said:
There are two versions, the traditional version, and the systemless version.
Click to expand...
Click to collapse
Speaking of OTA and systemless. I have opted for the systemless root method. If I want to install an OTA, all I have to do is flash the stock boot image, install update, then re root correct? Assuming there are no changes to system?
Sent from my Nexus 6P using Tapatalk
Related
Right just a quick question if I root my nexus 7 just to use stick mount and a OTG cable and add removal. Will I still get the OTA updates from the big G.
I'm a compulsive ROM changer and I have never owed a full Nexus device and would just like to keep it pure Nexus so to speak but with Root.
Sent from Galaxy SIII using Tapatalk
Yes.
Yes, you'll still get OTA updates, but you'll lose root (I know 'cause my old Galaxy tab lost it when it got ICS), so if you want to keep root, use the Root Keeper app in the Play Store. I thing there are ways or apps that do this too, but I don't know.
You will get them but they wont update your nexus 7 because of a custom recovery
Sent from my Nexus 7 using Tapatalk 2
E_Goldstein said:
You will get them but they wont update your nexus 7 because of a custom recovery
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Ahhh that's what I thought
Sent from Galaxy SIII using Tapatalk
Ignore last poster.
You can still get your ota if you keep the stock recovery
You can still use a custom recovery for gaining root by doing fastboot boot recovery.img instead of fastboot flash recovery recovery.img
Doing it this way will give you a single boot into custom recovery while Leaving the actual recovery on your tab stock
Sent from my Nexus 7
E_Goldstein said:
You will get them but they wont update your nexus 7 because of a custom recovery
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
That's not true. You can root and still have stock recovery. In fact you'll have stock recovery unless you flash one manually. edit: or unless your root tool flashes the recovery.
And to the OP, yes, you sure can have root, and still have updates [but apparently not upgrades], I recommend that over unrooted stock, but I would definitely recommend a custom rom like Paranoid Android [CM10 based]. It lets you choose the layout [tablet and phablet] of any app.
Yes, you will keep root if here is an upgrade. You might not keep it going from 4.1 to 4.2 on the OTA because like then other guy said, he lost root after a big update. If you go from 4.1 to 4.1.1 you should be fine.
Sent from my SGH-T989 using xda premium
Then if this is true, that they will flash why for the past 2 weeks when people have asked the same question has everyone else said the same as i did??
You cant get a straight answer on this site now a days i wish it go back to 5 years ago. It was nice t be on here then
Sent from my Nexus 7 using Tapatalk 2
E_Goldstein said:
Then if this is true, that they will flash why for the past 2 weeks when people have asked the same question has everyone else said the same as i did??
You cant get a straight answer on this site now a days i wish it go back to 5 years ago. It was nice t be on here then
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
OK let me give you the full breakdown which should hopefully make things easier to understand for everyone
[RECOVERIES AND OTA UPDATES]
in order to flash a manufacturer OTA update you must have the stock recovery on your devices Recovery Partition
you can still use a custom recovery via fastboot boot recovery.img as this doesnt touch your physical recovery partition
by doing fastboot boot clockworkrecovery.img you can then install your su binaries to get root
[OTA UPDATES AND KEEPING ROOT]
there are 2 different types of OTA updates
Incremental and Full System Updates
[INCREMENTAL UPDATES]
an incremental update will just update files on your system partition, as a stock rom doesnt have SU binaries, a incremental update will never
touch them and thus root will not be affected
[Full System Updates]
a full system update will erase and flash a completely new system partition, as such all data on the system partition is replaced including SU binaries so with this type of update Root will be lost
even after a full system update it is easy enough to just fastboot boot clockworkrecovery.img and reflash the su binaries again afterwards so nothing is ever truly lost
hope this is slightly educational for some of you
i want to root my device but then I am also planning to unroot it in the future to try updates ota. and then eventually will root again. my question is it is safe to root and unroot a device multiple times? sorry for the noob question.
Not unless you mess up the process no...
Sent From My Toro+ via Tapatalk
No, it's not safe? Or No, it is safe?
Sent from my Nexus 7 using Tapatalk 2
thank you so much
AMoosa said:
No, it's not safe? Or No, it is safe?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It is safe unless you do something wrong.
As long as you keep the stock recovery and are only rooting the stock Rom. You will still get the ota updates while rooted.
However it is possible that applying the update will remove root, but then you can just root it again anyway
Sent from my HTC One X using xda app-developers app
Why not just apply a rooted version of the update and save time and problems. Sometimes updates half further rooting capabilities
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Don't need stock recovery
bagofcrap24 said:
It is safe unless you do something wrong.
As long as you keep the stock recovery and are only rooting the stock Rom. You will still get the ota updates while rooted.
However it is possible that applying the update will remove root, but then you can just root it again anyway
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. You don't need stock recovery. Clockworkmod can apply updates as long as signature verification is disabled. It will patch completely normally but on your next boot will overwrite clockworkmod with stock recovery. You can avoid this by telling it to prevent itself from being modified when it asks when you hit reboot.
Rooting does not prevent updates in any way shape or form. The only things that prevent OTAs are modified fastboot (modified bootloader partition), modified gsm/cdma radio drivers (radio partition, does not apply to nexus 7), modified kernels or boot files (modified boot partition), icon packs, deodexing or other system apk mods (modified system partition), or some very specific changes to the data partition. All of those only include modifying existing files, not adding new files.
Google has a list of checks in their update and what's checked depends on the update so all of those things CAN prevent updating but not all of them will break any one update. If you root it just adds a small binary file onto the filesystem so you're fine. If you use that root to replace the calculator app with the one from gingerbread or something though it will change that file and may prevent updating.
I just got a notification about new security patches. It seems to me that if all its doing are small security tweaks I can update safely with this OTA update and still retain root and everything else. Can someone chime in?
Sent from my Nexus 6P using Tapatalk
will.bates94 said:
I just got a notification about new security patches. It seems to me that if all its doing are small security tweaks I can update safely with this OTA update and still retain root and everything else. Can someone chime in?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The update will not work while you are rooted.
dratsablive said:
The update will not work while you are rooted.
Click to expand...
Click to collapse
What's preventing it? And to get around it is it just a simple unroot or will I basically need a relocked bootloader and everything else?
Sent from my Nexus 6P using Tapatalk
will.bates94 said:
What's preventing it? And to get around it is it just a simple unroot or will I basically need a relocked bootloader and everything else?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It depends on what method you used to root. If you have a systemless root, then you need to flash stock
boot.img
recovery.img
If you have a non-systemless root you will need to flash
boot.img
system.img
recovery.img
dratsablive said:
It depends on what method you used to root. If you have a systemless root, then you need to flash stock
boot.img
recovery.img
If you have a non-systemless root you will need to flash
boot.img
system.img
recovery.img
Click to expand...
Click to collapse
I do in fact have systemless. But why is this all necessary just for a small update that doesn't even change major files of M?
Sent from my Nexus 6P using Tapatalk
Because the updates checks for any changes to the system. And you need stock recovery because the OTA does not work with TWRP.
Just download the update and flash it using fastboot if you are on stock. You will have to flash the entire google image instead of the small incremental update but its easier than unrooting or flashing system and stock recovery which you will have to do in fastboot also.
murphyjasonc said:
Just download the update and flash it using fastboot if you are on stock. You will have to flash the entire google image instead of the small incremental update but its easier than unrooting or flashing system and stock recovery which you will have to do in fastboot also.
Click to expand...
Click to collapse
I am in fact stock software wise. But flashing the entire Google image will reset data and everything else won't it?
Sent from my Nexus 6P using Tapatalk
will.bates94 said:
I am in fact stock software wise. But flashing the entire Google image will reset data and everything else won't it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It will not wipe the data on your internal SD card. It will only over write your system partition. You will have to set your phone up and download your apps or restore them from titanium backup but all your personal data such as pictures will not be deleted.
murphyjasonc said:
It will not wipe the data on your internal SD card. It will only over write your system partition. You will have to set your phone up and download your apps or restore them from titanium backup but all your personal data such as pictures will not be deleted.
Click to expand...
Click to collapse
I am on a custom rom and want to flash stock rom without losing root and other data. Is it possible to do so with fastboot? Can't find a flashable stock rom.
rajarshi10 said:
I am on a custom rom and want to flash stock rom without losing root and other data. Is it possible to do so with fastboot? Can't find a flashable stock rom.
Click to expand...
Click to collapse
Probably not going to happen. Are you referring to the new security update or...?
Sent from my Nexus 6P using Tapatalk
See this thread:
http://forum.xda-developers.com/nexus-6p/general/january-security-update-incremental-zip-t3286533
Hey XDA,
My Nexus ha been a dream. Though I've hit a few bumps, I don't expect to waste money on other flagships again.
I don't need to be able to right this instant, but wiping cache is one of my regular troubleshooting tools. Upon troubleshooting an MMS issue I was having, I discovered my recovery wasn't working properly. Though I fixed the MMS issue by resetting APN settings, the recovery thing has been bothering me.
I am running stock and locked. I have done nothing to this phone to warrant it being my fault. The problem is simple (and a Google search indicated, common). When you get to Recovery, you get a droid on its back, a red exclamation mark and "NO COMMAND". Doesn't matter if you hold up and power, tap up, or get there from the bootloader. The recovery software is seemingly missing completely.
I have an extended warranty through the retailer I bought from, but the phone is otherwise fine, so this is a last resort.
My dilemma is that I want to use Android pay. My understanding is that even unlocking the bootloader breaks Android pay. Is this correct? If so, can one reliably reset the phones security trips to allow Android pay after flashing the recovery back on?
Thanks for the help.
No, unlocking the boot loader does not block Android Pay.
There is a systemless root method for the Nexus that allows you to use Android Pay while rooted, there are also a couple of ROMS that have it working currently as well.
celsian said:
No, unlocking the boot loader does not block Android Pay.
There is a systemless root method for the Nexus that allows you to use Android Pay while rooted, there are also a couple of ROMS that have it working currently as well.
Click to expand...
Click to collapse
Quite so? Can you provide links to the root method and mayhaps the roms? Does this mean I could slap TWRP on here with no consequence?
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Does this mean that I can't flash at least a stock recovery?
Download your system image, unzip it, unlock your bootloader and flash only the recovery.IMG in fastboot, then relock your bootloader again. Android Pay will work fine and your warranty won't be affected so long as you relock your bootloader
Arcaed said:
Does this mean that I can't flash at least a stock recovery?
Click to expand...
Click to collapse
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Sorry, but are you saying if I wanted to install twrp I would need a modified stock boot img?
The Stig 04 said:
Sorry, but are you saying if I wanted to install twrp I would need a modified stock boot img?
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
In that case, where do I get a full system flash?
Arcaed said:
In that case, where do I get a full system flash?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Sent from my Nexus 6P using Tapatalk
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
You beat me to it with #3. Unfortunately I'm at work and couldn't come back to this thread quickly enough.
toknitup420 said:
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Actually AP now works with systemless root again. I have AP working (yes actually making purchases), currently running the latest Chroma Rom with Supersu 2.61
Found the workaround in this thread.
I'm sure Google will patch it again though.
Arcaed said:
Quite so? Can you provide links to the root method and mayhaps the roms? Does this mean I could slap TWRP on here with no consequence?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65188325
Heisenberg said:
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I've always been under the impression that the device will not boot with twrp installed unless you have DM verity checks removed. Has something changed with that.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
I've always been under the impression that the device will not boot with twrp installed unless you have DM verity checks removed. Has something changed with that.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It isn't necessary. I'm on my eighth Nexus 6P and I haven't flashed any modified boot.img prior to flashing TWRP.
83097markcynt said:
Actually AP now works with systemless root again. I have AP working (yes actually making purchases), currently running the latest Chroma Rom with Supersu 2.61
Found the workaround in this thread.
I'm sure Google will patch it again though.
Click to expand...
Click to collapse
I can second this. I have systemless root, and AP working, confirmed with purchases. Just a note, if you can successfully add a card, that means it has to contact your bank for approval, therefore it should confirm AP is working.
I haven't downloaded any security patches since I followed the main guide and rooted my phone.
I now have seen the news regarding the security update and how many critical flaws there are so I would like to update.
How can I do so without losing root?
Losing root shouldn't really be a concern. All you need to do is flash SuperSU again afterwards, which takes about a minute.
https://play.google.com/apps/testing/eu.chainfire.flash
This is an app by Chainfire called Flashfire. It works perfectly for what you want. I have used it myself on a few occasions. Let me know how it worked for you.
Sent from my Nexus 6P using XDA-Developers mobile app
+1 FlashFire
If you are impatient and don't want to wait for the OTA zip, just download the factory image and flash the following files using flashfire.
boot.img
system.img
vendor.img
Remember to disable security before you flash or you will have an issue with the vendor.img.
Heisenberg said:
Losing root shouldn't really be a concern. All you need to do is flash SuperSU again afterwards, which takes about a minute.
Click to expand...
Click to collapse
Hey, so I'm rooted with stock ROM and EX kernel but received the April update, any info why I got it?
I thought if you're rooted you weren't supposed to get an OTA update.
Sent from my Nexus 6P using Tapatalk
Doodsz said:
Hey, so I'm rooted with stock ROM and EX kernel but received the April update, any info why I got it?
I thought if you're rooted you weren't supposed to get an OTA update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You'll still receive the OTA, you just can't flash it via the traditional method.
I remember using the FlashFire method a month ago. The update worked and I didn't lose root, but I lost TWRP in the process.
ZabiGarma said:
I remember using the FlashFire method a month ago. The update worked and I didn't lose root, but I lost TWRP in the process.
Click to expand...
Click to collapse
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Sent from my Nexus 6P using XDA-Developers mobile app
dratsablive said:
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Click to expand...
Click to collapse
I couldn't flash it with FlashFire. I had to reinstall it from PC, which ended up with TWRP asking for a password, meaning I had to end up wiping the phone, which was worse than doing the regular OTA update.
ZabiGarma said:
I couldn't flash it with FlashFire. I had to reinstall it from PC, which ended up with TWRP asking for a password, meaning I had to end up wiping the phone, which was worse than doing the regular OTA update.
Click to expand...
Click to collapse
The new version of twrp 3.0.2.0 has been fixed. At least for me it worked.
Nice, I haven't installed the latest TWRP. I'll give it a try.
What I don't recall, though, is if last time I lost the applications I installed by flashing them with TWRP (like viper4android) or which rely on root.
I always remove security before flashing updates. Only issue is setting up the Imprint and adding cards back to Android Pay.
dave2metz said:
https://play.google.com/apps/testing/eu.chainfire.flash
This is an app by Chainfire called Flashfire. It works perfectly for what you want. I have used it myself on a few occasions. Let me know how it worked for you.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Is FlashFire no longer available?
dratsablive said:
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
If you use FlashFire just deselect recovery from the list when you load the latest update.
Sent from my Nexus 6P using XDA-Developers mobile app
Flash stock recovery and then ADB sideload the update. Links can be found in general. Then when it's done reflash twrp and SuperSU. Pretty easy. I've done it.