Hi, i got A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches M2G47H.
Im using RR O v6.1.0 20180709 santoni Unofficial treble, and using red wolf recovery, and Clarity 3.9.
already try using another rom, but still same problem.
How To fix this? T-T
Hiya! I have the same issue. The only thing I know that this warning appears after installing custom kernel (Clarity)
LineageOS 15.1 (by Swapnil Soni) + Clarity 4.0 Treble.
i've used luisrom setup: official 3.2.2.0 twrp + v37 firmware + RR-O-v6.1.0-20180731-santoni-Unofficial-treble-LuisROM + open_gapps-arm64-8.1-nano-20180731.
everything is ok, but i have received that msg too. click on ok and still running good
Related
Has anybody tried the Android P DP4 GSI on the Xiaomi Mi 8/ Mi 8 SE?
Couldn't get the treble P GSI to boot on my Mi 8 SE but I managed to get the Oreo GSI running (doesn't have notch support though).
PravAndroidGeek said:
Has anybody tried the Android P DP4 GSI on the Xiaomi Mi 8/ Mi 8 SE?
Couldn't get the treble P GSI to boot on my Mi 8 SE but I managed to get the Oreo GSI running (doesn't have notch support though).
Click to expand...
Click to collapse
Which GSI booted on your SE?
Other Mi8 SE users reported that every GSI they flashes resulted in a bootloop.
Can you also mention the last MIUI version you had when you flashed a GSI?
As for P, you tried the semi-GSI, right?
Some people said that they had to fix things themselves for the image to boot but did you try flashing Magisk or setting Selinux to permissive? There should be a "permissiver" zip on the P gsi thread if I'm not mistaken.
dm-verity and selinux could cause a bootloop.
The Marionette said:
Which GSI booted on your SE?
Other Mi8 SE users reported that every GSI they flashes resulted in a bootloop.
Can you also mention the last MIUI version you had when you flashed a GSI?
As for P, you tried the semi-GSI, right?
Some people said that they had to fix things themselves for the image to boot but did you try flashing Magisk or setting Selinux to permissive? There should be a "permissiver" zip on the P gsi thread if I'm not mistaken.
dm-verity and selinux could cause a bootloop.
Click to expand...
Click to collapse
Got my Mi8 SE running MIUI 9 Chinese.
Unlocked the bootloader and flashed the latest Xiaomi.EU MIUI 10 ROM as a base and then tried both: GSI for phh-Treble AOSP and Resurrection Remix phh-Treble. Both worked surprisingly well, the notch being detected was the main issue. I followed this guide on xda.
Yes it was the P semi-GSI that resulted in a bootloop. Might try the permissiver zip.
PravAndroidGeek said:
Got my Mi8 SE running MIUI 9 Chinese.
Unlocked the bootloader and flashed the latest Xiaomi.EU MIUI 10 ROM as a base and then tried both: GSI for phh-Treble AOSP and Resurrection Remix phh-Treble. Both worked surprisingly well, the notch being detected was the main issue. I followed this guide on xda.
Yes it was the P semi-GSI that resulted in a bootloop. Might try the permissiver zip.
Click to expand...
Click to collapse
Tell us how it works out [emoji846]
Skickat från min MI 8 via Tapatalk
PravAndroidGeek said:
Got my Mi8 SE running MIUI 9 Chinese.
Unlocked the bootloader and flashed the latest Xiaomi.EU MIUI 10 ROM as a base and then tried both: GSI for phh-Treble AOSP and Resurrection Remix phh-Treble. Both worked surprisingly well, the notch being detected was the main issue. I followed this guide on xda.
Yes it was the P semi-GSI that resulted in a bootloop. Might try the permissiver zip.
Click to expand...
Click to collapse
Been wanting to get the 8 se, but I've been waiting to hear if phh-treble and other GSIs work before buying. other than notch problems are there any other major issues? Once P is released and phh-treble is updated to android 9 the notch won't be a problem anymore due to AOSP notch support.
Running lineage GSI on SE too without issues (except some full screen apps which do not support notch). The minimum brightness is a bit high.
Ydraulikos said:
Running lineage GSI on SE too without issues (except some full screen apps which do not support notch). The minimum brightness is a bit high.
Click to expand...
Click to collapse
Can you point me to a guide to run Lineage os or RR on out SE?
I am familiar in flashing custom for many years but i am new to treble and just heard about it.
Unlock your bootloader, flash a TWRP and format your data partition. Then flash and try to boot the latest xiaomi.eu rom. If you succeed, format /data /system /cache and flash /system with an arm64 GSI for A only devices such as https://github.com/phhusson/treble_...d/lineage-v21/system-arm64-aonly-gapps-su.img
Ydraulikos said:
Unlock your bootloader, flash a TWRP and format your data partition. Then flash and try to boot the latest xiaomi.eu rom. If you succeed, format /data /system /cache and flash /system with an arm64 GSI for A only devices such as https://github.com/phhusson/treble_...d/lineage-v21/system-arm64-aonly-gapps-su.img
Click to expand...
Click to collapse
ok, i am running xiaomi.eu rom so thats allready done.
The img i download is allready the lineage os, what i see
And is there a completely different forum/site where just. only trebel based custom roms are stored and discussed.
Is it gapps included, because normally it has to be flashed separtly.
Can you just format and go back to any miui rom, and when wanted to trebel based, just flash img file in /system again
Sorry for all the questions
marcel112 said:
ok, i am running xiaomi.eu rom so thats allready done.
The img i download is allready the lineage os, what i see
And is there a completely different forum/site where just. only trebel based custom roms are stored and discussed.
Is it gapps included, because normally it has to be flashed separtly.
Can you just format and go back to any miui rom, and when wanted to trebel based, just flash img file in /system again
Sorry for all the questions
Click to expand...
Click to collapse
Gapps are included in the above link. You don't need to flash anything else. And yes you can always flash the stock rom. Just remember to erase /data when you change between MIUI & AOSP based ROMs.
Ydraulikos said:
Gapps are included in the above link. You don't need to flash anything else. And yes you can always flash the stock rom. Just remember to erase /data when you change between MIUI & AOSP based ROMs.
Click to expand...
Click to collapse
ok, so its like normal business.
Normally when i switch between custom i allways full wipe
/dalvik
/data
/cache
/system
As long as format data was once, i dont have problem..
Can you provide links for more like RR for SE?
I didnt knew there was development at all for SE on custom roms
EDIT: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
this one is for RR, and if i am correct you linked me to the first in the V5 section, so the xiaomi mi 8 se is a ARM64 A-only device?
But what is the difference between gapps and vanilla
marcel112 said:
ok, so its like normal business.
Normally when i switch between custom i allways full wipe
/dalvik
/data
/cache
/system
As long as format data was once, i dont have problem..
Can you provide links for more like RR for SE?
I didnt knew there was development at all for SE on custom roms
EDIT: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
this one is for RR, and if i am correct you linked me to the first in the V5 section, so the xiaomi mi 8 se is a ARM64 A-only device?
But what is the difference between gapps and vanilla
Click to expand...
Click to collapse
Gapps include google services, vanilla does not.
Mi 8/SE are ARM64 A-only devices. You can try flashing any treble based rom with a high chance to operate normally. With a decent treble implementation, there is no need for custom rom development. The device specific blobs are moved to a separate partition and are provided by vendor.
Ydraulikos said:
Running lineage GSI on SE too without issues (except some full screen apps which do not support notch). The minimum brightness is a bit high.
Click to expand...
Click to collapse
Does the system detect the notch on lineage?
Ydraulikos said:
Gapps include google services, vanilla does not.
Mi 8/SE are ARM64 A-only devices. You can try flashing any treble based rom with a high chance to operate normally. With a decent treble implementation, there is no need for custom rom development. The device specific blobs are moved to a separate partition and are provided by vendor.
Click to expand...
Click to collapse
i did full wipe,
after that i tried to install image, but as what do i need to flash this?
system image
boot
recovery
vendor image
firmware
persist
splash
logo
etc etc?
i choose system image, but after flash ( was quick ) i get no OS?
edit: so i can flash anyone off this page, as long as i use arm64 Aonly for my Mi 8 SE?
edit 2: got it..
install is real fast, and phone is very quick
after trying treble...
i tried to go back to miui backup..
It boots fine, but i cant get past pin code?
I know 100% its the right code, does it have to do with trying treble?
PravAndroidGeek said:
Has anybody tried the Android P DP4 GSI on the Xiaomi Mi 8/ Mi 8 SE?
Couldn't get the treble P GSI to boot on my Mi 8 SE but I managed to get the Oreo GSI running (doesn't have notch support though).
Click to expand...
Click to collapse
MI8 is also same.
P GSI (can't boot)
RR oreo rom (all working)
- last MIUI verion : XIAOMI.EU 8.7.19 version.
jectsin said:
MI8 is also same.
P GSI (can't boot)
RR oreo rom (all working)
- last MIUI verion : XIAOMI.EU 8.7.19 version.
Click to expand...
Click to collapse
Everything works on RR? How is the camera?
_katho_ said:
Everything works on RR? How is the camera?
Click to expand...
Click to collapse
work. but bad quality
jectsin said:
work. but bad quality
Click to expand...
Click to collapse
yes and notch is not detected for me
marcel112 said:
yes and notch is not detected for me
Click to expand...
Click to collapse
Notches are "expected" on AOSP only with P and newer Android versions.
It probably can be modded but since P is around the corner, it might not be worth it.
The Marionette said:
Notches are "expected" on AOSP only with P and newer Android versions.
It probably can be modded but since P is around the corner, it might not be worth it.
Click to expand...
Click to collapse
i know this is not miui forum, but i made twrp backup..
Why cant i unlock after restoring after flashing Treble based roms ?
I tried yesterday 3 trebles and full wiped, and restored nandroid of miui 10.
All looks good, but after boot up, i cant get past pincode( i know its right code 110% )
I Am Facing Volte issue on every custom rom.
.In detail.
Nowadays i have tried a lot pie roms,some custom recoveries and also flashed latest firmware file from xiaomifirmwareupdater.com .
But after flashing a latest pie rom volte on my santoni is not working.
It is not even working on those roms
On which it works befores like lineage os 15.1 or aosp extended pie.
Pls help.
Is this problem related to firmware or something else .???
amandeep0007 said:
I Am Facing Volte issue on every custom rom.
.In detail.
Nowadays i have tried a lot pie roms,some custom recoveries and also flashed latest firmware file from xiaomifirmwareupdater.com .
But after flashing a latest pie rom volte on my santoni is not working.
It is not even working on those roms
On which it works befores like lineage os 15.1 or aosp extended pie.
Pls help.
Is this problem related to firmware or something else .???
Click to expand...
Click to collapse
Did you wiped vendor partition in recovery ?
Or you flashed any dolby Atmos zip ?
lokesh ganesh said:
Did you wiped vendor partition in recovery ?
Or you flashed any dolby Atmos zip ?
Click to expand...
Click to collapse
Yes i flashed vendor partition but not every time and with current rom installation i haven't wiped vendor
And i havent flashed dolby atmos zip in current rom
I m using v4android v2.7
With magisk 18.1
amandeep0007 said:
Yes i flashed vendor partition but not every time and with current rom installation i haven't wiped vendor
And i havent flashed dolby atmos zip in current rom
I m using v4android v2.7
With magisk 18.1
Click to expand...
Click to collapse
Did you do dirty flash?
If you did I recommend clean flash this time.
Didnt works
I guess that's going to be helpful for both developers and users.
Info:
P-based vendor up to date with Lineage 16.0 device trees and kernel
Full and proper support of the versioned VNDK and linker namespace isolation
Instructions:
I'm not going to provide them, just head here instead: https://forum.xda-developers.com/mi-a1/how-to/treble-stock-to-treble-everything-to-t3793734
As usual, it requires repartitioning.
Downloads:
Treble-enabled unofficial Lineage 16.0 build (already includes vendor) not updated since 05.04.2019
vendor.img and boot.img (01.05.2019)
Source code:
Common tree
Device tree
Kernel patch
Vendor blobs
Notes:
I did it for pure fun and I'm not going to provide any extensive support. So don't expect me to update it daily and fix every bug you'll cry about.
Just like any other proper Treble implementation, this doesn't include IMS blobs on the vendor partition. So no out-of-the-box VoLTE on your fancy GSIs.
Basic functionality is verified with AOSP P GSIs
Amazing! Thanks Flex!
And before anyone actually asks that: yes, it works with official Q GSI without any modifications, but has Wi-Fi issues just like everyone else.
Awesome news and great work!
Thank you so much for this.
Amazing work Bra but you already know that xD
Another great work from you. Kudos.
MASTER!
Awesome stuff, thanks for this.
can i ask . i want to flash android Q so i just need the vendor only right?
Your on on this device is amazing, than you so much!
Great job man! Thanks
flex1911 said:
And before anyone actually asks that: yes, it works with official Q GSI without any modifications, but has Wi-Fi issues just like everyone else.
Click to expand...
Click to collapse
What issues? Wifi completely not working or..?
Hi @flex1911
I tried everything, but your vendor and your LineageOS gives me black screen on Tissot.
Also it corrupts my recovery, I can't boot into it :/
I have this issue after flashing the "boot.img"
Iv4n99 said:
Hi @flex1911
I tried everything, but your vendor and your LineageOS gives me black screen on Tissot.
Also it corrupts my recovery, I can't boot into it :/
I have this issue after flashing the "boot.img"
Click to expand...
Click to collapse
This vendor is for Treble roms, you don't need it if youre using Flex' LOS16
Yunikari said:
This vendor is for Treble roms, you don't need it if youre using Flex' LOS16
Click to expand...
Click to collapse
I'm trying to flash the official Q gsi
But It gives me black screen
The vendor isn't compatible with my phone
Iv4n99 said:
Hi @flex1911
I tried everything, but your vendor and your LineageOS gives me black screen on Tissot.
Also it corrupts my recovery, I can't boot into it :/
I have this issue after flashing the "boot.img"
Click to expand...
Click to collapse
Try to update your firmware.
flex1911 said:
Try to update your firmware.
Click to expand...
Click to collapse
Artem u are on fire. I bought this device after Asus. And glad you are here ?... Thanks buddy.
great work!
Nice.
Is boot.img the kernel? Sorry if it's a stupid question, and does it work with 4.9 kernels?
I am a new owner of this phone and i read that touch screen isn't working for twrp.
This problem exist and for orange fox or only for twrp? And if so how can i install custom roms or make a backup?
manthes said:
I am a new owner of this phone and i read that touch screen isn't working for twrp.
This problem exist and for orange fox or only for twrp? And if so how can i install custom roms or make a backup?
Click to expand...
Click to collapse
Touch Screen
Hello community, I have a problem when I install a recovery : TWRP (different versions), Orange Fox, Pitch Black, etc ... The installation works but the touch screen does not work. I managed to install different Custom Rom with the commands ...
forum.xda-developers.com
So custom roms have problem with this touchscreen but if i use TWRP with stock rom i will have the same problem or it is only related with the rom?
manthes said:
So custom roms have problem with this touchscreen but if i use TWRP with stock rom i will have the same problem or it is only related with the rom?
Click to expand...
Click to collapse
Recovery and ROM.
With TWRP
You can connect a USB mouse
or there is a TWRP version that works with hardware buttons
Only stock ROM 13 and 14 work with tfs_ts touchscreen afaik. No custom ROMs that I know of.
Fostel said:
Only stock ROM 13 and 14 work with tfs_ts touchscreen afaik. No custom ROMs that I know of.
Click to expand...
Click to collapse
FYI, stable Xiaomi.eu works, too, since it's stock based...
Reddit Note 10 Pro Updates
OrangeFox Recovery R11.1_3 - UNOFFICIAL | Android 12/13.
Updated: 12/04/'23
Changelog:
• Corrected version naming (R11)
• Synced the latest OrangeFox source
• Updated Magisk to 26.1
• Updated the kernel
Notes:
• There are 2 versions. One for MIUI and one for AOSP. The MIUI version includes the new touchscreen driver and does not support EROFS and F2FS compression (The MIUI version can also be used for crDroid for example since the kernel shipped with that ROM does not support EROFS or F2FS compression)
Thanks. Is it true that with orange fox i can still get miui updates?
And also where can i find it? If it is at telegram and is forbidden to share the link please send me a pm
hyperboarean said:
Reddit Note 10 Pro Updates
OrangeFox Recovery R11.1_3 - UNOFFICIAL | Android 12/13.
Updated: 12/04/'23
...
Click to expand...
Click to collapse
Happy to report that this version works with the latest fts_ts (Focaltech) touch present in recent sweet devices -- mine's an Amazon bought 6/128GB... Great job!
since this device is fully compatible with project treble, can I just flash GSI and not worrying about bug or breaking my phone? or it's just a bad idea?
you can flash GSI image from here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
i tried LineageOS TD-based, i've got some issues with power button and can't send SMS in 4G (work in 3G)...