"Vendor image does not match the system" message. - Essential Phone Questions & Answers

I'm using carbon rom latest build 20200122.
It performs well for now but does the vendor not match a problem? It annoys me that the message appear on each reboot which makes me think that there's a problem with how i flash it. The vendor image is the same version of my flashing of clean stock before i flash this rom. Does flashing vendor.img helps? I try to find the img file but no luck.

Related

Should I flash matching vendor.img everytime after I flash a rom?

If I flash a rom, should I fastboot flash the vendor.img that matches the base of the rom every time after the rom boots?
I am asking because on Team Nocturnal's rom it asks to do that so i want to know if i should do that for every rom i flash.

[NEED HELP] Flashing MM TWRP

I wanna go to the RR MM version ROM for Zenfone 5, but fewmsome days before I decide to do it, my microusb got some kind of bug, anyway, it doesn't connect to pc (I tried everything). So, in the tutorial says to flash the new recovery made by them, but i don't have how to connect it on pc to flash the new TWRP recovery, but I have a funcional system working (the stock .87 version from asus) and I want to know if there's a way that I can flash the recovery without using pc (once that my microusb jack is f*kd). I saw in other forum that "recovery.img" is inside the /factory partition, so apps like Flashify cannot read and write on it. Just droidboot can do that. So this is what I want to know, of there's a way to flash the recovery trough the booted Android and if I can make a script to Droidboot run. (Of course, all of them without pc). Or even if I can flash RRMM on my current twrp version (2.8.7.0)
Thanks xda.
Try to flash it via TWRP 2.8.7.0
"Error flashing image, no partition specified".
Twrp actually doesn't show any partitions to install the image.
MarconiGRF said:
"Error flashing image, no partition specified".
Twrp actually doesn't show any partitions to install the image.
Click to expand...
Click to collapse
I provided flashable zip for my RR MM rom. So you shoudl just choose zip archvie with rom to flash it.
It is not a image.
tank0412 said:
I provided flashable zip for my RR MM rom. So you shoudl just choose zip archvie with rom to flash it.
It is not a image.
Click to expand...
Click to collapse
Oh, I read your post again, i'll try to flash with twrp 2.8.7.0
Sucessful installing ROM, really fast and battery management. Thx

Camera not working after root

I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!
kwcty6888 said:
I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!
Click to expand...
Click to collapse
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?
Heisenberg said:
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?
Click to expand...
Click to collapse
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?
kwcty6888 said:
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?
Click to expand...
Click to collapse
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.
Heisenberg said:
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.
Click to expand...
Click to collapse
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!
kwcty6888 said:
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!
Click to expand...
Click to collapse
Flash the full factory images (except userdata), then flash the latest TWRP, not boot into TWRP and enter the wipe menu, select advanced wipe, tick the data box and wipe it. Boot up and see if that helps.

Need help....Not able to install cm-13.0-20160623-NIGHTLY-tomato.....

Hello guys , i am unable to install cm-13.0-20160623-NIGHTLY-tomato in my YU Yureka. Its stuck on "patching system image unconditionally"
I am using latset twrp 3.0.0.0 . I am on official Cos 12.1.
Before flashing i formatted system, dalvik-ART,cache,dalvik cache.
While installing there is no exception or error raised by recover. I kept my Yureka for 30-40 min with installation going on after so much time there is no progress, not a single percent. (and my memory card is also not shown in twrp recovery)
Then i tried to install recovery again and done the rom flashing procedure, it stucks on "Patching system image unconditionally".
Is there anything wrong with recovery or rom or i skipped any step?
plz help me guys.
@Aj_$tyle$
Use CM recovery to check if it is getting flashed. TWRP is also upgraded to 3.0.2-0. You can use that one too.
Also match SHA-1 of downloaded ROM zip file.
saurav007 said:
@Aj_$tyle$
Use CM recovery to check if it is getting flashed. TWRP is also upgraded to 3.0.2-0. You can use that one too.
Also match SHA-1 of downloaded ROM zip file.
Click to expand...
Click to collapse
dude i tried twrp 3.0.2.0 its not working for me...neither internal or external storage is shown in that recovery......lets try cm recovery...hope it will work for me
saurav007 said:
@Aj_$tyle$
Use CM recovery to check if it is getting flashed. TWRP is also upgraded to 3.0.2-0. You can use that one too.
Also match SHA-1 of downloaded ROM zip file.
Click to expand...
Click to collapse
tried CM recovery....in the middle of flashing it showing "Signature verification failed"....whats wrong with signature verification?
help me dude
@saurav007
i matched the sha 1 and they are same......
@saurav007
i matched the sha 1 and they are same......

Flashing latest vendor img causes bootloop

I was between roms, was testing out MIUI 8 before going back to Pure Nexus. After wiping I flashed pure nexus vendor img (nbd90x) and then the rom and gapps. I try to boot afterward and I just keep bootlooping from the google logo. I went back and used a 6.0 vendor img (mtc20l) and I'm able to boot into the rom but receive the message to flash the correct vendor img. But I can't since the phone won't boot with the vendor img I'm supposed to be using! I also tried using the stock image for 6.0 and 7.0 from google and neither of them are booting now. Is there something I should do differently or any other steps I can take?
Odd
DreamJohn said:
I was between roms, was testing out MIUI 8 before going back to Pure Nexus. After wiping I flashed pure nexus vendor img (nbd90x) and then the rom and gapps. I try to boot afterward and I just keep bootlooping from the google logo. I went back and used a 6.0 vendor img (mtc20l) and I'm able to boot into the rom but receive the message to flash the correct vendor img. But I can't since the phone won't boot with the vendor img I'm supposed to be using! I also tried using the stock image for 6.0 and 7.0 from google and neither of them are booting now. Is there something I should do differently or any other steps I can take?
Click to expand...
Click to collapse
Hmm I just did what u did came from miui v8 to pure nexus and I didn't bootloop running the same vendor.
DreamJohn said:
I was between roms, was testing out MIUI 8 before going back to Pure Nexus. After wiping I flashed pure nexus vendor img (nbd90x) and then the rom and gapps. I try to boot afterward and I just keep bootlooping from the google logo. I went back and used a 6.0 vendor img (mtc20l) and I'm able to boot into the rom but receive the message to flash the correct vendor img. But I can't since the phone won't boot with the vendor img I'm supposed to be using! I also tried using the stock image for 6.0 and 7.0 from google and neither of them are booting now. Is there something I should do differently or any other steps I can take?
Click to expand...
Click to collapse
Factory reset and wipe system in TWRP then try again. Then download the PN 7.0 zip if you still bootloop. I'm guessing you are referring to PN 7.0. If not, fastboot flash the vendor that matches the PN 6.0.1 base.
Sent from my Nexus 5X using Tapatalk

Categories

Resources