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

How do I flash MMB29P

Sorry guys, I have been out of the loop with the Nexus 6p. I'm slightly new to the device. I am currently on MMB29M stock and rooted. I want to flash MMB29P, but I do no have a computer with a working adb. Where can I find a zip for stock MMB29P? Can I simply flash the new build with TWRP or does it have to be done with faceted images through adb? Also do I need to flash a vendor image.
Thanks in advance
Also is there a way I can update without having to wipe data?
Is there any real point for this update and will these "security updates" be happening each month?

http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Search

http://forum.xda-developers.com/nexus-6p/development/rom-optimized-stock-rom-debloated-t3285959

HerroMoto said:
Also do I need to flash a vendor image.
Click to expand...
Click to collapse
Yes. Vendor partition contains proprietary files that are necessary for the phone to function properly. Match the vendor to your rom's base.
Is there any real point for this update and will these "security updates" be happening each month?
Click to expand...
Click to collapse
Depends on whether you care for security updates. Yes, each month.
Sent from my Nexus 5X using Tapatalk

HerroMoto said:
Sorry guys, I have been out of the loop with the Nexus 6p. I'm slightly new to the device. I am currently on MMB29M stock and rooted. I want to flash MMB29P, but I do no have a computer with a working adb. Where can I find a zip for stock MMB29P? Can I simply flash the new build with TWRP or does it have to be done with faceted images through adb? Also do I need to flash a vendor image.
Thanks in advance
Also is there a way I can update without having to wipe data?
Is there any real point for this update and will these "security updates" be happening each month?
Click to expand...
Click to collapse
Try this: http://www.droidorigin.com/how-to-flash-factory-images-on-nexus-smartphones/

Guys thanks for the advice, but I cannot use adb, I am just looking for a zip to flash in recovery that I don't need to wipe data. I know how to set up adb but I cannot use it.

geoff5093 said:
http://forum.xda-developers.com/nexus-6p/development/rom-optimized-stock-rom-debloated-t3285959
Click to expand...
Click to collapse
Thank you I believe this is what I'm looking for

March Security update

Is up on Google developer website. MMB29V
https://dl.google.com/dl/android/aosp/shamu-mmb29v-factory-0b4a53f0.tgz
Edit: No change in bootloader or radio.

Thank you for upload. my work blocks google dl but not drive for some reason XD

Has anyone been able to get the checksum to verify? the MD5 for me doesn't match from the link provided or the Google image page.

just tried as well off the Google image page..MD5 does not match :|

I just downloaded from the stock images page also and the MD5 matches for me.

They just changed the MD5 code to match the factory image I downloaded. The new one matches my image.

How does one go about flashing this?
Flash all files through fastboot, except userdata.img?

murtaza02 said:
How does one go about flashing this?
Flash all files through fastboot, except userdata.img?
Click to expand...
Click to collapse
What build are you on now?

holeindalip said:
What build are you on now?
Click to expand...
Click to collapse
The February one. MMB29Q.
Unlocked bootloader
Not rooted.
Sent from my Nexus 6

murtaza02 said:
The February one. MMB29Q.
Unlocked bootloader
Not rooted.
Sent from my Nexus 6
Click to expand...
Click to collapse
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)

cam30era said:
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)
Click to expand...
Click to collapse
Will do and report back.
Stupid question, but does Google post changelogs?
Other than the security patch, could anything else have changed?
Sent from my Nexus 6

@murtaza02,
Not a stupid question, at all. Go here for answer > http://source.android.com/security/bulletin/2016-03-01.html

cam30era said:
@murtaza02,
Not a stupid question, at all. Go here for answer > http://source.android.com/security/bulletin/2016-03-01.html
Click to expand...
Click to collapse
That's some pretty detailed stuff!
Thanks man.
The factory image just finished downloading, I will report back in about 10 minutes.
Sent from my Nexus 6
---------- Post added at 07:17 PM ---------- Previous post was at 07:02 PM ----------
@cam30era
Thanks so much!
It worked. I flashed it and wiped cache in stock recovery. It's Optimizing apps now, and should be done soon!

cam30era said:
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)
Click to expand...
Click to collapse
That's what I was getting too just wanted to make sure he was at least on 6.0

@holeindalip @cam30era
The build date on the Kernel version changed. ( Kernel is boot.img right? )
When I was on MMB29Q, it showed Dec 10 2015
After MMB29V flash, it shows Jan 20 2016

murtaza02 said:
@holeindalip @cam30era
The build date on the Kernel version changed. ( Kernel is boot.img right? )
When I was on MMB29Q, it showed Dec 10 2015
After MMB29V flash, it shows Jan 20 2016
Click to expand...
Click to collapse
Kernel is included in boot.IMG with other files.

I compared md5 between mmb29q and mmb29v and boot, system and recovery seem different.
Noob question here:Is recovery different because I have twrp installed or shall I flash it too?

wrydgj said:
I compared md5 between mmb29q and mmb29v and boot, system and recovery seem different.
Noob question here:Is recovery different because I have twrp installed or shall I flash it too?
Click to expand...
Click to collapse
I think that boot.img should be flashed. I don't think that it will override your TWRP recovery.

harpin14789 said:
I think that boot.img should be flashed. I don't think that it will override your TWRP recovery.
Click to expand...
Click to collapse
I asked about recovery.img, I know that boot.img has to be flashed. Nevermind, I flashed both of them, just in case, and twrp after all flashes[emoji6]
Sent from my shamu using Tapatalk

What I find funny is that some of the patches are not even included in the update but in the updated binaries.
Also there were changes to the kernel. A few of the issues were kernel issues.

Rooted but can't install certain romd

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

no force encrypt on nexus 6p running mhc19i

Hi, can some one give me a guide on the nexus 6 p running mhc19i for no force encrypt, with either a system root that will allow me to remove apps, or a systemless root that I have to go through recovery, and is there a recovery for this version at this time other then the stock one

gigawatt said:
Hi, can some one give me a guide on the nexus 6 p running mhc19i for no force encrypt, with either a system root that will allow me to remove apps, or a systemless root that I have to go through recovery, and is there a recovery for this version at this time other then the stock one
Click to expand...
Click to collapse
To decrypt you need to format the userdata partition:
Code:
fastboot format userdata
This will obviously wipe your storage so back it up to your PC first. You will also need to flash a custom kernel that doesn't force encryption first otherwise the stock kernel will just encrypt again when you boot after formatting. You need to use TWRP recovery to flash SuperSU to get root. I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

yeh, is there a custom kernel for mhc19i

gigawatt said:
yeh, is there a custom kernel for mhc19i
Click to expand...
Click to collapse
Of course, there are many. Have you actually looked?

yes, I have looked, but most of them have an aroma installer, I am totally blind so I need one I can flash through fastboot as there is no talkback in aroma or recovery mode. Even the stock no force encrypt would be helpful thanks.

gigawatt said:
yes, I have looked, but most of them have an aroma installer, I am totally blind so I need one I can flash through fastboot as there is no talkback in aroma or recovery mode. Even the stock no force encrypt would be helpful thanks.
Click to expand...
Click to collapse
You can flash any of them via fastboot. Extract the boot.img from the zip and flash it:
Code:
fastboot flash boot boot.img
You'll just end up with the default settings. Why don't you just flash TWRP? Then you can install it the intended way.

I can flash twrp through fastboot, but I am totally blind and use a screen reader, so I would have to have some one around to use the twrp interface, since there is no speech there, so I need a kernel or modified no force encrypt boot.img I can flash through fastboot

gigawatt said:
I can flash twrp through fastboot, but I am totally blind and use a screen reader, so I would have to have some one around to use the twrp interface, since there is no speech there, so I need a kernel or modified no force encrypt boot.img I can flash through fastboot
Click to expand...
Click to collapse
Ahh, I see, that is definitely a difficult situation. So basically as I said, I believe any of them can be flashed via fastboot, but it isn't without its own work. You'd need to download the kernel zip, extract it, place the boot.img into your working directory (your fastboot folder), and use the "fastboot flash boot boot.img" command to flash it to the device. This will give you a kernel that doesn't force encryption, and you could then go on to use an app like Kernel Auditor to tweak the settings once you've booted into Android. How possible is this for you?

well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help

gigawatt said:
well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help
Click to expand...
Click to collapse
Apologies for the late reply, been a bit busy with my family. It looks like Franco is one of the kernels that doesn't have the boot.img directly inside the zip. There's probably a way to extract it but it's beyond my expertise. I'm in the process of extracting the boot.img from some other popular kernels for you now though, I'll update here once I have some uploaded. It might take a while because my upload speed is woefully slow.

gigawatt said:
well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help
Click to expand...
Click to collapse
Actually, it turns out none of the kernels have an easily accessible boot.img inside the zip. Things have changed since I last unpacked a kernel. I'll see what I can find out for you.

Here my friend use this thread. From @Tigerstown
https://tapatalk.com/shareLink?url=...share_tid=3306684&share_fid=3793&share_type=t
[UPDATED 3-10-16][Stock modified boot.img for regular root/Android N decrypted boot
It contains a stock modified boot image allowing system root and no force encryption. He updates thread for every build. Flash right from fastboot. If you need anything else feel free to PM me.
Sent from my Nexus 6P using Tapatalk

toknitup420 said:
Here my friend use this thread. From @Tigerstown
https://tapatalk.com/shareLink?url=...share_tid=3306684&share_fid=3793&share_type=t
[UPDATED 3-10-16][Stock modified boot.img for regular root/Android N decrypted boot
It contains a stock modified boot image allowing system root and no force encryption. He updates thread for every build. Flash right from fastboot. If you need anything else feel free to PM me.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.

Heisenberg said:
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.
Click to expand...
Click to collapse
Yes that's the correct link. I shared it from Tapatalk instead of web browser. Thank you for grabbing the correct one.
Sent from my Nexus 6P using Tapatalk

Heisenberg said:
Apologies for the late reply, been a bit busy with my family. It looks like Franco is one of the kernels that doesn't have the boot.img directly inside the zip. There's probably a way to extract it but it's beyond my expertise. I'm in the process of extracting the boot.img from some other popular kernels for you now though, I'll update here once I have some uploaded. It might take a while because my upload speed is woefully slow.
Click to expand...
Click to collapse
If they are using anykernel zip there is no boot.img.
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
Heisenberg said:
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.
Click to expand...
Click to collapse
I posted that thread in General. I should have posted in dev threads but less traffic the better for me answering the same questions over and over ??