Database Users

Question on vendor img and flashing.

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

Updating TWRP via TWRP n recovery

I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk

A bad flash, perhaps? Have you checked the MD5 after downloading?

Possible bad download but at this point I can't reflash the recovery until I can fast boot .. I gotta order another Type C to USB to connect the phone to the computer for fast boot grrrrr...
Thx
Sent from my Nexus 6P using Tapatalk

Glad to help! Next time make sure you check MD5 before flashing (even then an occasional bad flash could still cause trouble, but hey, what's the choice here?) You can still boot to Android normally, no?
Sidenote: anyone knows if a micro B to C adaptor would work with fastboot?

Yeah I can still boot to Android fine jus when I select recovery n bootloader it hangs in bootloader. I have to hard reset to get out of bootloader mode lol....
Jus sucks BC now I gotta wait until friday to order a Type C to USB cable to use the computer to fast boot TWRP to recovery.. :/
I jus got this 6P 4 days ago coming from the HTC M9 Developer Edition I decided to go with the 6P over the M10 even though I would have gotten $100 off the M10 for not using my UhOh protection.
But I'm currently Stock w/ root until I figure out or understand this whole Vender thing when flashing Roms.. Jus being very cautious.
With HTC you jus flash the ROM you want but here some say jus flash the ROM and some say flash the Vender matching the ROM.. Lol,..
Sent from my Nexus 6P using Tapatalk

About the vendor img... Not too sure about the whole technical details behind them, but I just flash them every time Google updates them (think monthly security updates), at the very least to get rid of the 'vendor img outdated' popup. You don't need to flash a new vendor img everytime you update/switch ROMs, but only when there's a new vendor.

I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app

scoot0073 said:
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
People have been facing the same issue all around. Even I did, last night after updating to N Preview. Anyhow, the only solution I know right now is to have a decrypted filesystem (disable encryption), for TWRP to boot and work properly.

Yeah disable encryption I believe I read requires booting into recovery and wiping User Data or something alone those line's.
Unless there's a option in Android settings to disable it idk yet as I jus had the phone a few day's.
But so far I happy with my decision to get the 6P over the M10 even if the 6P is 4 or 5 moths old...
Sent from my Nexus 6P using Tapatalk

OK I got the latest TWRP Recovery flash . I used Flashify app and it flashed the recovery and I got a working recovery now..
Sent from my Nexus 6P using Tapatalk

Pain-N-Panic said:
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank u so much that fixed my borked recovery thank you again
Sent from my Nexus 6P using Tapatalk

Error message

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

developer preview 2 is out now, how do I flash without losing everything?

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

Installing OTA 7.1.2 whilst having TWRP installed caused soft brick.

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

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

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

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

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

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

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

Did you have the Pixel modifications?

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

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

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

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

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

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

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

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

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