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
Related
Hello,
My wife has a Nexus 4.
I unlocked the bootloader, flashed TWRP, rooted it, and installed busybox.
Yesterday she handed me her phone and it was sitting in TWRP.
She said she got a message saying there was an update and she clicked okay.
I asked her if she saw anything going on but she wasn't paying attention so I didn't know if the update was applied or not.
So... I just rebooted the system from within TWRP.
Looking at her "about phone" it still shows that she is on 4.2.1 and when I check for updates it says she is up to date.
Questions:
What to do now?
Why wasn't the update applied? ... in the past on my Nexus 7 I have done OTA updates with rootkeeper installed and TWRP applied them automatically.
Was the update file deleted from her phone or can I find it somewhere in TWRP and apply it?
Is it like a normal .zip that you install or is it another process?
I'm in the same situation, unsure what to do.
I don't want to have to to do a factory reset for a minor update.
EDIT: Also installing the OTA.ZIP in TWRP fails
Got there in the end:
a) If you want to keep your data & settings and are running the stock rom; only flash boot.img, system.img, and recovery.img (optional) with fastboot.
Here is the JOP40D factory image if you need it. occam-jop40d-factory-ca7602f0.tgz - 327.21 MB
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
alexroborock said:
Got there in the end:
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
Click to expand...
Click to collapse
There must be a better way to do this.
That is a huge security risk flashing someone else's untrusted image onto your phone.
What about adb sideload?
You can download the image directly from Google
Sent from my Nexus 4 using Tapatalk 2
You need stock recovery for the ota update to work.
Sent from my Nexus 4 using xda app-developers app
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
silverramsrt said:
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
Click to expand...
Click to collapse
Did you lose root?
Rizy7 said:
Did you lose root?
Click to expand...
Click to collapse
Yes. The update replaced the recovery_from_boot.p or whatever file and the insecure boot image I had. I just reflashed TWRP, did a factory reset and installed CM anyway.
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
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.
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...
Link to the developer Preview for anyone interested
https://developer.android.com/preview/download.html#top
I'm currently rooted, with TWRP. So ideally how to install and keep everything and I assume you just flash supersu.zip to root again.
TIA.
flashfire.
Thanks, just tried, but it doesn't seem to recognized this zip from the link above
angler-npf26f-factory-0cd1829d.zip
Is there a different zip to flash?
install it as firmware
Use fastboot and to save your data, don't flash userdata.img.
https://www.youtube.com/watch?v=dsKn2E68A0M
Quick q on the subject. Twrp, rooted, dp1, modded build.prop, flashed Pixel bootanimation and navbar buttons. I suppose I can't use flashfire, right?
Puck24 said:
Quick q on the subject. Twrp, rooted, dp1, modded build.prop, flashed Pixel bootanimation and navbar buttons. I suppose I can't use flashfire, right?
Click to expand...
Click to collapse
I have the same setup and also want to know how to flash without losing anything. Also would rather not adb. Will flashfire do this without losing root?
Also, I went to the OP link to get the ota, and it's just a Google page on how to test an update. Where do I get the update file?
Same here.
Sent from my Pixel XL using XDA-Developers mobile app
I actually got the OTA notification sometime in the last 8 hours while I was asleep. Saw some1 posting the link in the General section, I think
I also have (had) all the pixel goodies installed and flashed the OTA with FlashFire. Now everything is gone
I used FF. If you unchecked recovery and check modem, you'll keep recovery and root. Pixel goodies are gone, but easy to reflash
Confirm: you loose Pixel stuff but just reflash, only strange thing is that I had to flash Pixel Launcher thru twrp as with FlashFire it was not working.
Did you flashfire the OTA or the Factory Image of the DP2?
Enviado de meu Pixel XL usando Tapatalk
Factory image from here
https://developer.android.com/preview/download.html#device-preview
Carterman32 said:
I used FF. If you unchecked recovery and check modem, you'll keep recovery and root. Pixel goodies are gone, but easy to reflash
Click to expand...
Click to collapse
You did put the factory image on your nexus and then press the + button and flash firmware? Is that it? And then you can select to keep your datas and root?
And in order to keep TWRP, do I uncheck recovery or it will keep TWRP anyway?
Thanks in advance.
I unzipped and flashed just system.img in TWRP, followed by SuperSu, and then modified the vendor/build.prop to match the system/build.prop to keep from getting the "internal problem" alert. Maybe not the simplest method, but worked fine.
Sent from my Pixel XL using Tapatalk
timosuomi said:
I unzipped and flashed just system.img in TWRP, followed by SuperSu, and then modified the vendor/build.prop to match the system/build.prop to keep from getting the "internal problem" alert. Maybe not the simplest method, but worked fine.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Unless you have a specific desire not to do this, flash the matching vendor.img in TWRP. This is tied to that "internal problem" warning because of the proprietary drivers included in the file.
Also, I do not recommend flashing just the system.img for every update. You may run into a non functional camera when Google releases an OTA that requires the latest boot and vendor to be installed.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Unless you have a specific desire not to do this, flash the matching vendor.img in TWRP. This is tied to that "internal problem" warning because of the proprietary drivers included in the file.
Also, I do not recommend flashing just the system.img for every update. You may run into a non functional camera when Google releases an OTA that requires the latest boot and vendor to be installed.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Good call. I'm just coming from a Nexus 6, and I don't recall dealing with vendor.img with that or previous Nexii.
Sent from my Pixel XL using Tapatalk
timosuomi said:
Good call. I'm just coming from a Nexus 6, and I don't recall dealing with vendor.img with that or previous Nexii.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Ahh, that makes sense now. The vendor partition was originally part of the system. The Nexus 9 was the first Android device to feature a separate vendor partition and both 2015 Nexus devices launched with this separate partition.
Flash boot, system, and vendor each month OR whenever you move to a different month's OTA. With custom roms, just flash the vendor and custom rom. You can check /vendor/build.prop to see which vendor is currently installed.
Sent from my Nexus 5X using Tapatalk