I tried to install the official OTA update on my Nexus 6P using Flashfire. I got an error message stating that the new OTA was older than the developer build I am already running so it wouldn't flash. Am I missing something here? Did anybody else have this problem?
Download full factory image and try flashing that with FlashFire, you don't lose your data and make sure to untick the recovery option
If I untick the recovery option does that mean I lose root and my custom recovery?
jhs39 said:
If I untick the recovery option does that mean I lose root and my custom recovery?
Click to expand...
Click to collapse
I was on dp2. Downloaded the whole ROM and used flash fire to flash. Didn't untick anything. After flashed, lost viper mod but other apps remained, including root. I did a factory reset, started from scratch, updated apps and flashed super su zip. Didn't lose twrp.
tropical cactus said:
I was on dp2. Downloaded the whole ROM and used flash fire to flash. Didn't untick anything. After flashed, lost viper mod but other apps remained, including root. I did a factory reset, started from scratch, updated apps and flashed super su zip. Didn't lose twrp.
Click to expand...
Click to collapse
Is there anything that makes the new update worth all that trouble?
jhs39 said:
Is there anything that makes the new update worth all that trouble?
Click to expand...
Click to collapse
The Dec security patch. Everything else is the same as dp2 and no beta tester logo at boot up.
tropical cactus said:
I was on dp2. Downloaded the whole ROM and used flash fire to flash. Didn't untick anything. After flashed, lost viper mod but other apps remained, including root. I did a factory reset, started from scratch, updated apps and flashed super su zip. Didn't lose twrp.
Click to expand...
Click to collapse
I was on DP2 and used the factory image but only flashed boot, system and vendor. No problems so far.
Sent from my Pixel XL using XDA-Developers mobile app
tropical cactus said:
The Dec security patch. Everything else is the same as dp2 and no beta tester logo at boot up.
Click to expand...
Click to collapse
Thanks for the info.. Will probably just wait for the IT'S then.. dB2 seems perfectly stable to me.
Joe
dratsablive said:
I was on DP2 and used the factory image but only flashed boot, system and vendor. No problems so far.
Click to expand...
Click to collapse
Do you notice any changes from DP2?
Joe
jhs39 said:
Do you notice any changes from DP2?
Joe
Click to expand...
Click to collapse
Performance wise no.
Related
Google has just released the April Security bulletin and the nexus factory images.
Factory Images Download
Nexus Security Bulletin April.2016
Anyone know/tested if the current SU works on the new Linux kernel?
Sent from my Nexus 5X using XDA-Developers mobile app
mymusicathome said:
Anyone know/tested if the current SU works on the new Linux kernel?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm using 2.71 and it works just fine. Android Pay also still works on the latest everything.
Flashed the factory image and no more optimizing apps???
Need to know if there are a bug fixes like wifi etc...
mymusicathome said:
Anyone know/tested if the current SU works on the new Linux kernel?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
What kernel was prior to this?
jlmcr87 said:
Flashed the factory image and no more optimizing apps???
Click to expand...
Click to collapse
Did you double check and did it right? I just updated my 5X and N7 LTE, both did the optimizing app piece that took forever. Erased the cache?
The optimizing apps comes from clearing Art/dalvik cache.
Sent from my Nexus 5X using Tapatalk
I have issues with the april build, i am not able to see any notifications in my pull down and also quick settings are missing. i downgraded to the march build and it is still broken :/
I also double-wiped everything before flashing the new images..no optimizing apps :-s
PS: For me, xPosed v81 doesn't work with latest build
Just try without xposed installed...
Scutariu said:
I also double-wiped everything before flashing the new images..no optimizing apps :-s
PS: For me, xPosed v81 doesn't work with latest build
Click to expand...
Click to collapse
There are no apps to optimize! What are you possibly talking about? And to the person whose flash took a long time due to optimizing apps, you might want to start over and do it the right way.
Sent from my Nexus 5X using XDA-Developers mobile app
enzippo said:
Just try without xposed installed...
Click to expand...
Click to collapse
Tried with v79..worked
bobby janow said:
There are no apps to optimize! What are you possibly talking about? And to the person whose flash took a long time due to optimizing apps, you might want to start over and do it the right way.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
I just confirmed that guy's statemend, I DID NOT did 2 full wipes to get "Optimizing apps", I did it to try something else
Scutariu said:
Tried with v79..worked
I just confirmed that guy's statemend, I DID NOT did 2 full wipes to get "Optimizing apps", I did it to try something else
Click to expand...
Click to collapse
Oh I see. There are only 2 things I see that happen on an image flash. 4 or is it 8 apps get updated immediately, then all the others start downloading updates from the PS. I think there are about 2 dozen of them in all and it takes forever. I presume that was your experience too. I feel for the guy that optimized because he probably didn't do a factory reset before flashing the new system.img.
Did you restore via Titanium by any chance? I'm having some issues on paid versions of apps I restored. PS says it might be a bootlegged app and denied access to them. I had to uninstall and reinstall from the PS which naturally wiped all my data from the backup. I wonder if I could restore just data? Oh well, all fixed now but this is something new.
It took a long time to optimize my apps because there are quite a number of apps and they were mostly games that are quite large. The process basically recaches the apps since I erased the cache as part of the flash. It's part of the process -
Flash bootloader
reboot bootloader
flash radio
reboot bootloader
flash boot.img
erase cache
flash cache
flash recovery
flash system
flash vendor
reboot
I don't flash userdata since I don't want to wipe user data. After all that, flash twrp and do your usual root, etc...
Try using flashfire by Chainfire (requires root). Simply download the factory image and flash it using the app (make sure to untick flashing of data and select inject root). That way you don't need to use your PC and flashing just take around 2-3 min. If you would like to install twrp afterwards you can do so by using flashify since you're already rooted.
Skickat från min Nexus 5X via Tapatalk
just installed elementalx kernel. do i have to flash that again, also can i skip flashing recovery since i got twrp? assuming i have to flash supersu again
OTA: https://android.googleapis.com/pack...01e537.signed-bullhead-MHC19Q-from-MHC19J.zip
sethyx said:
OTA: https://android.googleapis.com/pack...01e537.signed-bullhead-MHC19Q-from-MHC19J.zip
Click to expand...
Click to collapse
Noob here.. Can you guide? I have 5x stock rooted , twrp and elemental x installed.
How can i update to april patch without erasing media/data and still have root, twrp and elemental x?
Thanks in advance
sravanz said:
Noob here.. Can you guide? I have 5x stock rooted , twrp and elemental x installed.
How can i update to april patch without erasing media/data and still have root, twrp and elemental x?
Thanks in advance
Click to expand...
Click to collapse
Go to the dirty unicorns thread and download the vendor.img file and flash with the newest twrp
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
Three again. Verizon, Dutsche and every one else. Flashing now.
So far full images only, no OTA.
OTAs are up too. Anyone see a change log or know if TWRP and SuperSU are working?
sliding_billy said:
OTAs are up too. Anyone see a change log or know if TWRP and SuperSU are working?
Click to expand...
Click to collapse
I am still investigating, but it would seem SU is not working.
I ran flash-all.bat after removing the -w
Boots and runs fine.
fastboot booted twrp RC1 and flash SU 2.79 SR3
It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.
TonikJDK said:
I am still investigating, but it would seem SU is not working.
I ran flash-all.bat after removing the -w
Boots and runs fine.
fastboot booted twrp RC1 and flash SU 2.79 SR3
It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.
Click to expand...
Click to collapse
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.
sliding_billy said:
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.
Click to expand...
Click to collapse
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.
Kisakuku said:
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.
Click to expand...
Click to collapse
Just was a gut feeling that whatever was going wrong in the developer build would somehow been implemented in the May build. I am sure they are unrelated, but that was why I asked before the OP was updated to include the SU break.
The VZ OTA will download if you set the date to May 4th.
just checked my phone and got Verizon update without changing date
My OTA for Verizon didn't hit yet. And moving the date forward didn't help. Hopefully soon.
what will happen to supersu if try to flash this full factory image via flashfire and
bush911 said:
what will happen to supersu if try to flash this full factory image via flashfire and
Click to expand...
Click to collapse
It will be gone.
Pixel users are reporting bootlooping on the May update after flashing TWRP only
https://forum.xda-developers.com/showthread.php?p=72121371
https://forum.xda-developers.com/showthread.php?p=72120712
What are the chances that this was done purposely? "Breaking root and twrp"
DR3W5K1 said:
What are the chances that this was done purposely? "Breaking root and twrp"
Click to expand...
Click to collapse
Anyone try Magisk? I imagine same result.
Sent from my Pixel XL using Tapatalk
I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.
if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore
itchy67x said:
if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore
Click to expand...
Click to collapse
Just use April's bootloader.
Taebom said:
Just use April's bootloader.
Click to expand...
Click to collapse
thx that works
Taebom said:
Just use April's bootloader.
Click to expand...
Click to collapse
Thanks, that works for the Pixel too. I flashed April's K bootloader on the May L version no problem. TWRP and SU work fine now.
dowlf said:
I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.
Click to expand...
Click to collapse
FWIW: sideload of n2g47o worked fine on my (stock) XL. Did you have any modifications?
Hi there,
i try to install factory image on my nexus 6P 8.0.0 (OPR6.170623.017, Sep 2017) with the adb commands, everthing works ok but after turn on the device, the logo of starting android is moves and moves and moves and no start of the system, in the previus version it works correct, there is something on these version that makes it wrong?
secondly, i think i will downgrade to 8.0.0 (OPR6.170623.013, Aug 2017, Not for TMO/USCC/Fi), there is option to upgrade using flashfire ? if so, which version i need to download full ota image or factory image for that?
thank you
update:
so i managed to install factory image 8.0.0 (OPR6.170623.017, Sep 2017) , but when i go to settings under updates still there is update of 991MB - it's very strange.
also i need to know about the flash fire which version i need to security updates full ota image or factory image for that?
thank you
Been answered already.
The latest is 019 and after 017 you will get that OTA of 019.
wizardwiz said:
Been answered already.
The latest is 019 and after 017 you will get that OTA of 019.
Click to expand...
Click to collapse
and where i can find these to download? it's not on the developer site,
also i have another questions
thank you
You can get the 019 OTA (991Mb) file here
https://forum.xda-developers.com/sho...&postcount=282
It is weird that people get 019 OTA update of 991Mb after updating to 017. I do agree on that.
wizardwiz said:
You can get the 019 OTA (991Mb) file here
https://forum.xda-developers.com/sho...&postcount=282
It is weird that people get 019 OTA update of 991Mb after updating to 017. I do agree on that.
Click to expand...
Click to collapse
i got 404 page, but i found it and install it now everything is ok.
so about the flash fire which version i need for the security updates full ota image or factory image for that?
and what to sign over the app to save the data and the root and the twrp recovery?
thanks
I7210I said:
i got 404 page, but i found it and install it now everything is ok.
so about the flash fire which version i need for the security updates full ota image or factory image for that?
and what to sign over the app to save the data and the root and the twrp recovery?
thanks
Click to expand...
Click to collapse
New link
https://forum.xda-developers.com/showpost.php?p=73762462&postcount=282
I used the 019 OTA and flashed it after unrooting, and reverted to factory recovery. Kept ElementalX kernel and it worked like charm.
ok and for next updates, what to sign with the flashfire?and what to choose to download full ota image or factory image for that?
I7210I said:
ok and for next updates, what to sign with the flashfire?and what to choose to download full ota image or factory image for that?
Click to expand...
Click to collapse
I have always avoided OTA's and used the full Google image. They are usually available at the same time. I only select Boot, System & Vendor. It works every time without fail. It's never not worked across multiple Nexus devices. If there is a new bootloader or radio (modem) which is rare, I drop down to fastboot and flash those manually. FF is a Godsend for someone like me who has Nexus devices and updates monthly with security updates. My .02 cents.
v12xke said:
I have always avoided OTA's and used the full Google image. They are usually available at the same time. I only select Boot, System & Vendor. It works every time without fail. It's never not worked across multiple Nexus devices. If there is a new bootloader or radio (modem) which is rare, I drop down to fastboot and flash those manually. FF is a Godsend for someone like me who has Nexus devices and updates monthly with security updates. My .02 cents.
Click to expand...
Click to collapse
i assume you don't have TWRP?
I7210I said:
i assume you don't have TWRP?
Click to expand...
Click to collapse
Yes, I use TWRP. It is always preserved using FF.
so you need to preserve the recovery, isn't it?
I7210I said:
so you need to preserve the recovery, isn't it?
Click to expand...
Click to collapse
haha. yes, you use (select) the preserve recovery option. It makes a copy of your recovery partition (TWRP) so you don't lose your custom recovery. There is a FAQ on using FF here. Best of luck to you.
Thank you
hello guys
i am not getting any update after 7.10.14
can any one also facing it
i am rooted with magisk and also twrp is installed
i have also done no. of tweaks on my device
is there any solution to solve it
Red_Man 898 said:
hello guys
i am not getting any update after 7.10.14
can any one also facing it
i am rooted with magisk and also twrp is installed
i have also done no. of tweaks on my device
is there any solution to solve it
Click to expand...
Click to collapse
Same this side. I can see there is an update from the notifications. When I am clicking it.. its not opening.
Sent from my ONEPLUS A3003 using Tapatalk
When you install twrp, forget about updates. You need to flash full stock image using miflash application on Windows. I had the same problem, flashed stock images using miflash and update worked! I did not even lose my phone data.
Edit: Just boot into twrp to flash magisk. Don't flash twrp or system update will fill after downloading.
I was in the same situation (even if i've never flashed twrp).
Solved by flashing 17.10.30 Rom (after that I got the update)
Cheers.
tonycapuozzo said:
I was in the same situation (even if i've never flashed twrp).
Solved by flashing 17.10.30 Rom (after that I got the update)
Cheers.
Click to expand...
Click to collapse
How do I flash this version now ? I am already on 17.10.30
ProudRed said:
How do I flash this version now ? I am already on 17.10.30
Click to expand...
Click to collapse
Well...try re-flashing the same image or wait for the full November Rom.
Cheers
tonycapuozzo said:
Well...try re-flashing the same image or wait for the full November Rom.
Cheers
Click to expand...
Click to collapse
Just the boot image ? Where do I get the extracted boot image ?
If you have done multiple tweaks, I suppose that those were done to system directly. In such case you'll need to flash system partition as well. Both are included in full ROM, just extract them from archive http://en.miui.com/download-333.html.
https://www.youtube.com/watch?v=5Ozdhl-JdvU
give it a try.
If not getting updates (like: Your phone is already update) try to clean Google Service Framework app data from Settings - App - 3 dots on corner - Show system apps
If your device is rooted, then make clean installation of os. There will be ota update.
I am stock not rooted nor unlocked. Ad still stuck no more updates for me