Related
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
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.
[continuation of title]
And this is my way of trying to contact him about His pixel experience Project which He seems to be Working on
So If you read this
Please provide information so that we can contact you
Thx in advance! (If read)
Some random said:
[continuation of title]
And this is my way of trying to contact him about His pixel experience Project which He seems to be Working on
So If you read this
Please provide information so that we can contact you
Thx in advance! (If read)
Click to expand...
Click to collapse
NO luck,stuck at G logo :crying:
lookmanns said:
NO luck,stuck at G logo :crying:
Click to expand...
Click to collapse
Me 2
Even with A CRAP TON
Of patches
Some random said:
Me 2
Even with A CRAP TON
Of patches
Click to expand...
Click to collapse
btw I found this dev in galaxy s2 plus forum,and his name is ud4
lookmanns14 said:
btw I found this dev in galaxy s2 plus forum,and his name is ud4
Click to expand...
Click to collapse
Oh
Nice!
UPDATE:
I was able to contact him and got an answer
He stated that he did not have an Xperia x to test this ROM
But told that I could test and send feedback if it works or not.
Maybe you can write a PM asking if you can test too! (Anyone who reads this can ask!)
This whole thing feels weird.
On first flash, recovery says the ROM was created by jhenrique09, who is an official maintainer of PE. But after searching both jhenrique09 and PE's official Github, there's no sign of suzu on the list. I'm assuming this is a port. This brings us to another problem.
A quick look at the file name reveals this ROM is based on 4.4 kernel. As far as I know, there is no Pie ROM out there that is using 4.4 kernel (Chippa_a's LOS uses 3.10, Omni and Treble uses 4.9). The closest thing I could think of is Omni 8, but why port a Pie ROM using an Oreo base?
Lastly, who would make a ROM for a phone they don't have?
iH8Ecchi said:
This whole thing feels weird.
On first flash, recovery says the ROM was created by jhenrique09, who is an official maintainer of PE. But after searching both jhenrique09 and PE's official Github, there's no sign of suzu on the list. I'm assuming this is a port. This brings us to another problem.
A quick look at the file name reveals this ROM is based on 4.4 kernel. As far as I know, there is no Pie ROM out there that is using 4.4 kernel (Chippa_a's LOS uses 3.10, Omni and Treble uses 4.9). The closest thing I could think of is Omni 8, but why port a Pie ROM using an Oreo base?
Lastly, who would make a ROM for a phone they don't have?
Click to expand...
Click to collapse
IT seemed kindof fishy to me too but....well....it kind of boots
We could try an android 8.1 OEM file and see if it boots
Some random said:
IT seemed kindof fishy to me too but....well....it kind of boots
We could try an android 8.1 OEM file and see if it boots
Click to expand...
Click to collapse
If not.....extract kernel and see what's wrong I guess
Some random said:
IT seemed kindof fishy to me too but....well....it kind of boots
We could try an android 8.1 OEM file and see if it boots
Click to expand...
Click to collapse
it will not boot with android 8.1 an 9 oem..you just got infinity restart
I think oem already include in this rom,you can check oem file after flash the rom in /root/oem using twrp file manager
Someone needs to take some logs without patches of any sort
On the 4.4 kernel Version
(Got private message about this 45 minutes ago)
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.
are there any roms for the N200 5G that would give better performance?
let me know
Try a GSI for now. One specific individual had been cranking on getting a device tree together, and if you have any experience, he could use your help.
rinnycoop121 said:
are there any roms for the N200 5G that would give better performance?
let me know
Click to expand...
Click to collapse
I recommend the CherishOS 12 GSI. It's a good GSI to start with if you're new.
twomad said:
I recommend the CherishOS 12 GSI. It's a good GSI to start with if you're new.
Click to expand...
Click to collapse
ok How do we flash roms on the N200 5G?
rinnycoop121 said:
ok How do we flash roms on the N200 5G?
Click to expand...
Click to collapse
There are multiple tutorials on the internet. Here's an example https://www.droidwin.com/install-android-12-gsi-roms-on-oneplus-nord-n200-5g/
Here is my guide:
GSIs on N200
The process of flashing alone is conventional, shouldn't even need a thread to detail, but still leaving a thread here for search indexing. With an unlocked BL, flash an ARM64 AB GSI within fastbootd, reboot to recovery, format userdata, reboot...
forum.xda-developers.com
Note that I do not recommend GSI's as I cannot get Magisk or VoLTE to work with them.
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
elginsk8r said:
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
Click to expand...
Click to collapse
great
rinnycoop121 said:
are there any roms for the N200 5G that would give better performance?
let me know
Click to expand...
Click to collapse
There are a few projects in the works. I personally am waiting to sell my current laptop to fund a ryzen 5 5600 dev rig which will allow me to build a larger variety ROMs as I add storage. I have it worked out where the price of my laptop will give me enough to order everything but storage drives. Settling with a single 16GB dimm to maximize upgradability while maintaining the best price to performance ratio currently available.
elginsk8r said:
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
Click to expand...
Click to collapse
hey buddy, i seen your trees, looking good. i just got my n200 and am waiting for unlock code. i built your rom with your trees and will flash once i'm unlocked. Thanks for all your hard work! as far as i can see you"re the only one working on n200 (dre9). do you accept pull requests rom and/or device side?
You can submit patches via review.evervolv.com gerrit. I am also on telegram if you have questions (just no eta requests). Kernel has been purged of Linux stable merges to be closer to the caf tag used. Trees are lineage compatible via 2 reverts if anyone wishes to build for lineage
I have a device tree and a kernel tree that can be used to compile LineageOS for the Nord N200. In its current state, only Wi-Fi is not working, which I have not been able to fix.
Because OOS12 came out for this device last week, I have to wait until OP releases the A12 kernel code, which could take anywhere between two and five months.
andr01dfr3ak said:
I have a device tree and a kernel tree that can be used to compile LineageOS for the Nord N200. In its current state, only Wi-Fi is not working, which I have not been able to fix.
Because OOS12 came out for this device last week, I have to wait until OP releases the A12 kernel code, which could take anywhere between two and five months.
Click to expand...
Click to collapse
WiFi is working with @elginsk8r trees. I'll run a build with your trees once I get a chance. I haven't been able to build much as work is crazy busy right now.
rc420head said:
WiFi is working with @elginsk8r trees. I'll run a build with your trees once I get a chance. I haven't been able to build much as work is crazy busy right now.
Click to expand...
Click to collapse
I also have a bunch of stuff on gerrit cleaning up previous issues and further refinement. Message me on telegram @andr01dfr3ak and maybe we can work together to avoid reinventing the wheel.
Not sure, but I got the DL link for the Android 12 OTA update...: " https://android.googleapis.com/packages/ota-api/package/2ae18bc3e36cfe74ae7f1b65d0f817043c57707a.zip "
AboveTG said:
Not sure, but I got the DL link for the Android 12 OTA update...: " https://android.googleapis.com/packages/ota-api/package/2ae18bc3e36cfe74ae7f1b65d0f817043c57707a.zip "
Click to expand...
Click to collapse
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
andr01dfr3ak said:
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
Click to expand...
Click to collapse
Alright not gonna lie man, im kind of new to all this, but I downgrade with the msm tool and ill try to figure out how to build. I know I need to fork it, but after that I have no clue what to do.
andr01dfr3ak said:
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
Click to expand...
Click to collapse
I found a payload dumper on github that works well. I renamed it payloaddumper+ because I felt it fit the tool name better. should work as a portable app I believe. Just run the .exe. Hope this helps.