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
Related
I was wondering if anyone has an answer. I got my 6p yesterday and used skipsofts nrk to unlock and root the 6p. All fine and i am still getting the beginning splash screen saying device corrupt. I was reading in the purenexus rom thread and it said to flash the mdb08m vendor img. When I rooted I was and still am on Mdb08l. Am I able to flash that vendor img on the L or do I need to go up to M? Also is there a link or something on how to flash a vendor img and also where I would find it?
Sent from my Nexus 6P using Tapatalk
jeff5347 said:
I was wondering if anyone has an answer. I got my 6p yesterday and used skipsofts nrk to unlock and root the 6p. All fine and i am still getting the beginning splash screen saying device corrupt. I was reading in the purenexus rom thread and it said to flash the mdb08m vendor img. When I rooted I was and still am on Mdb08l. Am I able to flash that vendor img on the L or do I need to go up to M? Also is there a link or something on how to flash a vendor img and also where I would find it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hey! Thanks for posting! I would like to know this as well.
The corrupt device message is because you need to completely wipe everything (factory reset including wiping user data). The vendor mismatch error is different.
Sent from my Nexus 6P using XDA Free mobile app
akellar said:
The corrupt device message is because you need to completely wipe everything (factory reset including wiping user data). The vendor mismatch error is different.
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Pretty certain he means the message that says "cannot check device FOR corruption..."
ohlin5 said:
Pretty certain he means the message that says "cannot check device FOR corruption..."
Click to expand...
Click to collapse
That message is apparently part of the bootloader and cannot be removed. At least nobody has found a way yet. It isn't indicating an issue either though, just that the bootloader is unlocked.
Edit: just realized I can't read and that has nothing to do with the original question. You flash the vendor image in fastboot with the command "fastboot flash vendor vendor.img" The vendor image version needs to match the build you are running.
Sent from my Nexus 6P using XDA Free mobile app
I flashed via fastboot last night the m vendor IMG. I had already dl'd purenexus which is on m and gapps. Flashed the vendor in FB then went to recovery and wipe everything minus internal storage then flashed PN and gapps. All is working great just that initial corrupt screen appears. So as of now there's no way to get rid of it?
Sent from my Nexus 6P using Tapatalk
jeff5347 said:
I flashed via fastboot last night the m vendor IMG. I had already dl'd purenexus which is on m and gapps. Flashed the vendor in FB then went to recovery and wipe everything minus internal storage then flashed PN and gapps. All is working great just that initial corrupt screen appears. So as of now there's no way to get rid of it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Correct
Sent from my Nexus 6P using XDA Free mobile app
I have a Nexus 6 (shamu) and to get rid of that message, you need a custom kernel that has the "dm verity" removed. Does this not apply for the 6P? Just throwing this bit if info out there.
H4X0R46 said:
I have a Nexus 6 (shamu) and to get rid of that message, you need a custom kernel that has the "dm verity" removed. Does this not apply for the 6P? Just throwing this bit if info out there.
Click to expand...
Click to collapse
on the 6p it's coded inside the bootloader.
Abaddon said:
on the 6p it's coded inside the bootloader.
Click to expand...
Click to collapse
WOW! Thanks! That's something!
I'm struggling to understand how to change vendor into my nexus 6P due to the fact that I have now NDE63X vendore but I'm not able to replace with nothing different. I mean that I was trying to flash Benzo rom that needs NBD90X but I was not able to flash it though TWRP neither FB, now I would try Resurrection Remix but it's the same....the build no I have at the end of the flashing is still NDE63X.
I'm going crazy with this, I'm felling a dude (as I am) but can someone explain what is missing in my understanding?
akellar said:
That message is apparently part of the bootloader and cannot be removed. At least nobody has found a way yet. It isn't indicating an issue either though, just that the bootloader is unlocked.
Edit: just realized I can't read and that has nothing to do with the original question. You flash the vendor image in fastboot with the command "fastboot flash vendor vendor.img" The vendor image version needs to match the build you are running.
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
The corruption message is just a badge of honor [emoji3]
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------
mickjmickj said:
I'm struggling to understand how to change vendor into my nexus 6P due to the fact that I have now NDE63X vendore but I'm not able to replace with nothing different. I mean that I was trying to flash Benzo rom that needs NBD90X but I was not able to flash it though TWRP neither FB, now I would try Resurrection Remix but it's the same....the build no I have at the end of the flashing is still NDE63X.
I'm going crazy with this, I'm felling a dude (as I am) but can someone explain what is missing in my understanding?
Click to expand...
Click to collapse
When you download the correct vendor image you need can use twrp to do it. When your in twrp and St the install screen it's on the bottom right of the screen I believe it says "flash image". Lmk if this helps
Sent from my Pixel XL using XDA-Developers mobile app
bigmatt503 said:
The corruption message is just a badge of honor [emoji3]
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------
When you download the correct vendor image you need can use twrp to do it. When your in twrp and St the install screen it's on the bottom right of the screen I believe it says "flash image". Lmk if this helps
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
You realize you quoted a post from over a year ago, right?
Mickjmickj asked his question 1 day ago. What was the point of your post? The guy asked a question YESTERDAY and I tried to help. So yes, the original post was a year old.
Sent from my Pixel XL using XDA-Developers mobile app
akellar said:
You realize you quoted a post from over a year ago, right?
Click to expand...
Click to collapse
It seems someone reply as well
bigmatt503 said:
The corruption message is just a badge of honor [emoji3]
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------
When you download the correct vendor image you need can use twrp to do it. When your in twrp and St the install screen it's on the bottom right of the screen I believe it says "flash image". Lmk if this helps
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
I did in that way and furthermore with fastboot but I'm still with the same vendor.
Now I'm with Resurrection Remix using NDE63X
All seems running fine but I've not learned anything new.
vendor image when and why
Okay new to 6p here is my question if i flash say purenexus and my vendor is prior to n4f226i and i flash purenex. do i need to flash the vendor to match that build
i know how to flash it i however did try just that after i did in recovery i got a /vendor dose not exist and had to reflash to factory and start over again ahh
i got it now nevermind
kentek said:
Okay new to 6p here is my question if i flash say purenexus and my vendor is prior to n4f226i and i flash purenex. do i need to flash the vendor to match that build
i know how to flash it i however did try just that after i did in recovery i got a /vendor dose not exist and had to reflash to factory and start over again ahh
i got it now nevermind
Click to expand...
Click to collapse
For anyone in the future that finds this thread, answer lies below:
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning indicates a mismatched vendor and system partition. The vendor partition was integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS build and monthly security update. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line. These will always match up with the factory image of the same Android build (six digit numerical/alphabetical name) for this device.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone. If you are a custom rom user, make sure that you flash the vendor.img for the Google monthly security update that you are moving to. Be aware that sometimes AOSP roms utilize the AOSP master branch that has a newer Android build than the monthly security update for this device. You will still need to install that month's vendor.img.
The phone will fail to boot if you mismatch the vendor.img with a different Android version. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat. The vendor.img is typically not included in the custom rom zip but is often available as a separate download.
Click to expand...
Click to collapse
kentek said:
Okay new to 6p here is my question if i flash say purenexus and my vendor is prior to n4f226i and i flash purenex. do i need to flash the vendor to match that build
i know how to flash it i however did try just that after i did in recovery i got a /vendor dose not exist and had to reflash to factory and start over again ahh
i got it now nevermind
Click to expand...
Click to collapse
You flashed the vendor image in recovery? Did you choose the correct partition to flash it to? I've flashed the vendor multiple times in TWRP but never got an error message like the one you are describing. Where did you get your vendor image from?
jhs39 said:
You flashed the vendor image in recovery? Did you choose the correct partition to flash it to? I've flashed the vendor multiple times in TWRP but never got an error message like the one you are describing. Where did you get your vendor image from?
Click to expand...
Click to collapse
wrong vendor image user screw up I got it runs great now with ex kernel substrate thank you for the reply
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
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...
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
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
I7210I said:
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
Click to expand...
Click to collapse
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
funnel71 said:
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
Well keep in mind at the moment I am not rooted. As for updates when I used to be rooted I would flash the stock images for the system recovery bootloader and vendor partitions first. After that was done route would be erased and I could take the OTA update. I should also mention that I have not updated to Oreo. Given the hardware difficulties with my phone I've chosen to stay at 7.1.2
Sent from my Nexus 6P using Tapatalk
so...i'm in 8.1 and these is the conclusion in that state after few tests.
I7210I said:
so...i'm in 8.1 and these is the conclusion in that state after few tests.
Click to expand...
Click to collapse
I would tend to agree with you either you have a version that is not compatible with 8.1 or perhaps you just downloaded a corrupted zip file. I can't speak for root on 8.1 because I don't have that version but I think you've done enough testing to prove your theory that it's the zip that cause your boot loop
Sent from my Nexus 6P using Tapatalk
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
stankyou said:
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Use Magisk it's latest greatest. Just install the Magisk app from apkmirror and it will prompt to download flaahable zip. As far as TWRP 3.2.1-0 I believe is latest.
I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
What are you trying to say? The bootloop you are talking about is different from hardware bootloop of death in nexus 6p.
Supersu works fine for everyone,if its bootlooping for you thn you are doing something wrong or flashing wrong supersu zip.
The most of the reported bootloop of death users are not rooted.
the twrp is 3.2.1 and i used now the Magisk and it works.
the way i used is :
fastboot format userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery <filename>.img
fastboot flash system system.img
Fastboot flash vendor vendor.img
ofcurse with the right names of files..