Related
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.
Hello everyone. So I'm brand new to not only xda but rooting and the likes all together. Yesterday I rooted my nexus 6p without issue and I will now list what I used. Twrp 3.0.0 -1-angler, BETA-SuperSU-v2.67-20160121175247. My phone build was MMB29P. then I flashed on pure_nexus_angler-6.0.1-20160315-CMTE and PureNexus_Dynamic_GApps_6.x.x_3-15-16.zip. Now my phone is saying its build MHC19J. I don't know if that is normal, but now I'm confused. When I boot up I get an Android System message saying " It appears your vendor image may be out of date. Please flash the latest vendor image for your device. " So followed the link to the vendor images and I see the list of vendor images however I don't see my build MHC19J.. or am I to get MMB29P? also once I do get it downloaded and load up twrp I see the option to click image and there's several boxes there to check/uncheck.. Do i just check vendor? So put as short as possible I need to know which vendor image i should get and how to flash it from twrp. Thanks for reading and your help will be greatly appreciated.
Also I almost forgot.. Will i need to flash a raido file or anything like that??
Read this first: http://forum.xda-developers.com/showpost.php?p=64399854
Then read this: http://forum.xda-developers.com/showpost.php?p=65102741&postcount=7741
The answers to your question are both in those links, which you should ALWAYS read. You'll thank me later for making you read those.
Danzilla79 said:
Hello everyone. So I'm brand new to not only xda but rooting and the likes all together. Yesterday I rooted my nexus 6p without issue and I will now list what I used. Twrp 3.0.0 -1-angler, BETA-SuperSU-v2.67-20160121175247. My phone build was MMB29P. then I flashed on pure_nexus_angler-6.0.1-20160315-CMTE and PureNexus_Dynamic_GApps_6.x.x_3-15-16.zip. Now my phone is saying its build MHC19J. I don't know if that is normal, but now I'm confused. When I boot up I get an Android System message saying " It appears your vendor image may be out of date. Please flash the latest vendor image for your device. " So followed the link to the vendor images and I see the list of vendor images however I don't see my build MHC19J.. or am I to get MMB29P? also once I do get it downloaded and load up twrp I see the option to click image and there's several boxes there to check/uncheck.. Do i just check vendor? So put as short as possible I need to know which vendor image i should get and how to flash it from twrp. Thanks for reading and your help will be greatly appreciated.
Also I almost forgot.. Will i need to flash a raido file or anything like that??
Click to expand...
Click to collapse
The vendor version you need is MHC19I which you can download following the link on the first post on the pure nexus ROM. Flash it via TWRP by hitting the flash img button and then selecting the vendor partition (duh). It's also good to make sure you are running the latest bootloader and radio (the bootloader should be on version 3.51 and the radio on 3.61).
I just got my N6P and am coming from the N6 and I have to say I love this phone. I unlocked and rooted my N6P right away. I am no stranger to root and custom Roms. Right now I am on the stock ROM because something is throwing me off a little.
What is the deal with the vendor images? The N6 didn't have them (at least you didn't have to mess with them when you flashed a ROM). My question is this, do you have to flash a vendor image in fastboot each time you flash a ROM? I want to flash some Roms, but until I know more about the vendor images I am holding off on any flashing.
Sent from my Nexus 6P using XDA-Developers mobile app
You only need to flash the vendor image once per new build number. So say you are on a ROM with build XXXXXX and you are updating to YYYYYY. You still flash the ROM then the YYYYYY vendor image. If there is another ROM you want to try on YYYYYY, you don't have to flash the YYYYYY vendor image again.
The vendor image files are a bunch of proprietary binaries and drivers that allow your phone to run properly. These vendor files were originally in /system on all previous Nexus devices but starting with the Nexus 9, they were moved to their own partition, /vendor. Super convenient for ROM developers since they no longer have to include those files from the factory images; instead, people can just flash the images directly from Google.
nathanchance said:
You only need to flash the vendor image once per new build number. So say you are on a ROM with build XXXXXX and you are updating to YYYYYY. You still flash the ROM then the YYYYYY vendor image. If there is another ROM you want to try on YYYYYY, you don't have to flash the YYYYYY vendor image again.
The vendor image files are a bunch of proprietary binaries and drivers that allow your phone to run properly. These vendor files were originally in /system on all previous Nexus devices but starting with the Nexus 9, they were moved to their own partition, /vendor. Super convenient for ROM developers since they no longer have to include those files from the factory images; instead, people can just flash the images directly from Google.
Click to expand...
Click to collapse
Thank you for your reply. That makes sense. I appreciate it very much.
Sent from my Nexus 6P using XDA-Developers mobile app
nathanchance said:
You only need to flash the vendor image once per new build number. So say you are on a ROM with build XXXXXX and you are updating to YYYYYY. You still flash the ROM then the YYYYYY vendor image. If there is another ROM you want to try on YYYYYY, you don't have to flash the YYYYYY vendor image again.
The vendor image files are a bunch of proprietary binaries and drivers that allow your phone to run properly. These vendor files were originally in /system on all previous Nexus devices but starting with the Nexus 9, they were moved to their own partition, /vendor. Super convenient for ROM developers since they no longer have to include those files from the factory images; instead, people can just flash the images directly from Google.
Click to expand...
Click to collapse
That might not be entirely accurate. Layers installs to the vendor partition, and I believe some aspects of gapps might too. It's best just to flash the vendor whenever flashing a ROM to ensure there's no residual data that could cause problems.
Heisenberg said:
That might not be entirely accurate. Layers installs to the vendor partition, and I believe some aspects of gapps might too. It's best just to flash the vendor whenever flashing a ROM to ensure there's no residual data that could cause problems.
Click to expand...
Click to collapse
Yes, I'll give you that. Just not strictly necessary but it is good practice
nathanchance said:
Yes, I'll give you that. Just not strictly necessary but it is good practice
Click to expand...
Click to collapse
I'd totally define it as being necessary, not flashing the vendor is very much like dirty flashing one ROM over another. Plus, it's things like failing to flash the vendor that cause bogus bug reports in ROM threads and waste everyone's time.
Heisenberg said:
That might not be entirely accurate. Layers installs to the vendor partition, and I believe some aspects of gapps might too. It's best just to flash the vendor whenever flashing a ROM to ensure there's no residual data that could cause problems.
Click to expand...
Click to collapse
Some gapps packages may install to /vendor? Do you have any info on what packages or types of files from gapps package would get installed in /vendor?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Some gapps packages may install to /vendor? Do you have any info on what packages or types of files from gapps package would get installed in /vendor?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I honestly don't know, I believe I read it somewhere but I can't remember where.
Heisenberg said:
I honestly don't know, I believe I read it somewhere but I can't remember where.
Click to expand...
Click to collapse
No worries, I'm sure one of us will stumble on it soon enough
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Some gapps packages may install to /vendor? Do you have any info on what packages or types of files from gapps package would get installed in /vendor?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Looking at the installer script in OpenGapps, nothing gets added to the /vendor partition. Google apps are installed onto the system, while vendor is a list of proprietary blobs.
DJBhardwaj said:
Looking at the installer script in OpenGapps, nothing gets added to the /vendor partition. Google apps are installed onto the system, while vendor is a list of proprietary blobs.
Click to expand...
Click to collapse
Yeah I looked at the same thing just before. We can disregard that portion of what I said, the information I read was obviously wrong.
Is it necessary to flash vendor images when using the stock ROM from Google then rooting after clean flash it?
Thanks!
fresnogamer said:
Is it necessary to flash vendor images when using the stock ROM from Google then rooting after clean flash it?
Thanks!
Click to expand...
Click to collapse
Nope. Flashing vendor is only required when switching to a different security update. The root and/or clean flash process does not touch the /vendor partition.
Sent from my Nexus 5X using Tapatalk
Thank you for the info.
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
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 signifies 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 base. 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.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone. The phone will fail to boot if you mismatch the vendor.img with a different OS base. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat.
Click to expand...
Click to collapse
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
SlimSnoopOS said:
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
Click to expand...
Click to collapse
Thanks so much for the swift reply! I'll check these links out right away. I'm sure they will fill in the gaps for me.
Best,
KT
KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
jhs39 said:
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0..
Click to expand...
Click to collapse
MultiRom support for this device was released when Marshmallow was out. So MR33 is based on the Marshmallow branch and ships with 3.0.2. The developer just isn't ready to release support for Nougat 7.0 and couple that with the issues of TWRP 3.0.2-x. He's actively pushing commits to support Nougat.
Sent from my Nexus 5X using Tapatalk
jhs39 said:
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
Click to expand...
Click to collapse
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
KilgoreTrout71 said:
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
Click to expand...
Click to collapse
It might just take a while for the service to go through. Good luck.
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.