hi all!
can somebody explain what the difference between "vendor" (beryllium-8.11.15-9.0-vendor-firmware) and the image of my os (lineage-16.0-20181127-UNOFFICIAL-beryllium) is. i tried googling it but i couldnt find a good "explain like i'm 5" kinda explanation. or maybe less what the difference is but what they are in general?
thanks!
bad1080 said:
hi all!
can somebody explain what the difference between "vendor" (beryllium-8.11.15-9.0-vendor-firmware) and the image of my os (lineage-16.0-20181127-UNOFFICIAL-beryllium) is. i tried googling it but i couldnt find a good "explain like i'm 5" kinda explanation. or maybe less what the difference is but what they are in general?
thanks!
Click to expand...
Click to collapse
Vendor + Firmware it contains "vendor" and "firmware" ,since android oreo vendor are separated from system image to support project treble. Firmware is basically software for supporting the hardware.
Your Image OS (miui 10) it contains all of them, "vendor firmware and system" so everytime you flashed miui 10 you included the vendor and firmware to, no need to flash another one. Unless you are using custom rom which only contains system image.
arifreggit said:
Vendor + Firmware it contains "vendor" and "firmware" ,since android oreo vendor are separated from system image to support project treble. Firmware is basically software for supporting the hardware.
Your Image OS (miui 10) it contains all of them, "vendor firmware and system" so everytime you flashed miui 10 you included the vendor and firmware to, no need to flashed another one. Unless you are using costom rom which only contains system image.
Click to expand...
Click to collapse
ah thats where this is coming from (project treble), thanks for clarifying! (my os is lineage as stated above though)
Related
hi need inputs from this great community regarding my issue. my mobile device, which is in Android 5.1, but earlier releases of the same model was on Android 4.4. i compared both scatter files from kitkat version and L and scatter on Android L has extra FRP and EBR2 partition. i wanted to downgrade to Kitkat so im wondering if i can flash the stock rom from kitkat to my lollipop device. and since they dont have the same scatterfile or partition, i will maintain my device,which is in Lollipop, use its scatterfile but will use images from the kitkat-rom, assuming both devices have the same hardware and same drivers used, will this method work? will it overwrite or overlap partitions not normally seen when using sp-flash-tool? im excluding the preloader.bin since for some reasons i can't seem to make backup of it.
Nit really sure. Not alot of development for that chip is done here. Most devices here that have developers are using Qualcomm. But no you won't be able to mix the two and with the new partition most likely also came with a new bootloader that will prevent downgrading.
Only one way to find out. Try and find out.
wertzPH said:
hi need inputs from this great community regarding my issue. my mobile device, which is in Android 5.1, but earlier releases of the same model was on Android 4.4. i compared both scatter files from kitkat version and L and scatter on Android L has extra FRP and EBR2 partition. i wanted to downgrade to Kitkat so im wondering if i can flash the stock rom from kitkat to my lollipop device. and since they dont have the same scatterfile or partition, i will maintain my device,which is in Lollipop, use its scatterfile but will use images from the kitkat-rom, assuming both devices have the same hardware and same drivers used, will this method work? will it overwrite or overlap partitions not normally seen when using sp-flash-tool? im excluding the preloader.bin since for some reasons i can't seem to make backup of it.
Click to expand...
Click to collapse
Once you've made a proper backup with sp-flash-tool, you can safely blast out everything starting from MBR (including MBR) and higher (EBR, FAT, Recovery etc.), and overwrite it with Kitkat partitions.
I've done similar stuff to my MT6577 phone - edited MBR, merged and resized some partitions. It feels fine.
However, if Lollipop had replaced your preloader, things get little more complicated, but not too much.
Is it end of less popular custom ROMs..??
Or is it end of Custom ROM itself..??
What will be the future..??
XDA will fill with kernels and vendor images..??
syamkumar.tpl said:
Is it end of less popular custom ROMs..??
Or is it end of Custom ROM itself..??
What will be the future..??
XDA will fill with kernels and vendor images..??
Click to expand...
Click to collapse
You can't say. No one can. There are still thousands of legacy and old devices which are getting the traditional custom rom support. Uptill now. But to answer your question regarding vendor images. That could be great because. If one custom vendor.img file is made for a treble device. 95% of the other devices with treble support can boot that too. Just like phussons aosp vendor.img file.
This isn't definetly not the end. But a beginning of a new era. Treble supported custom rom vendor.img will make more roms available to more devices. Since the work pressure of devs is greatly reduced in porting it.
syamkumar.tpl said:
Is it end of less popular custom ROMs..??
Or is it end of Custom ROM itself..??
What will be the future..??
XDA will fill with kernels and vendor images..??
Click to expand...
Click to collapse
I am slightly confused. I thought that Treble was all about portable system images (GSI). In my understanding (which may well be wrong) the vendor images are (and must be) device-specific, but the GSIs are meant to be generalised. So, if there is a decent Mido vendor image (either from Xiaomi, or XDA members), we should be able to flash any GSI made by anybody - Google, Samsung, OnePlus, Xiaomi, Huawei, or whatever. Also, anybody should be able to customise any GSI to make their own GSI (e.g., by adding root, tweaking build.prop, or any other such). And, anybody should be able to build their own GSI, without worrying about the underlying hardware. If this is all correct, then I would imagine that there would be even more custom ROMs (i.e., GSIs). I would probably cook my own as well.
Hi!
i am new to the treble-enabled stuff, this is the first phone i own that is treble capable and i have a few questions. I think they can apply to other NOBS, so here i go hoping some nice guy will help me understand:
Background: i have the redmi 5plus (global) which i have unlocked (after painful 720h) and i have flashed Pixel Experience 8.1 rom, but i like to experiment and it seems most of interesting roms are on treble.
1. By default, "vince" is not treble enabled. (treble check app says so)
2. "vince" seems to be an "A only" device, not A/B device,
Main Question: Now, what should i do to try (safely) some GSI roms (like here XDA LOS 16 GSI)?
Sub-Question 1: I must most likely flash some other things first, i guess... like a vendor or a treble image? Where do i find it?
Sub-Question 2: I have installed TRWP recovery, is it treble enabled or should i ALSO find a treble enabled recovery?
If i got it all wrong, please i would be happy to stand corrected!
Hi.
Well, yeah, you need to install another vendor, as far as I know, OrangeFox is the treble enabled recovery.
Someone already explained this in this post.
Have fun. :fingers-crossed:
Xyzko said:
Hi.
Well, yeah, you need to install another vendor, as far as I know, OrangeFox is the treble enabled recovery.
Someone already explained this in this post.
Have fun. :fingers-crossed:
Click to expand...
Click to collapse
Thank you! Sometimes hard to find the right threads...
Installed orangefox, cool recovery!
One last question... how does kernel works with treble? Do i need treble enabled kernels if i want to change the kernel? Are they provided with the treble-enabled rom already or i get to keep the existing kernel? Is the kernel on a dedicated partition separated from the GSI and the Vendor? (i am starting to understand this, maybe)?
gardiol said:
Thank you! Sometimes hard to find the right threads...
Installed orangefox, cool recovery!
One last question... how does kernel works with treble? Do i need treble enabled kernels if i want to change the kernel? Are they provided with the treble-enabled rom already or i get to keep the existing kernel? Is the kernel on a dedicated partition separated from the GSI and the Vendor? (i am starting to understand this, maybe)?
Click to expand...
Click to collapse
Months ago it started to appear some projects about android 9.0 before of Google revealed it as android Pie, then at this time devices with treble support also can support GSIs from these projects according two specific conditions: the processor (first qualcomm, then exynos, kirin and mtk were supported) and kind of partition system A-A/B.
At this first times was needed to flash a vendor treble supported rom to add treble support and flash over it a GSI 9.0. without the need to flash other kernel.
In this forum there are a lot of GSIs that eventually could work in our device but it could be many bugs https://forum.xda-developers.com/project-treble/trebleenabled-device-development.
Now is not needed to complicate the job flashing a vendor, then a GSI and maybe a custom treblized kernel so started to appear first developments of roms running 9.0 and these roms will work as exactly did it any rom 7.1 or 8.1, in the future they could be include treble support.
This is the short story.
After some searching I have several question:
1. Does every 8.0 + support treble , or I need a 8.0 + rom which claim it support treble , like https://forum.xda-developers.com/redmi-3/development/rom-treble-roms-gsi-t3831555
2. There is a thing call `vendor` on treble project wiki : https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-3-3-Pro#booting-gsis-pie . What is this used for ?
3. Can I just flash above vendor instead of flashing a whole rom , then install gsi ?
4. I also found below 3 files , they contain `vendor` in names . Equal to above vendor?
https://androidfilehost.com/?fid=1322778262903982506
https://forum.xda-developers.com/showpost.php?p=79042530&postcount=161
https://forum.xda-developers.com/redmi-3/development/rom-treble-roms-gsi-t3831555/page40
twinsq said:
After some searching I have several question:
1. Does every 8.0 + support treble , or I need a 8.0 + rom which claim it support treble , like https://forum.xda-developers.com/redmi-3/development/rom-treble-roms-gsi-t3831555
2. There is a thing call `vendor` on treble project wiki : https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-3-3-Pro#booting-gsis-pie . What is this used for ?
3. Can I just flash above vendor instead of flashing a whole rom , then install gsi ?
4. I also found below 3 files , they contain `vendor` in names . Equal to above vendor?
https://androidfilehost.com/?fid=1322778262903982506
https://forum.xda-developers.com/showpost.php?p=79042530&postcount=161
https://forum.xda-developers.com/redmi-3/development/rom-treble-roms-gsi-t3831555/page40
Click to expand...
Click to collapse
1-just treble Oreo Rom which include vendor
2-i think that is source code
3-you can just install vendor then put GSI, no need the whole firmware
4-Use third link because some fixes available there
mohammadj26 said:
1-just treble Oreo Rom which include vendor
2-i think that is source code
3-you can just install vendor then put GSI, no need the whole firmware
4-Use third link because some fixes available there
Click to expand...
Click to collapse
Thank you very much ! :good:
Hello Guys after trying many roms I felt like making one for communtiy
But I didnt want to make it from scratch when google is already doing a great job
of directly proving system.img
So what I did was collected Best of all vendor and major required files for booting. Including Always on Display my favourite.
And made a Flashable Zip of that specific files, images,patches etc.
So yes this best vendor can be used on any GSI FILES which you may want to boot.
This is basically a best Suitable vendor for major roms and specific for all Google Android Roms, I will be updating it when needed
For now,
All you need to do is Install this Zip
Flash System.img (whichever you like generic or Pixel or Other Oem)
Mount system and Vendor
Flash Patch 1 & 2
Reboot System, setup everything
Install latest gms as and when available
Connect to PC (optional) and give commands provided. For best results.
Hope this is exhaustive guide
Download Links
Major Boot Vendor Files
https://drive.google.com/file/d/1GqXP2ddv1DTJ8at_nSZR2_rhRs9iJBhy/view?usp=drivesdk
Q. Why didnt you give whole rom.zip instead of such pieces
A. Because this is only for advanced users , noobs stay away. This is specially made to cater this user who will flash latest GSI images from google and dont have to wait for other Devs to make rom for them. Basically you have PixelUI with minimum bugs.
Q. Can I use other GSI With this vendor
A. As per my research and flahsing experience with this vendor I can say major boots so dont know about others.
Q. Will you support This Project
A. Yes I will and since its not difficult to flash gsi when available theirs no support needed
Q. I want support in sense how to flash and bugs
A. Youre idiot If you ask so since already said this is GSI not Rom bugs are from GSI you flashed so we cant solve. Though patches will be released when available
Special thanks to my group Tester/Fixer
https://t.me/joinchat/E1XkwhvIsDgznr0dMrxzXQ
Havoc OS DEVELOPER, major vendor files are from it including updater script.
Erfan gsi for providing system images at earliest
And you all guys for support
Youtube Video on Latest GSI
HTTPS://youtube.com/JigneshJain
Updated with latest links and vendor