Database Users

The 4.2.1 OTA Help

So i just switched from HTC ONE X to the nexus 4 and my version is 4.2 and i just rooted it. I have the system OTA update 4.2.1. Should i take it or is there another way to update my phone to 4.2.1 without OTA?

Do not OTA update once you're already rooted; flash this stock ROM (https://www.dropbox.com/s/syi2vmxh0noi2bv/occam-jop40d-factory-ca7602f0.tgz) and re-root.

klvnhng said:
Do not OTA update once you're already rooted; flash this stock ROM (https://www.dropbox.com/s/syi2vmxh0noi2bv/occam-jop40d-factory-ca7602f0.tgz) and re-root.
Click to expand...
Click to collapse
Thank you i was looking for this file! so i just put it in my SD card and then install Zip from sd card from recovery?

ronnyg12 said:
Thank you i was looking for this file! so i just put it in my SD card and then install Zip from sd card from recovery?
Click to expand...
Click to collapse
That is a tgz file, not a zip. You'll need a PC, 7zip and fastboot.

estallings15 said:
That is a tgz file, not a zip. You'll need a PC, 7zip and fastboot.
Click to expand...
Click to collapse
Yes yes i figured it out

I've been trying to do this without wiping my device. It's still downloading so I haven't seen the contents, but I'm assuming just flash the .img files with fastboot and it won't erase anything? Would the Rootkeeper app work for this?

if you're only rooted, ota will work and would install without issues. it will only fail if you have modified some system files or the recovery. no need to reflash anything except the supersu for root if you don't use rootkeeper

I'm using Franco's kernel and CWM recovery. I have the stock system files, so if I flash those back, how do I go about applying this update? I'm so sick of seeing the update message in my notification bar and do not want to wipe to flash a new ROM.
Edit: I have previously tried flashing the stock boot.img and recovery.img, but trying the update via the notification still failed.

Nitemare3219 said:
I'm using Franco's kernel and CWM recovery. I have the stock system files, so if I flash those back, how do I go about applying this update? I'm so sick of seeing the update message in my notification bar and do not want to wipe to flash a new ROM.
Click to expand...
Click to collapse
Flash the stock recovery.img and boot.img. You won't lose anything.

Nitemare3219 said:
I'm using Franco's kernel and CWM recovery. I have the stock system files, so if I flash those back, how do I go about applying this update? I'm so sick of seeing the update message in my notification bar and do not want to wipe to flash a new ROM.
Edit: I have previously tried flashing the stock boot.img and recovery.img, but trying the update via the notification still failed.
Click to expand...
Click to collapse
Your settings probably also modified the system files. Try flashing that too since you have the stock files. Just don't do userdata so your data is kept intact
Sent from my Nexus 4 using Tapatalk 2

why it is not possible to make OTA update on rooted phone?
Sent from my Nexus 4 using Tapatalk 2

I rooted, unlocked bootloader and flashed recovery yesterday then installed the OTA after, had no issues at all. If you are using cwm recovery it re-roots and prevents stock recovery being flashed after the ota is installed.
So am running rooted 4.2.1 at the mo.. And its sick
Sent from my Nexus 4 using xda app-developers app

blablazzz said:
why it is not possible to make OTA update on rooted phone?
Click to expand...
Click to collapse
You can, it's fine and will work as long as you have stock recovery. You might lose root but can easily re-root if necessary.
Sent from my Nexus 4 using xda premium

why OTA will not work if custom recovery will be present?
Sent from my Nexus 4 using Tapatalk 2

blablazzz said:
why OTA will not work if custom recovery will be present?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Because it won`t!!!

So how does OTA work?

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

OTA without computer?

I was curious if there is a way to take an ota on my stock rooted 6P with TWRP recovery.
I presume flashing the ota zip won't work if system has been modified in any way, however I did use systemless root... Can I flash the ota zip in TWRP?
P.S. I'm familiar with the fastboot process, done it quite a few times. Just curious if I'm going to have to do that each month for a security update.
Sent from my Nexus 6P using Tapatalk

GatorsUF said:
I was curious if there is a way to take an ota on my stock rooted 6P with TWRP recovery.
I presume flashing the ota zip won't work if system has been modified in any way, however I did use systemless root... Can I flash the ota zip in TWRP?
P.S. I'm familiar with the fastboot process, done it quite a few times. Just curious if I'm going to have to do that each month for a security update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The OTA installer looks at system, boot, and recovery. If there is any modification from stock, it will abort installation. So as long as you want to run with TWRP and a rooted system, you will have to fastboot flash the factory image files.

Is there somewhere where I can find the ota zip? I'm still stock.

cam30era said:
The OTA installer looks at system, boot, and recovery. If there is any modification from stock, it will abort installation. So as long as you want to run with TWRP and a rooted system, you will have to fastboot flash the factory image files.
Click to expand...
Click to collapse
Modifying the build prop for wifi tether and unlocked bootloader will tasty flag the ota update via flashing or waiting for ota being pushed?
Sent from my Nexus 6P using Tapatalk

imex99 said:
Modifying the build prop for wifi tether and unlocked bootloader will tasty flag the ota update via flashing or waiting for ota being pushed?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Unlocked bootloader has no effect. Build.prop edits will cause OTA install to abort.

cam30era said:
Unlocked bootloader has no effect. Build.prop edits will cause OTA install to abort.
Click to expand...
Click to collapse
So, just delete build prop edit, can flash ota zip with twrp, reboot, edit build prop and reboot again?
Trying to keep pay working...
Sent from my Nexus 6P using Tapatalk

imex99 said:
So, just delete build prop edit, can flash ota zip with twrp, reboot, edit build prop and reboot again?
Trying to keep pay working...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No. OTA can only be ADB sideloaded via stock recovery.

Help to get N preview 3 installed from a custom rom with no pc just TWrp

Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk

iamdarren said:
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).

DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
Where can I find the modified boot image?
Edit: Found it, nevermind.

messiahfreedom said:
Where can I find the modified boot image?
Edit: Found it, nevermind.
Click to expand...
Click to collapse
Grab it from here, and make sure to download the corresponding boot.img to your build number.
Link: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684

DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
If we do it this way, will we lose data? Can we just update from 6.0.1?

jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk

jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
No, you won't loose any data. Your userdata/data partition will stay as is. You will just wipe the system and boot through TWRP, and then flash the listed image files.

superchilpil said:
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
But if we do it the manual way as stated before, do we lose root? What about gapps? Will those be included?

flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!

I ended up loading up from the PC. It's better this way because I only had 2gb of space on my 64gb!!! Bad thing is, I have spent about 2hrs installing!
Sent from my Nexus 6P using Tapatalk

So I can use flashfire to flash the latest N beta even though I'm currently running a custom ROM?
Sent from my Nexus 6P using XDA-Developers mobile app

GatorsUF said:
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
Click to expand...
Click to collapse
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.

x.0ni.x said:
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
Click to expand...
Click to collapse
why does the wug toolkit not work?

I don't know a lot about Flashfire as far as it's compatibility with Custom Roms and such. I was previously on stock android Marshmellow with root and twrp. My phone downloaded the OTA for Android N when I "enrolled" in the beta program. I chose not to allow the phone to attempt to install the OTA as it would likely fail due to my custom recovery, to my surprise when I opened flashfire it offered to install the "update.zip" (AKA the OTA) and I simply hit "flash". It installed the OTA (did not use TWRP) and rooted my phone all on it's own, I did not lose anything no data was lost.
As a side not I would not recommend using Flashfire if you don't know how to use fastboot commands and the Android SDK. It is not complicated and it is a almost certain way to fix your phone when things go haywire. I strongly encourage you to learn how to use it as it is essential to owning a Nexus imo. These root kits and flashfire programs are cool, but they are always subject to failures...

Installing OTA 7.1.2 whilst having TWRP installed caused soft brick.

I have just installed went to install the new OTA onto my angler, which was done through TWRP, except it seems to have either corrupted or erased my system partition, because now I just get the "No Command" on boot. TWRP still works and my files are intact, should I just flash a stock 7.1.1 image from Google? (7.1.2 is not yet provided outside OTA for angler it seems)

fuj1n said:
I have just installed went to install the new OTA onto my angler, which was done through TWRP, except it seems to have either corrupted or erased my system partition, because now I just get the "No Command" on boot. TWRP still works and my files are intact, should I just flash a stock 7.1.1 image from Google? (7.1.2 is not yet provided outside OTA for angler it seems)
Click to expand...
Click to collapse
I would download the 7.1.1 stock like you said and then flash boot, system, vendor, and Recovery. You have to be completely stuck before you install any OTAs. This should leave your data intact but I would make sure you have a backup somewhere before you begin
Sent from my Nexus 6P using Tapatalk

funnel71 said:
I would download the 7.1.1 stock like you said and then flash boot, system, vendor, and Recovery. You have to be completely stuck before you install any OTAs. This should leave your data intact but I would make sure you have a backup somewhere before you begin
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thank you, I downloaded the stock image, deleted userdata.img from the zip and used fastboot update <image>, that worked like a charm and all my data was left intact. Will update when Google decides they want to let me install the OTA again.

fuj1n said:
Thank you, I downloaded the stock image, deleted userdata.img from the zip and used fastboot update <image>, that worked like a charm and all my data was left intact. Will update when Google decides they want to let me install the OTA again.
Click to expand...
Click to collapse
If you still have a copy of the OTA you could install that using ADB sideload from stock recovery not TWRP. But as you say a safer route might be to just wait for the OTA to appear within your stock installation. Completely up to you
Sent from my Nexus 6P using Tapatalk

Related to this issue: I have TWRP, root and the Pixel package flashed to my 7.1.1 installation. I got the beta notification update this morning.
How would I proceed with flashing the update?
Flash stock recovery and system and download the OTA then or something else?

Puck24 said:
Related to this issue: I have TWRP, root and the Pixel package flashed to my 7.1.1 installation. I got the beta notification update this morning.
How would I proceed with flashing the update?
Flash stock recovery and system and download the OTA then or something else?
Click to expand...
Click to collapse
My recommendation is to flash boot, system, recovery, and xender. That should leave your data intact and put your to complete stock. I cannot advise on beta programs because I have never done it and I don't wish to just for the simple fact that it is beta. But if you are brave it sounds like you have the right idea.
Sent from my Nexus 6P using Tapatalk

I was able to flash on rooted 6P by flashing stock recovery. Took a long time at boot animation, and also security is back to January level.

Did you have the Pixel modifications?

Puck24 said:
Did you have the Pixel modifications?
Click to expand...
Click to collapse
I did before I applied the update, I had to modify build.prop afterwards to get the Assistant back. Haven't applied the pixel mod since it hasn't been updated for the 7.1.2 release.

How can I remove the OTA notification? I don't want to update but notification is annoying.

thegios said:
How can I remove the OTA notification? I don't want to update but notification is annoying.
Click to expand...
Click to collapse
If you are rooted you can freeze the update notification process.
Sent from my Pixel XL using XDA-Developers Legacy app

thegios said:
How can I remove the OTA notification? I don't want to update but notification is annoying.
Click to expand...
Click to collapse
Just slide the notification just a little too the side and hit block all notifications for it it go into developer settings and turn off auto updates
Sent from my Nexus 6P using Tapatalk

dratsablive said:
I did before I applied the update, I had to modify build.prop afterwards to get the Assistant back. Haven't applied the pixel mod since it hasn't been updated for the 7.1.2 release.
Click to expand...
Click to collapse
Thx for the info. I'll hold off for now, since i like the Pixel nav keys, tinted navbar and boot animation

Well you can also apply the boot animation. Works for me.
Sent from my Pixel XL using XDA-Developers Legacy app

just flash the stock recovery that matches your build number and you all be fine like me .

Is there a way to do that without a PC? I would like to flash stock recovery for 7.1.1.

RockZors said:
Is there a way to do that without a PC? I would like to flash stock recovery for 7.1.1.
Click to expand...
Click to collapse
The only way you can do that is if your phone is rooted and you flash it with something like Flashify.
Sent from my Nexus 6P using Tapatalk