How to port vendor? - Android Q&A, Help & Troubleshooting

How can I port for the with the same processor? in vendor.img which files do i need to change? which lib? etc. thx

0

Seppppx said:
There isn't a specific guide for this. You will have to use your creative thinking to create solutions for problems. But you can follow these steps.
1. If you want to port your vendor to a new android version. See what was changed with phones with the same SoC.
2. Replace old files with new files from the other device vendor.
3. Be careful. You can mess up your phone.
Click to expand...
Click to collapse
I want to try this for gsi roms. Because current GSI roms send me to the recovery part. can't boot.
As you said number 2 I don't know which old files to replace
if it's easy for you maybe one day help with teamviewer

You'd build a GSI system image and change that. You don't need to use /vendor as it contains blobs for the device and doesn't need to be changed.

0

Seppppx said:
You won't need to port a vendor partition if you want to try GSIs.
Unless your phone is not treble. Have you checked if your phone is treble? You can do that by installing treble check from the Google Play store.
Which GSIs have you tried?
What device do you have?
What Android version do you have.
Devices that ship with Android 8 must be treble because of requirements by Google. (Unless your phone isn't google certified or VTS certified, I'm not sure)
You can see which files to add and delete (this won't be the same for your phone) by looking at the diff between treble and non treble proprietary-files.txt, proprietary-files-qc.txt, proprietary-files-qc-perf.txt.
https://github.com/ArrowOS-Devices/android_device_asus_zenfone3/compare/arrow-9.x...9.x-non-treble
Click to expand...
Click to collapse
Again hi. Phh gsi roms work fine. I want to try Ertan gsi. erfan gsi does not boot. That's why I thought maybe porting would be the solution. I have gm9 pro. Sp660 SoC. I want try a2 vendor port but ı cant

aykutfb93 said:
Again hi. Phh gsi roms work fine. I want to try Ertan gsi. erfan gsi does not boot. That's why I thought maybe porting would be the solution. I have gm9 pro. Sp660 SoC. I want try a2 vendor port but ı cant
Click to expand...
Click to collapse
No it's with how the system.img is built. Sometimes takes a bit more work to get things booting

TheExploitedOne said:
No it's with how the system.img is built. Sometimes takes a bit more work to get things booting
Click to expand...
Click to collapse
oh okey understand. I think there is no any solution :/

aykutfb93 said:
How can I port for the with the same processor? in vendor.img which files do i need to change? which lib? etc. thx
Click to expand...
Click to collapse
Ihave The Same Question but with different processor

Related

Getting Device Tree And Vendor Blobs For Less-Used Device

I had made a thread about creating a custom ROM for Android over here: http://forum.xda-developers.com/general/xda-assist/building-custom-android-rom-t3526514#post70277383 and Art Vanderlay suggested I post here, so here it is.
I own the BLU Energy X 2, and I am in need of the Device Tree and Vendor Blobs for the phone to create a custom ROM based off of CyanogenMod. My device currently has CyanogenMod on it, however it's an unofficial port for the BLU Studio Selfie. I am not sure how the dev of that ROM got these files, however the Infinix Hot 2 is a "clone" of that device, so he may have just ported it from there, or it may have not even needed porting at all Anyways, for me to create a custom ROM based off of CyanogenMod, I need the Device Tree and Vendor Blobs. I do have the ProjectConfig file if that helps.
These files are usually somewhere on GitHub, but due to the development community for BLU devices in general being almost non-existant, these files are nowhere to be found. So, how can I get these files for my device to start building a custom ROM? Thanks
If you need any other information, please reply.
Device Specs:
BLU Energy X 2
Model #: E050U
Android Version: 5.1 Lollipop
Kernel Version: 3.10.74+
Chipset: MT6580
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Audriuskins said:
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Click to expand...
Click to collapse
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
NateDev473 said:
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
Click to expand...
Click to collapse
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Audriuskins said:
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Click to expand...
Click to collapse
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
NateDev473 said:
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
Click to expand...
Click to collapse
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Audriuskins said:
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Click to expand...
Click to collapse
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
These come from the oem. While the directions posted sometimes work it is dirty hacking at best and never stable. This is why developers stay away from mtk devices and they are really only used in cheap devices.
NateDev473 said:
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
Click to expand...
Click to collapse
Search on Github
Audriuskins said:
Search on Github
Click to expand...
Click to collapse
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
NateDev473 said:
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
Click to expand...
Click to collapse
No idea x)
I guess you can try xd
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
Ok, thanks
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
NateDev473 said:
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
Click to expand...
Click to collapse
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Audriuskins said:
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Click to expand...
Click to collapse
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
NateDev473 said:
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
Click to expand...
Click to collapse
I can't help you very much, because I'm new in MTK development ://
Audriuskins said:
I can't help you very much, because I'm new in MTK development ://
Click to expand...
Click to collapse
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
NateDev473 said:
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
Click to expand...
Click to collapse
I dont know

Regarding Treble support

Our rosy had android N out of the box I wonder will it have treble support or not..?
There is a /cust partition that could be used to move vendor files but it needs work
I'm going to try to copy the files and flash a GSI image to see if it boots
Manosdocpap said:
There is a /cust partition that could be used to move vendor files but it needs work
I'm going to try to copy the files and flash a GSI image to see if it boots
Click to expand...
Click to collapse
Hi, what is a GSI image, if you don't mind answering...
iamboredatwork said:
Hi, what is a GSI image, if you don't mind answering...
Click to expand...
Click to collapse
GSI stands for Generic System Image, its an image made for treble supported devices
Manosdocpap said:
There is a /cust partition that could be used to move vendor files but it needs work
I'm going to try to copy the files and flash a GSI image to see if it boots
Click to expand...
Click to collapse
Tell us if it works
It works, but firmware is faulty.
Juanan and another dev have fixed mostly this faulty firmware
Manosdocpap said:
It works, but firmware is faulty.
Juanan and another dev have fixed mostly this faulty firmware
Click to expand...
Click to collapse
When will it be open for all to try the new GSIs..
When will the developers bring treble support to our device?
Thanks for your response
Android P treble also boots.
When you find some Oreo firmware blobs then you have your answer.
So can I flash the developer preview treble ROM of android p on my rosy ?
yeah, does the treble rom android p work for redmi 5, and is it buggy please? if someone can test and tell us what bugs it has or whether it works that would be great please
Manosdocpap said:
It works, but firmware is faulty.
Juanan and another dev have fixed mostly this faulty firmware
Click to expand...
Click to collapse
*Please* make a small tutorial explaining how to get treble working on Rosy.
Thank you.
Manosdocpap said:
It works, but firmware is faulty.
Juanan and another dev have fixed mostly this faulty firmware
Click to expand...
Click to collapse
How did you seperate vendor files? Did u copy them directly from system/vendor? Which files did u copy? Shed some light on the situation. Thanks in Advance. Keep up the good work
it would be great if someone could test it and tell us whether it works fine on our ROSY

GALAXY J6 (SM-J600F) Treble supported, arm/arm64 ?

Hi
I am trying to find any custom rom that could be flashed on my J600F device.
Long story short, there is not.
I learned (and checked) J6 is actually compatible with project treble.
Now, that i know i can flash GSI roms, i am still a bit confused if this device is ARM/ARM64.
Any clue ?
dzeron said:
Hi
I am trying to find any custom rom that could be flashed on my J600F device.
Long story short, there is not.
I learned (and checked) J6 is actually compatible with project treble.
Now, that i know i can flash GSI roms, i am still a bit confused if this device is ARM/ARM64.
Any clue ?
Click to expand...
Click to collapse
I don't know too much about the subject, but I read that you need GSI's that are ARM with ARM64 binders. Samsung likes using 64-bit chips to run in 32-bit mode lol
ShaDisNX255 said:
I don't know too much about the subject, but I read that you need GSI's that are ARM with ARM64 binders. Samsung likes using 64-bit chips to run in 32-bit mode lol
Click to expand...
Click to collapse
Thank you for the answer.
That's quite even more confusing unfortunately.
If anything comes up, like a GSI/Custom rom (i tried without any positive result) that you are sure it should work for the device.. PM me anytime
dzeron said:
Thank you for the answer.
That's quite even more confusing unfortunately.
If anything comes up, like a GSI/Custom rom (i tried without any positive result) that you are sure it should work for the device.. PM me anytime
Click to expand...
Click to collapse
On 4pda there is a working gsi
Kep1105 said:
On 4pda there is a working gsi
Click to expand...
Click to collapse
Send me the link and thank you !! :good:
dzeron said:
Send me the link and thank you !! :good:
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?s=&showtopic=908536&view=findpost&p=81620052
What's that I wanna know
Currently using Omni ROM gsi
danicadanicadanica said:
Currently using Omni ROM gsi
Click to expand...
Click to collapse
pls tell me what GSI rom did you install with complete package name of the rom, and link, thanks in advance. Hope you read my reply
For the record, the name that the GSI are adapting that are compatible with the J6 is called a64 or sometimes referred to as arm32_binder64
Not to be confused with arm64 which is completely 64 bits
So, the GSI are as follows:
arm - Not compatible with J6
arm64 - Not compatible with J6
a64 - Compatible with J6

Repartition Tool for A5 - A7 (2017)

Code:
Your warranty is now void.
Should anything happen to your device, I will be there to help you,
but I won't be responsible for any damage on your device.
before flashing it! YOU are choosing to make these modifications
This is a flasheable zip that makes the Galaxy A5 and A7 (2017 Series) Treble capable
What does the zip do?
if you flash it once it deletes the system partition and creates 2 new partitions:
system ~4.1Gb
vendor 600Mb
and installs modified TWRP for Treble
if flashed again, it will erase vendor and system partitions and create a single system partition ~4.7Gb (stock) plus reinstall TWRP stock version.
What doesn't the zip do?
this zip does not add the necessary files for Project Treble, it only creates the necessary partitions
Notes:
repartitioning is an extremely dangerous process, I have personally tested it on an A720F and the Muhamet User has confirmed its operation on an A520F.
for now the zip is only useful for developers because we do not have a vendor partition usable so far
Special thanks to:
Corsicanu for stock TWRP
CosmicDan for the repartitioning guide
Muhamet for Trying it on his A5
Downloads
Repartition_Tool_A5-A7_2017.zip - TWRP 3.3.1-0
A7_TDKernel.img - Treble Debug Kernel (Based on HadesKernel 1.7)
XDA:DevDB Information
Treble Repartition Tool for A5 - A7 (2017), Tool/Utility for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
Reverant
Version Information
Status: Testing
Created 2019-06-15
Last Updated 2019-09-01
What does this zip?
Repartition all partitions?
A bit more information in OP thread would be nice
Wher is the zip??
Simon1511 said:
What does this zip?
Repartition all partitions?
A bit more information in OP thread would be nice
Click to expand...
Click to collapse
I assume so. You can also do this with parted.
Simon1511 said:
What does this zip?
Repartition all partitions?
A bit more information in OP thread would be nice
Click to expand...
Click to collapse
no at all, only modifies the system partition, your other partitions like "data" will be untouched
Honestly, this seems promising.
But, does the vendor partition remain empty, or does this copy the vendor files to there, so we can install treble ROMs?
Or we should flash a treble ROM that's made for our device specifically so it fills that hole? Or maybe some other way? That part is a bit unclear. In short, how does the vendor partition get filled?
Also, you mentioned treble TWRP. Where did you get it? Did you make it? What version is it?
Thanks for your patience about this
sheepkill15 said:
Honestly, this seems promising.
But, does the vendor partition remain empty, or does this copy the vendor files to there, so we can install treble ROMs?
Or we should flash a treble ROM that's made for our device specifically so it fills that hole? Or maybe some other way? That part is a bit unclear. In short, how does the vendor partition get filled?
Also, you mentioned treble TWRP. Where did you get it? Did you make it? What version is it?
Thanks for your patience about this
Click to expand...
Click to collapse
Yes, you need a treble rom or vendor files and a different boot image. Then it's ready for gsi's. Treble twrp can be compiled similar to "normal" twrp. So someone needs to build a treble rom. You?
SnowFuhrer said:
Yes, you need a treble rom or vendor files and a different boot image. Then it's ready for gsi's. Treble twrp can be compiled similar to "normal" twrp. So someone needs to build a treble rom. You?
Click to expand...
Click to collapse
Thought that was the case
Hehe, maybe I could, but I don't think I will
But well, we'll see what happens in the future.
I was trying to make a usable vendor partition, but I don know how exactly, and now I am studing, I am on a "walted 1 second for power, watling another", pelease be patient
the twrp was modified by me, its v3.2.3-1 , my conection intenet drops when I try to upload the zip
Soon I will edit the thread ading some of info
Reverant said:
I was trying to make a usable vendor partition, but I don know how exactly, and now I am studing, I am on a "walted 1 second for power, watling another", pelease be patient
the twrp was modified by me, its v3.2.3-1 , my conection intenet drops when I try to upload the zip
Soon I will edit the thread ading some of info
Click to expand...
Click to collapse
Any news??
We need this on your device please. Come to our rescue.
Thanks and looking forward
treble A5
tested on A5 2017 work fine but vendor partition can be mounted
soltan82 said:
tested on A5 2017 work fine but vendor partition can be mounted
Click to expand...
Click to collapse
yes, you need a moded kernel to mount it, i have one, but for A7.
Reverant said:
yes, you need a moded kernel to mount it, i have one, but for A7.
Click to expand...
Click to collapse
Do for A5 please
Please update
Moddingexpert1988 said:
Please update
Click to expand...
Click to collapse
Why? Theres no need for an update.
Also, stop asking for updates everywhere, thats against the XDA rules.
Simon1511 said:
Why? Theres no need for an update.
Also, stop asking for updates everywhere, thats against the XDA rules.
Click to expand...
Click to collapse
Gsi not working,because don't have treble vendor
Moddingexpert1988 said:
Gsi not working,because don't have treble vendor
Click to expand...
Click to collapse
You mean you have no vendor partition?
You have TWRP that came with it installed and you can see/mount the vendor partition in the recovery? If so, theres nothing wrong with this script.
Simon1511 said:
You mean you have no vendor partition?
You have TWRP that came with it installed and you can see/mount the vendor partition in the recovery? If so, theres nothing wrong with this script.
Click to expand...
Click to collapse
No what I'm trying to say is that the vendor partition is empty and I would like you to update it for that
Moddingexpert1988 said:
No what I'm trying to say is that the vendor partition is empty and I would like you to update it for that
Click to expand...
Click to collapse
Dude, did you even read the OP post?
It clearly says "...Does not add the neccessary files for Project Treble...".
This script only adds an empty partition, not the files needed for treble.

Xiaomi 12X custom rom requested

Hi everyone, I've been trying to find a custom rom for Xiaomi Mi 12X, but none found so far. I tried to port Pixel Experience rom using the Xiaomi Mi 11X (alioth) device tree and changed accordingly, since the SOC and almost all specs are the same except Camera. Can anybody shed some light in how to correctly port the ROM for my devices without official device tree from LineageOS or Pixel Experience? Thank you.
Anybody has any suggestions?
JChanMe said:
Anybody has any suggestions?
Click to expand...
Click to collapse
Hi, right now I'm using crdroid gsi, which works pretty good. Except of fp, everything works as it should. It's smooth, has a good bb and even MGC's Gcam 8.1, last stable, works incl. portrait, nightmode and with all lenses (ok, no pixelbinning). Installing is pretty simple: use fastbootd and just fash img to system. That's it....
Voodoojonny said:
Hi, right now I'm using crdroid gsi, which works pretty good. Except of fp, everything works as it should. It's smooth, has a good bb and even MGC's Gcam 8.1, last stable, works incl. portrait, nightmode and with all lenses (ok, no pixelbinning). Installing is pretty simple: use fastbootd and just fash img to system. That's it....
Click to expand...
Click to collapse
Thank you but I don't see it on crdrood website, did you build it yourself?
JChanMe said:
Thank you but I don't see it on crdrood website, did you build it yourself?
Click to expand...
Click to collapse
It's a gsi treble rom (that works with many vendors)... Just search for project treble on xda!
Voodoojonny said:
It's a gsi treble rom (that works with many vendors)... Just search for project treble on xda!
Click to expand...
Click to collapse
Thank you. I figured it out and tried a few treble roms including pixel experience, there are a few problems including auto brightness, fingerprint and vibrator. You had the same problems?
JChanMe said:
Thank you. I figured it out and tried a few treble roms including pixel experience, there are a few problems including auto brightness, fingerprint and vibrator. You had the same problems?
Click to expand...
Click to collapse
Yes, especially the sound makes problems... When usung videocall, it's awfully distorted. I'm using stock for now. With Lawnchair and some modifications it's ok for now.
Do you know, why there's no thread for our phone here?
Just seen, you are forking some repositories... Have you been successful in building?
Voodoojonny said:
Just seen, you are forking some repositories... Have you been successful in building?
Click to expand...
Click to collapse
I successfully build the ROM without errors, just some warnings, but it didn't boot aftter flashing it.
JChanMe said:
I successfully build the ROM without errors, just some warnings, but it didn't boot aftter flashing it.
Click to expand...
Click to collapse
Did you flash with vendor or system only?
Voodoojonny said:
Did you flash with vendor or system only?
Click to expand...
Click to collapse
No, I used the same procedure as described for Alioth device, fastboot flash boot boot.img, then from recovery use adb push to update the zip ROM file.
JChanMe said:
No, I used the same procedure as described for Alioth device, fastboot flash boot boot.img, then from recovery use adb push to update the zip ROM file.
Click to expand...
Click to collapse
But how did you built the rom. Did you get out a flashing zip directly? Normally, you create different partitions as fas as I know... Would you share your rom? Btw. which one did you build?
Voodoojonny said:
But how did you built the rom. Did you get out a flashing zip directly? Normally, you create different partitions as fas as I know... Would you share your rom? Btw. which one did you build?
Click to expand...
Click to collapse
Yes, after building I got a zip and flashing it using update by adb push. I built Pixel Experience Android 11
JChanMe said:
Yes, after building I got a zip and flashing it using update by adb push. I built Pixel Experience Android 11
Click to expand...
Click to collapse
But you used the lineage device tree. And PE is aosp not lineage. Might that be the problem? Would you try to build crdroid? Or instruct me how to setup a build environment?
No, I used the PE device tree, not Lineage. I used the build instructions provided by Pixel Experience for Alioth.
JChanMe said:
Anybody has any suggestions?
Click to expand...
Click to collapse
Yesterday xiaomi released kernel for 12x on GitHub. So I think now you can build pe/los without troubles
Maxletsplay_1 said:
Yesterday xiaomi released kernel for 12x on GitHub. So I think now you can build pe/los without troubles
Click to expand...
Click to collapse
Didn't they release the kernel when the phone was released?
JChanMe said:
Didn't they release the kernel when the phone was released?
Click to expand...
Click to collapse
Technically yes, but i've checked GitHub(about month ago) and I didn't saw kernel for this phone, just an empty folder
JChanMe said:
Didn't they release the kernel when the phone was released?
Click to expand...
Click to collapse
Did you replaced vendor libs with libs from 12x and other stuff like fstab, bins, rc files..configs? Attach logs from boot if you decide to build again. My advice is to build as eng and disable encryption, put selinux to minimal mode, nuke livedisplay, import vendor modules if you build with stock prebuilt kernel. Always look for F Linker errors in log and resolve them.
I'm waiting for AOSP rom too.

Categories

Resources