Hi guys,
I've seen this question asked a few times, but no one ever answers it. I tried looking around on other sites, but can't seem to find an answer.
I just came over from a Galaxy S5, and I don't think we ever used those. Is there anybody who'd be willing to point me in the direction of knowing?
It holds proprietary binaries for the Nexus 5x, 6p and 9, from what I've read.
Hey OP, did you find out what a vendor.img is yet? Have also come to Nexus from Samsung. Flashing my first rom, and don't know what this vendor file is. Or if I even need it. Like you, have found threads where people ask, but no definitive answers...
I've been curious about this, too.
Also wondering how the Vendor partition differs from System. What do the data/functions in the Vendor partition do?
EFS partition seems to be specific to the individual device (unique IMEI). Is Vendor specific to each phone too, or do all Nexus 6Ps have the same thing in the Vendor partition (assuming they're on the same build of Android)?
The vendor.img is important to this device if you upgrade your OS. You might have to flash it with every update too or your camera won´t work. This IMG is indeed strange if you´re used to older devices which are not as complicated.
Gorgtech said:
The vendor.img is important to this device if you upgrade your OS. You might have to flash it with every update too or your camera won´t work. This IMG is indeed strange if you´re used to older devices which are not as complicated.
Click to expand...
Click to collapse
OK cool, so the vendor file is Nexus specific. And the OS won't operate properly without it? So I assume it's not possible to bake the vendor file straight into a custom rom? Just flashed pure nexus vendor.img along with the rom. Still not exactly sure what it does, but hey, if I need it, I'll flash it if I change roms.
Gorgtech said:
The vendor.img is important to this device if you upgrade your OS. You might have to flash it with every update too or your camera won´t work. This IMG is indeed strange if you´re used to older devices which are not as complicated.
Click to expand...
Click to collapse
Supplemental information about Vendor from a former member of the Android team
SlimSnoopOS said:
Supplemental information about Vendor from a former member of the Android team
Click to expand...
Click to collapse
Thanks for the link. So from my understanding, all the proprietary nexus files are stored on it's own 'vendor' partition, separate from the OS. And is updatable with it's own .img. Which is different to touchwiz (for eg.), which merges it's own files with android into the one partition.
Edit: FYI, just found this in PureNexus FAQ's:
Q: What is the vendor.img/vendor.zip? (5X and 6P only)
A: The vendor partition is new to Nexus phones with the 5X and 6P. Previous devices had the vendor files (proprietary binaries and drivers) within the system partition (/system/vendor); on these devices, they now have it in their own partition (/vendor). If this is not up to date, you will get an error message and need to flash the latest one so your phone continues to work properly. Beans has made this a TWRP flashable file available in the OP of the 5X and 6P threads (also linked below) so you do not have to fastboot it.
I'm a bit late on this one, but does anyone know if updating OTA (stock android updater) updates the vendor partition as well or do you specifically have to flash it?
So, with this partition for drivers ROMs can keep the same camera quality as stock?
Llaver said:
I'm a bit late on this one, but does anyone know if updating OTA (stock android updater) updates the vendor partition as well or do you specifically have to flash it?
Click to expand...
Click to collapse
No, the vendor.img does not need to be flashed independently of the OTA update.
I have seen it in many phones other than mentioned in the thread, it is even in infinix phones. what i think is it contains apps from google like maps, drive, gmail, photos, and also some apps from the manufacturer of the phone. why i think this is the case? here is the my guess.
yesterday when i tried to remove google bloatware and manufacturer bloatware with root permissions etc. it didn't work.
i have magisk root, i had set selinux permissive as someone told me it would help BUT i was still unable to remove bloatware. they were removed for now but whenever i rebooted my phone, they were reinstalled and i think this vendor file does that.
as per google's android documents here is the difinitoin.
vendor: The vendor partition contains any binary that is not distributable to the Android open source project.
means, google apps are never distributed with AOSP but manufacturers does that via vendor.img to make it non-removable? i guess.
jameeldroid said:
I have seen it in many phones other than mentioned in the thread, it is even in infinix phones. what i think is it contains apps from google like maps, drive, gmail, photos, and also some apps from the manufacturer of the phone. why i think this is the case? here is the my guess.
yesterday when i tried to remove google bloatware and manufacturer bloatware with root permissions etc. it didn't work.
i have magisk root, i had set selinux permissive as someone told me it would help BUT i was still unable to remove bloatware. they were removed for now but whenever i rebooted my phone, they were reinstalled and i think this vendor file does that.
as per google's android documents here is the difinitoin.
vendor: The vendor partition contains any binary that is not distributable to the Android open source project.
means, google apps are never distributed with AOSP but manufacturers does that via vendor.img to make it non-removable? i guess.
Click to expand...
Click to collapse
????? This is a nexus, it contains no bloat because its a google device, its not a Motorola , lg, samjunk etc. Those devices contain "bloat" there are zero applications installed from the mfg, its stock android.
Not sure why you can't remove system apps, sounds like user error. I have never had an issue removing something with root and titanium backup.
The vendor contains what it says it does the binarys, blobs and other interworking's of the device that are needed for it to operate.
Hello. I'm a new to Android world. I have a Moto G4 (XT1622) and I install AOSiP-8.1-Derp-athene-20180501/Android Open Source Illusion Project ROM (arm64).
I see 'your vendor image does not match the system' message on every boot with a prompt to flash npjs25.93-14-13.
I download latest Nougat ROMs (arm32) (both adb and twrp flashable). Try both methods of flashing with success.
Then I install custom ROM again (with TWRP, clean) and see the same message again.
I search regarding this problem and everything ends with flashing Stock ROM and perform installing custom one again, what I done and mention of vendor.img file.
I try to find such file but no luck, my device has only vendor folder.
So my question is: how to remove this message in the custom ROM?
I post it here because ROM's thread is closed
Thanks.
Hi all,
I've been doing a lot of experimenting with my new 6P and have really enjoyed running Pure Nexus in place of the stock ROM on it. But the thing is, I bought the 128 GB version mainly because I was interested in experimenting with several different ROMs concurrently. I've used MultiROM in the past with no difficulty and right now I have it installed along with TWRP 3.0.2-0--the latest I could find with MultiROM support.
The problem is, I've been able to successfully install only a few secondary ROMs, either because flashing fails or I can't get them to boot after a successful flash. I suspect that this has to do with a mismatched vendor image, because the one I flashed for PN, I presume, is what any secondary is forced to look to, because MultiROM functionality apparently doesn't extend to multiple vendor images.
Am I correct about the way MultiROM works in this instance? Is there a workaround that would allow me to run ROMs that rely on different vendor images?
Thanks!
KT71
KilgoreTrout71 said:
Hi all,
I've been doing a lot of experimenting with my new 6P and have really enjoyed running Pure Nexus in place of the stock ROM on it. But the thing is, I bought the 128 GB version mainly because I was interested in experimenting with several different ROMs concurrently. I've used MultiROM in the past with no difficulty and right now I have it installed along with TWRP 3.0.2-0--the latest I could find with MultiROM support.
The problem is, I've been able to successfully install only a few secondary ROMs, either because flashing fails or I can't get them to boot after a successful flash. I suspect that this has to do with a mismatched vendor image, because the one I flashed for PN, I presume, is what any secondary is forced to look to, because MultiROM functionality apparently doesn't extend to multiple vendor images.
Am I correct about the way MultiROM works in this instance? Is there a workaround that would allow me to run ROMs that rely on different vendor images?
Thanks!
KT71
Click to expand...
Click to collapse
It sounds like you might be right about the vendor image. There is only one partition for the vendor image and whatever rom you run will use the vendor image that is flashed in that partition.
Hi everyone! As the title says I'm trying to dualboot my Nexus 6P with Oreo and Nougat. I'm trying to achieve this because I want to have Nethunter on my Nexus 6P over 7.1.2 while keeping an updated ROM as primary.
After so many trial and error I managed to succesfully install both Oreo (Lineage 15.1) as primary ROM and Nougat (PureNexus 7.1.2) with Nethunter as data ROM.
The only "problem" that I'm still trying to solve is: I have to flash the Nougat's vendor whenever I want to boot to my Nethunter ROM and flash back to Oreo's vendor when I want to get back to my Oreo ROM.
As you have noticed, this is both inconvenient and impractical at the same time. So what I've been looking for is a way to flash the vendor image on the fly after rebooting the device but before the ROM gets loaded by.
What I've found so far is that I can use OpenRecoveryScript (though I've been unable to find how to use it) to load an script with twrp.
If someone has any idea on how to achieve this I'd be totally grateful.
PD: If someone wants any help to get the same or similar setup as I've done just ask (Didn't explain here just to keep the post simple)
Hello!
Just unlocked my mi 9t and installed magisk. So far it's working great but I really want to try a custom rom because I don't really like miui.
Now I came from a oneplus 3t that has simple zip files to install roms. Now I see for this device you have gsi roms. My question is do I need to flash vbmeta and how would I go about doing that? Is it device specific? Or is the one in the xda tutorial universal?
Thanks!
They are different.
GSI are for all (or most) of devices (treble-enabled).
Zipped ROMs are device specific.
We still don't have "normal" roms because developers haven't get this phone. So, for now, we have to use GSI.
Some people think vbmeta is specific, but actually, at least for GSI roms, it's universal.
You can flash it using fastboot mode and CMD/Terminal or if TWRP allow it, flash from there.
Hi, I want to install TWRP on my phone, but it requires flashing vbmeta. I can find all kinds of links on xda, as well as one from Google's official GSI image.
I'm a little paranoid about the security issue on flashing random vbmeta on the machine, so my question is: is the vbmeta from google generic and can be flash to any arm device, or I have to use the one from 9t forum? Thanks!
ccaappton said:
Hi, I want to install TWRP on my phone, but it requires flashing vbmeta. I can find all kinds of links on xda, as well as one from Google's official GSI image.
I'm a little paranoid about the security issue on flashing random vbmeta on the machine, so my question is: is the vbmeta from google generic and can be flash to any arm device, or I have to use the one from 9t forum? Thanks!
Click to expand...
Click to collapse
Install the official TWRP, no wiping, flashing VBMeta or anything needed (QFJEUXM 11.0.4):
https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Every time you boot to TWRP, enter the same pin you are using when you boot to Android or you use there for unlocking the screen