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
Related
SINCE TWRP 3 THIS POST IS USELESS
Hi !
In this thread, you can find vendor.img from factory images in flashable zip format.
The zip will flash your vendor partition unconditionally (write_raw_image).
Flash it at your own risks
This is my first thread, be gentle plz
Thx to @BeansTown106 (Pure Nexus ROM) and Google
Update to MMB29Q vendor
Vendor from P and Q are the same in Nexus images...
gpvecchi said:
Vendor from P and Q are the same in Nexus images...
Click to expand...
Click to collapse
Not the same CRC (md5 or sha).
Can you explain plz ?
Blueblob said:
Not the same CRC (md5 or sha).
Can you explain plz ?
Click to expand...
Click to collapse
Sorry, my fault. I probably compared two times the same vendor.img. It's indeed different.
gpvecchi said:
Sorry, my fault. I probably compared two times the same vendor.img. It's indeed different.
Click to expand...
Click to collapse
We can do error, we are human.
Feedback is always a good thing.
I didn't compare img before your feedback, so next time I will do it, thx ?
Sent from my Nexus 5X using Tapatalk
What's so special about vendor.img so that we'll want to flash just this file?
ubcjack said:
What's so special about vendor.img so that we'll want to flash just this file?
Click to expand...
Click to collapse
Some people (myself included) are too lazy to download the factory image and extract the vendor.img and then flash it in fastboot and find it easier to flash in recovery.
Blueblob said:
Hi !
In this thread, you can find vendor.img from factory images in flashable zip format.
The zip will flash your vendor partition unconditionally (write_raw_image).
Flash it at your own risks
This is my first thread, be gentle plz
Thx to @BeansTown106 (Pure Nexus ROM) and Google
MDA89E vendor zip
MDB08I vendor zip
MDB08L vendor zip
MDB08M vendor zip
MMB29K vendor zip
MMB29P vendor zip
MMB29Q vendor zip
Click to expand...
Click to collapse
Sorry for this question, but what does the vendor file do exactly?
alwaysbelieve1 said:
Sorry for this question, but what does the vendor file do exactly?
Click to expand...
Click to collapse
The vendor partition contains proprietary drivers and such, if I understand correctly.
alwaysbelieve1 said:
Sorry for this question, but what does the vendor file do exactly?
Click to expand...
Click to collapse
Drivers and binaries from manufacturer (not open source).
Before 5X and 6P, it was mandatory to build Android (https://developers.google.com/android/nexus/drivers)
Now it's a dedicated partition.
Sent from my Nexus 5X using Tapatalk
added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up
Blueblob said:
MMB29Q vendor zip
Click to expand...
Click to collapse
When I booted the 2/4 nightly of CM13, I got the error about an "internal problem". Doing some searching, it said to flash the vendor.img that matched the build, which would be MMB29Q. When I flashed this zip, I still got the error. I pulled the vendor.img out of the stock image from google and flashed it with fastboot and now the error is gone. There is some sort of difference between this file and the google one.
psycho_asylum said:
When I booted the 2/4 nightly of CM13, I got the error about an "internal problem". Doing some searching, it said to flash the vendor.img that matched the build, which would be MMB29Q. When I flashed this zip, I still got the error. I pulled the vendor.img out of the stock image from google and flashed it with fastboot and now the error is gone. There is some sort of difference between this file and the google one.
Click to expand...
Click to collapse
Thx. Gonna check
Edit : Same CRC for vendor.img in my zip and zip from Google
Strange, maybe cache or something like that
Sent from my Nexus 5X using Tapatalk
Experienced same thing...
Looking for why
Haha ok, vendor partition needs to be mounted
You can do it in twrp
I'll will update files later
today's cm shows MMB29U in build.prop thus showing internal error message with Q
So...
My updater script doesn't work.
I'm investigating
Sent from my Nexus 5X using Tapatalk
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
No need to make a flashable zip anyway. We will able to flash vendor.img in twrp.
Sent from my Nexus 5X using Tapatalk
Is there any way to check which vendor image is installed?
Edit 1: Nevermind, found it under vendor/build.prop
Thanks for this, saves me from downloading a whole img.
Edit 2: Doesn't seem to work, even when I mount the vendor partition in twrp it doesn't seem to properly flash it. Any advice?
I gonna ask a mod to close my thread
I will find another way to contribute to community with my skills ?
Sent from my Nexus 5X using Tapatalk
Hi All,
I have unlocked my Nexus 6P and flashed it with customized framework. After that I locked my device. At the first reboot, the warning is displayed in "YELLOW" color but subsequent reboots are showing warning message in "RED" color instead of "YELLOW". Can anyone explain the reason, why the message is displaying RED for subsequent reboot.
My second issue , I am unable to use finger print scanner for custom framework. How can I use it for custom framework. Is there any binaries are needed ?
Are you talking about Xposed Framework??
Sent from my Nexus 6 using Tapatalk
Flash matching vendor using fastboot and it will go away.
Edit added:
More info. What are you talking about? Custom framework?? Details, installation process you used. More info, better help.
Sent from my Nexus 6P using Tapatalk
SM210 said:
Flash matching vendor using fastboot and it will go away.
Edit added:
More info. What are you talking about? Custom framework?? Details, installation process you used. More info, better help.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thank you SM210 for your replay. We have downloaded the AOSP 6.0.1_r14 (angler-mmb29q) and compiled for Nexus 6P. We unlocked the device and flashed these images ( system.img, boot.img, recovery.img, cache.img & userdata.img) on the mobile. we are testing two features
verified boot
finger print sensor
Verified boot
Once the images are flashed, we locked the device. At the first reboot, verify boot is displaying "YELLOW" color . "YELLOW" color means device has a different operating system than the one that originally came on your device. Until this point everything is fine. If I reboot the device again, it should display the same warning in "YELLOW" color as it is a different OS than the one that original came. But subsequent reboots, verified boot is displaying the warning in "RED" color. How to over come this issue ?
Finger print sensor
After the images are flashed, Nexus Imprint option is not present in Security settings. How to use finger print scanner in compiled AOSP ?
vendor.img for mmb29q must be fastboot flashed and when it is the red message will go away. It's in the factory image from Google. Just extract and flash it via fastboot then reboot and red message will stop.
Here is vendor.img for mmb29q https://www.androidfilehost.com/?fid=24399994186367251
I flashed latest yesterday which is mmb29v from Google factory image. Not sure if you know there's newer image out than mmb29q...
Sent from my Nexus 6P using Tapatalk
SM210 said:
Flash matching vendor using fastboot and it will go away.
Edit added:
More info. What are you talking about? Custom framework?? Details, installation process you used. More info, better help.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hey I have a question about the vendors. So I I flash the vendor IMG from FASTBOOT my annoying error message will be gone for good? Previously I used beanstown106 vendor files which I flashed through TWRP. That method got rid of the annoying pop up at boot up saying your security is outdated and what not.
Sent from my Nexus 6P using Tapatalk
krazy_smokezalot said:
Hey I have a question about the vendors. So I I flash the vendor IMG from FASTBOOT my annoying error message will be gone for good? Previously I used beanstown106 vendor files which I flashed through TWRP. That method got rid of the annoying pop up at boot up saying your security is outdated and what not.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No the red message, if you have it (the red one) will go away. Its caused because of not having matching vendor.
Sent from my Nexus 6P using Tapatalk
I'm Stock rooted latest twrp, but can install aosp based Roms, well it lets me install the Roms but no gapps package works none of them.
Forgot the error something about modified image needed.
Just trying to install an aosp based ROM not sure what's going on.
Sent from my Nexus 6P using Tapatalk
humdrum2009 said:
I'm Stock rooted latest twrp, but can install aosp based Roms, well it lets me install the Roms but no gapps package works none of them.
Forgot the error something about modified image needed.
Just trying to install an aosp based ROM not sure what's going on.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you can get an exact copy of the error message and post it here it'll help us figure out whats going on (hopefully). Also, What version of twrp are you using?
humdrum2009 said:
I'm Stock rooted latest twrp, but can install aosp based Roms, well it lets me install the Roms but no gapps package works none of them.
Forgot the error something about modified image needed.
Just trying to install an aosp based ROM not sure what's going on.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Having root has nothing to do with the ability to flash ROMs, you might be a bit confused about that. You need to provide more information too please:
1. What ROMs have you tried?
2. Exactly what gapps have you tried?
3. Are you making sure you flash the correct corresponding vendor image to go with the ROM build?
4. Exactly what error(s) are you getting?
Messgaes on failure
when i reboot i get your system cant be checked for corruption,please lock boot loader.
after twrp starts i try and flash dirty unicorn,i think i am missing a step
error says
update process ended with error 7
error installing zip file /sdcard/DU_TBO_GAPPS_3.1 ZIP
Okay dirty unicorn boots with the message flash updated vendor image.
humdrum2009 said:
when i reboot i get your system cant be checked for corruption,please lock boot loader.
after twrp starts i try and flash dirty unicorn,i think i am missing a step
error says
update process ended with error 7
error installing zip file /sdcard/DU_TBO_GAPPS_3.1 ZIP
Okay dirty unicorn boots with the message flash updated vendor image.
Click to expand...
Click to collapse
if someone could point me to the vendor images i can fla**** in fastboot latest updated build
humdrum2009 said:
if someone could point me to the vendor images i can fla**** in fastboot latest updated build
Click to expand...
Click to collapse
Here: https://www.androidfilehost.com/?w=files&flid=49333
Thanks to BeansTown106
Werid couldn't flash vendor image in fastboot ,neither with adb or wugfresh
I just went back to stock rooted for the time being. That link you provided if dead 404. I found it elsewhere on XDA going to try dirty u again in a few minutes wish me luck lol.
Sent from my Nexus 6P using Tapatalk
I recently, yesterday, flashed a 7.1 from to my phone. Actually both that at available, and both times I am getting this error message on boot. I'm not sure what I'm doing wrong. Phone seems to run well though. Help? Thanks!
It's in the attachment
I'd be curious to know aswell..
Sent from my ONE A2003 using Tapatalk
I had this same issue awhile back but somebody told me what to do and it went away..
For the life of me I can't remember what it was .
I'm thinking it had something to do with Vendor but can't remember
Sent from my Pixel XL using Tapatalk
Did you update the vendor image after flashing the ROM?
wwe9112 said:
I recently, yesterday, flashed a 7.1 from to my phone. Actually both that at available, and both times I am getting this error message on boot. I'm not sure what I'm doing wrong. Phone seems to run well though. Help? Thanks!
It's in the attachment
Click to expand...
Click to collapse
Just flash the vendor image to the corresponding build. Ex: build NBD90X needs the NBD90X vendor image and so on. Should resolve the issue.
BIGSAMDA1ST said:
Just flash the vendor image to the corresponding build. Ex: build NBD90X needs the NBD90X vendor image and so on. Should resolve the issue.
Click to expand...
Click to collapse
Now I'm stuck elsewhere, I decided to do a full flash -_-. I formatted everything not thinking and now I have no rom on my device. I think I am stuck. Is there a way to transfer a rom to my device? I used TWRP to format my device.
Boot into fastboot mode, unlock the bootloader, and flash the latest factory image...
https://developers.google.com/android/images?hl=en
redduc900 said:
Boot into fastboot mode, unlock the bootloader, and flash the latest factory image...
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Fastboot just says to connect a USB Cable but it's connected. I have drivers installed. I don't have a rom obviously to enable USB debugging -_-.
If u have TWRP just boot to recovery then plug in the phone to computer and a window will pop up showing Internal Storage and jus copy a ROM/Gapps/Vendor to Internal Storage and then select Install and flash away.
Sent from my Pixel XL using Tapatalk
scoot0073 said:
If u have TWRP just boot to recovery then plug in the phone to computer and a window will pop up showing Internal Storage and jus copy a ROM/Gapps/Vendor to Internal Storage and then select Install and flash away.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I got it! I had to use another pc for some reason; my main pc wasn't recognizing it but my laptop did -_-. Anyway, where do I find the vendor image? Also how do I flash that, I remember a while back I found one and went to flash it and there was several radio buttons on where to flash it. I don't want to screw this up lol.
Thank you so much.
Post#2 on first page
(How to install a ROM)
Read it more easier than me typing it all out..haha
http://forum.xda-developers.com/showthread.php?t=3206928
Sent from my Pixel XL using Tapatalk
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